GNOME Bugzilla – Bug 451367
crash in Panel: nada, actualizando Gento...
Last modified: 2007-06-26 21:55:44 UTC
Version: 2.18.1 What were you doing when the application crashed? nada, actualizando Gentoo Distribution: Gentoo Base System release 1.12.9 Gnome Release: 2.18.1 2007-06-25 (Gentoo) BugBuddy Version: 2.18.1 System: Linux 2.6.21.1-c3 #1 Fri Jun 15 16:49:58 WEST 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Crux Icon Theme: Crux Memory status: size: 171925504 vsize: 171925504 resident: 28897280 share: 18251776 rss: 28897280 rss_rlim: 18446744073709551615 CPU usage: start_time: 1182879999 rtime: 2395 utime: 2097 stime: 298 cutime:0 cstime: 8 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-panel' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 47874467910160 (LWP 22279)] 0x00002b8aa2f49ad5 in waitpid () from /lib/libpthread.so.0
+ Trace 143934
Thread 1 (Thread 47874467910160 (LWP 22279))
----------- .xsession-errors (8 sec old) --------------------- Command failed 5 times, aborting. Could not access configuration key <daemon/Greeter=/usr/libexec/gdmlogin> Using compiled in value </usr/libexec/gdmlogin> for <daemon/Greeter=/usr/libexec/gdmlogin> Failed to connect to socket, not sleeping Trying failed command again. Try 2 of 5. Failed to connect to socket, not sleeping Trying failed command again. Try 3 of 5. Failed to connect to socket, not sleeping Trying failed command again. Try 4 of 5. Failed to connect to socket, not sleeping Trying failed command again. Try 5 of 5. Failed to connect to socket, not sleeping Command failed 5 times, aborting. Could not access configuration key <greeter/GlobalFaceDir=/usr/share/pixmaps/faces/> Using compiled in value </usr/share/pixmaps/faces/> for <greeter/GlobalFaceDir=/usr/share/pixmaps/faces/> --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 422966 ***