At me it is established gthumb-2.8.1. At an quit if to press a dagger the appendix falls and to start it again it is impossible. It is necessary to use a command kill. But if to leave using menu File->Exit, all is perfect. But if I emerge -1 "<gthumb-2.8.1", gthumb Works perfectly. Reproducible: Always Steps to Reproduce: run gthumb press button Close on titlebar exit corrupt Actual Results: ... (gthumb:1888): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed *** glibc detected *** gthumb: double free or corruption (!prev): 0x0000555555a6d970 *** ======= Backtrace: ========= /lib/libc.so.6[0x2ac235453760] /lib/libc.so.6(__libc_free+0x85)[0x2ac2354542a5] /usr/lib/libglib-2.0.so.0(g_free+0x2e)[0x2ac239cc1103] ... Expected Results: Exit like on menu File->Exit Portage 2.1.2.2 (selinux/2007.0/amd64/hardened, gcc-3.4.6, glibc-2.5-r4, 2.6.20-hardened-r5 x86_64) ================================================================= System uname: 2.6.20-hardened-r5 x86_64 Intel(R) Xeon(R) CPU E5345 @ 2.33GHz Gentoo Base System release 1.12.9 Timestamp of tree: Mon, 30 Jul 2007 01:47:01 +0000 dev-lang/python: 2.4.4-r4 dev-python/pycrypto: 2.0.1-r6 sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.61 sys-devel/automake: 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10 sys-devel/binutils: 2.17 sys-devel/gcc-config: 1.3.16 sys-devel/libtool: 1.5.23b virtual/os-headers: 2.6.21 ACCEPT_KEYWORDS="amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=nocona -O2 -pipe -fforce-addr" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/share/X11/xkb" CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf /etc/revdep-rebuild /etc/terminfo" CXXFLAGS="-march=nocona -O2 -pipe -fforce-addr" DISTDIR="/usr/portage/distfiles" FEATURES="distlocks loadpolicy metadata-transfer parallel-fetch sandbox selinux sesandbox sfperms strict" GENTOO_MIRRORS="http://distfiles.gentoo.org http://www.ibiblio.org/pub/Linux/distributions/gentoo" LANG="ru_RU.UTF-8" LINGUAS="ru en" MAKEOPTS="-j4" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --filter=H_**/files/digest-*" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X amd64 berkdb bitmap-fonts bzip2 cli cracklib crypt cups dri gdbm gif glib gnome gpm gtk hardened iconv imlib isdnlog jpeg ldap libg++ midi mudflap ncurses nls nptl nptlonly nsplugin openmp pam pcre perl pic png pppd python readline reflection selinux server session slang spl ssl symlink tcpd tiff truetype truetype-fonts type1-fonts unicode userlocales vnc xorg zlib" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null plug rate route share shm softvol" ELIBC="glibc" INPUT_DEVICES="keyboard mouse" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="ru en" USERLAND="GNU" VIDEO_CARDS="apm ark chips cirrus cyrix dummy fbdev glint i128 i810 mach64 mga neomagic nv r128 radeon rendition s3 s3virge savage siliconmotion sis sisusb tdfx tga trident tseng v4l vesa vga via voodoo" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LC_ALL, LDFLAGS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, PORTDIR_OVERLAY and I use fluxbox
Created attachment 129604 [details] error log
(In reply to comment #0) > At me it is established gthumb-2.8.1. At an quit if to press a dagger the > appendix falls and to start it again it is impossible. It is necessary to use a > command kill. But if to leave using menu File->Exit, all is perfect. Could you clarify what do you mean by 'dagger' and 'appendix' here?
(In reply to comment #2) > (In reply to comment #0) > > At me it is established gthumb-2.8.1. At an quit if to press a dagger the > > appendix falls and to start it again it is impossible. It is necessary to use a > > command kill. But if to leave using menu File->Exit, all is perfect. > > Could you clarify what do you mean by 'dagger' and 'appendix' here? > Pressing of button Close on titlebar
(In reply to comment #3) > (In reply to comment #2) > > Could you clarify what do you mean by 'dagger' and 'appendix' here? > Pressing of button Close on titlebar Oh well, I still don't get what "appendix falls" is, but whatever...
err, never had this but I could only test on x86. Could you try with version 2.10.6 of gthumb ?
(In reply to comment #5) > err, never had this but I could only test on x86. > Could you try with version 2.10.6 of gthumb ? > ACCEPT_KEYWORDS=~amd64 emerge -1 gthumb, update to 2.10.6 ... Same! back to 2.6.5
I'm clueless here because it works for me but on the other hand I don't have a selinux/hardened box.
Created attachment 130787 [details] backtraces in gdb
Comment on attachment 130787 [details] backtraces in gdb I have posted a bug into Gnome bugzilla: http://bugzilla.gnome.org/show_bug.cgi?id=476468
could you also attach the output of "bt full" when in gdb. Meaningful backtrace will require to build packages with split-debug FEATURES and the like. Thanks for the taking the time to pursue this bug.
Created attachment 130859 [details] bt & bt full I'm confuse. I re-emerge USE=debug CFLAGS="${CFLAGS} -g -ggdb" FEATURES="splitdebug nostrip" ACCEPT_KEYWORDS=~amd64 emerge -1 gthumb
hum, first you can remove nostrip from FEATURES, it's useless when you have splitdebug. Then you might want to rebuild glibc and gnome-vfs with these cflags and features. Point is when you want a proper (complete) backtrace you need to the have the whole stack of librairies your program is using to have debug symbols available. The easiest way to get to this is to have these flags on permanently, but I understand that this might be a little too much just for debugging gthumb for you. just FYI, it's not too much overhead, just taking up disk space and splitdebug feature makes it so that debug symbols doesn't bloat your day to day use of your programs but just popup when needed (more on that in the relevant documentation).
(In reply to comment #12) > hum, first you can remove nostrip from FEATURES, it's useless when you have > splitdebug. Then you might want to rebuild glibc and gnome-vfs with these > cflags and features. > > Point is when you want a proper (complete) backtrace you need to the have the > whole stack of librairies your program is using to have debug symbols > available. > The easiest way to get to this is to have these flags on permanently, but I > understand that this might be a little too much just for debugging gthumb for > you. > > just FYI, it's not too much overhead, just taking up disk space and splitdebug > feature makes it so that debug symbols doesn't bloat your day to day use of > your programs but just popup when needed (more on that in the relevant > documentation). > I re-emerge: USE=debug CFLAGS="${CFLAGS} -g -ggdb" FEATURES="splitdebug" ACCEPT_KEYWORDS=~amd64 emerge -1 glibc glib gtk+ gnome-vfs gthumb but results is same. What's wrong? How to know what libraries it uses?
I've taken advantage of result of the utility ldd and re-emerge libgnome, libgnomeui, libICE, libSM, libbonoboui, libgnomecanvas, even re-emerge fluxbox, but results is same. How to check up, whether there are debug symbols in a executable file?
try readelf -d /usr/bin/gthumb |grep DEBUG
(In reply to comment #15) > try readelf -d /usr/bin/gthumb |grep DEBUG > output: 0x000...0015 (DEBUG) 0x0
Created attachment 130909 [details] libraries if I equery b libgmodule-2.0.so.0: app-emulation/emul-linux-x86-baselibs-10.2 dev-libs/glib-2.12.13 and it is a lot of such libraries.
Ok, my command was wrong, try this : $ readelf -W -a /usr/bin/gthumb|grep -i debug [27] .gnu_debuglink PROGBITS 0000000000000000 0906f4 000014 00 0 0 1 0x0000000000000015 (DEBUG) 0x0 000000000068bce0 0000038a00000007 R_X86_64_JUMP_SLOT 0000000000000000 debug + 0 906: 0000000000000000 357 FUNC GLOBAL DEFAULT UND debug anyway, it looks like you have a 64 bits install with 32 bit compatibility stuff installed. I only have either pure 64 bits or pure 32 bits installs. Try rebuilding all those emul libs as well, maybe that'll get us somewhere.
(In reply to comment #18) > Ok, my command was wrong, try this : > > $ readelf -W -a /usr/bin/gthumb|grep -i debug > [27] .gnu_debuglink PROGBITS 0000000000000000 0906f4 000014 00 > 0 0 1 > 0x0000000000000015 (DEBUG) 0x0 > 000000000068bce0 0000038a00000007 R_X86_64_JUMP_SLOT 0000000000000000 > debug + 0 > 906: 0000000000000000 357 FUNC GLOBAL DEFAULT UND debug > > anyway, it looks like you have a 64 bits install with 32 bit compatibility > stuff installed. I only have either pure 64 bits or pure 32 bits installs. Try > rebuilding all those emul libs as well, maybe that'll get us somewhere. > readelf -W -a /usr/bin/gthumb | grep -i debug [26] .gnu_debuglink PROGBITS 0000000000000000 1c18bb 000014 00 0 0 1 0x0000000000000015 (DEBUG) 0x0 00000000002b9778 000001fa00000007 R_X86_64_JUMP_SLOT 0000000000000000 debug + 0 506: 0000000000000000 447 FUNC GLOBAL DEFAULT UND debug Looks equally. I re-emerge: emerege -1 app-emulation/... app-emulation/emul-linux-x86-baselibs-10.2 app-emulation/emul-linux-x86-compat-1.0-r3 app-emulation/emul-linux-x86-gtklibs-10.0-r1 app-emulation/emul-linux-x86-xlibs-10.0 result is same. :\
You may be having problems because splitdebug needs debugedit to be installed for it to work. Try emerging debugedit, then re-emerging gthumb and it's immediate deps. You should get files in /usr/src/debug/<category>/<package> that contain debug info.
(In reply to comment #20) > You may be having problems because splitdebug needs debugedit to be installed > for it to work. Try emerging debugedit, then re-emerging gthumb and it's > immediate deps. You should get files in /usr/src/debug/<category>/<package> > that contain debug info. > It has not helped, probably it is necessary re-emerge everything, for example Xorg with splitdebug, but on it I while cannot go.
See http://bugzilla.gnome.org/show_bug.cgi?id=476468#c4 , same applies here
(In reply to comment #22) > See http://bugzilla.gnome.org/show_bug.cgi?id=476468#c4 , same applies here > This is my and same bug.
Ok, a few things to be remembered: http://www.gentoo.org/proj/en/qa/backtraces.xml then if the "GLib-GObject-CRITICAL" you have in your backtrace is the first you see, you can try to debug this particular message first with: G_DEBUG="fatal-criticals" gdb --args gthumb and see with upstream to fix this message. This might or might not be related to your specific issue but you have to get started somewhere anyway. Hope this helps.
