GNOME Bugzilla – Bug 475065
Crash on open
Last modified: 2008-08-29 15:24:57 UTC
Steps to reproduce: 1. Log into gnome 2. Get informed about panel crash 3. Close information 4. Next gnome-panel starts without problem Stack trace: Distribution: Gentoo Base System release 1.12.10 Gnome Release: 2.19.92 2007-09-06 (Gentoo) BugBuddy Version: 2.19.91 System: Linux 2.6.20-beyond2 #7 Thu Sep 6 15:24:24 CEST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Tango Memory status: size: 114085888 vsize: 114085888 resident: 42860544 share: 39329792 rss: 42860544 rss_rlim: 4294967295 CPU usage: start_time: 1189330428 rtime: 50 utime: 37 stime: 13 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-panel' Really redefine built-in command "frame"? (y or n) [answered Y; input not from terminal] Really redefine built-in command "thread"? (y or n) [answered Y; input not from terminal] Really redefine built-in command "start"? (y or n) [answered Y; input not from terminal] Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1226787120 (LWP 17139)] _______________________________________________________________________________ eax:FFFFFE00 ebx:000043A6 ecx:080E350C edx:00000000 eflags:00200246 esi:080E350C edi:00000000 esp:080E3418 ebp:080E3528 eip:B7FC5410 cs:0073 ds:007B es:007B fs:0000 gs:0033 ss:007B o d I t s Z a P c [007B:080E3418]---------------------------------------------------------[stack] 080E3448 : 00 00 00 00 00 00 00 00 - 00 00 00 00 10 35 0E 08 .............5.. 080E3438 : 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................ 080E3428 : F4 6F 12 B7 D5 B5 0C B7 - A6 43 00 00 0C 35 0E 08 .o.......C...5.. 080E3418 : 28 35 0E 08 00 00 00 00 - 0C 35 0E 08 23 0F 1F B7 (5.......5..#... [007B:080E350C]---------------------------------------------------------[ data] 080E350C : 6C 06 07 B7 A6 43 00 00 - FF FF FF FF FF FF FF FF l....C.......... 080E351C : F4 6F 12 B7 00 00 00 00 - A8 35 0E 08 78 35 0E 08 .o.......5..x5.. [0073:B7FC5410]---------------------------------------------------------[ code] 0xb7fc5410 <__kernel_vsyscall+16>: pop %ebp 0xb7fc5411 <__kernel_vsyscall+17>: pop %edx 0xb7fc5412 <__kernel_vsyscall+18>: pop %ecx 0xb7fc5413 <__kernel_vsyscall+19>: ret 0xb7fc5414 <_fini+118848>: nop 0xb7fc5415 <_fini+118849>: nop ------------------------------------------------------------------------------ 0xb7fc5410 in __kernel_vsyscall ()
+ Trace 161484
----------- .xsession-errors --------------------- ** (nm-applet:17196): WARNING **: <WARN> nma_dbus_init(): org.freedesktop.DBus.Error.NoServer raised: Failed to connect to socket /var/run/dbus/system_bus_socket: Connection refused ** (nm-applet:17196): WARNING **: <WARN> nma_dbus_init(): org.freedesktop.DBus.Error.NoServer raised: Failed to connect to socket /var/run/dbus/system_bus_socket: Connection refused error : xmlEncodeEntitiesReentrant : input not UTF-8 encoding error : output conversion failed due to conv error, bytes 0xD1 0x3D 0x31 0x32 I/O error : encoder error Cannot access memory at address 0x0 -------------------------------------------------- Other information: Portage 2.1.3.9 (default-linux/x86/2007.0/desktop, gcc-4.2.0, glibc-2.6.1-r0, 2.6.20-beyond2 i686) System uname: 2.6.20-beyond2 i686 Intel(R) Celeron(R) M processor 1.50GHz Timestamp of tree: Sun, 09 Sep 2007 02:00:01 +0000 distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] app-shells/bash: 3.2_p17-r1 dev-java/java-config: 1.3.7, 2.0.9999 dev-lang/python: 2.4.4-r4, 2.5.1-r2 dev-python/pycrypto: 2.0.1-r6 sys-apps/baselayout: 1.12.10-r4 sys-apps/sandbox: 1.2.18.1 sys-devel/autoconf: 2.13, 2.61-r1 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10 sys-devel/binutils: 2.18 sys-devel/gcc-config: 1.4.0-r2 sys-devel/libtool: 1.5.24 virtual/os-headers: 2.6.22-r2 ACCEPT_KEYWORDS="x86 ~x86" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=pentium-m -mfpmath=sse -pipe -momit-leaf-frame-pointer -ggdb" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/share/X11/xkb" CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf /etc/revdep-rebuild /etc/terminfo /etc/texmf/web2c /etc/udev/rules.d" CXXFLAGS="-O2 -march=pentium-m -mfpmath=sse -pipe -momit-leaf-frame-pointer -ggdb" DISTDIR="/usr/portage/distfiles" FEATURES="distlocks metadata-transfer sandbox sfperms splitdebug unmerge-orphans userfetch userpriv" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo" LANG="en_US.UTF-8" LC_ALL="en_US.UTF-8" LDFLAGS="-Wl,-O1 -Wl,--add-needed" LINGUAS="en_GB en_US pl" MAKEOPTS="-j2" 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" PORTDIR_OVERLAY="/usr/port
Arggggh. This is bug 446183, but happening in latest 2.19. Can you easily reproduce the crash? AFAIK, it only happens when you log in. Do you think you could try running the panel in valgrind to see what's happening?
Oh, and if you can easily reproduce, it'd be interesting to know if this happens with all themes.
It has been reproduced 2 times (I generally have long gnome uptimes). Where can I change what gnome-session starts (to s/gnome-panel/valgrid --leak-check=full/g;). I mean which file (not in GUI). I'm going to check also other themes.
If you didn't save a session, it's in /usr/share/gnome/default.session. Else it's in ~/.gnome2/session (iirc).
Do you by any chance know if gentoo has picked up any Fedora specific panel patches?
I can't see any patch in ebuild so I don't think so.
After appearing twice it hasn't appear any more. I'll provide needed information as soon as I reproduce it.
There is a similar crash on https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/147265 using GNOME 2.20
*** Bug 484281 has been marked as a duplicate of this bug. ***
*** Bug 498052 has been marked as a duplicate of this bug. ***
*** Bug 505303 has been marked as a duplicate of this bug. ***
The bugs duped to bug #505303 have some complete stacktraces, if required.
*** Bug 508674 has been marked as a duplicate of this bug. ***
*** Bug 512697 has been marked as a duplicate of this bug. ***
I can't reproduce it with 2.21.x. I leave it reopened as the duplicates occures,
*** Bug 520158 has been marked as a duplicate of this bug. ***
*** Bug 520247 has been marked as a duplicate of this bug. ***
*** Bug 520940 has been marked as a duplicate of this bug. ***
*** Bug 522359 has been marked as a duplicate of this bug. ***
*** Bug 525243 has been marked as a duplicate of this bug. ***
Since it has been a long time since last dup
*** Bug 536244 has been marked as a duplicate of this bug. ***
*** Bug 540816 has been marked as a duplicate of this bug. ***
*** Bug 547016 has been marked as a duplicate of this bug. ***
*** Bug 547099 has been marked as a duplicate of this bug. ***
*** Bug 547691 has been marked as a duplicate of this bug. ***
*** Bug 547971 has been marked as a duplicate of this bug. ***
*** Bug 547780 has been marked as a duplicate of this bug. ***
*** Bug 549377 has been marked as a duplicate of this bug. ***
Reopening due to dupes.
Folks, this is nearly exactly the same trace as in famous bug 446183. Hence closing as duplicate, feel free to contradict. Using the simple-dup-finder can help. ;-) *** This bug has been marked as a duplicate of 446183 ***