GNOME Bugzilla – Bug 489870
crash in Panel: I've just booting my com...
Last modified: 2007-10-28 15:10:10 UTC
Version: 2.20.0.1 What were you doing when the application crashed? I've just booting my computer, i would setup the clockwhen the bug appears.. Distribution: Debian lenny/sid Gnome Release: 2.20.0 2007-09-21 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-2-686 #1 SMP Fri Aug 31 00:24:01 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400000 Selinux: No Accessibility: Disabled GTK+ Theme: ClearlooksClassic Icon Theme: Mist Memory status: size: 47161344 vsize: 47161344 resident: 20852736 share: 12869632 rss: 20852736 rss_rlim: 4294967295 CPU usage: start_time: 1193031528 rtime: 131 utime: 110 stime: 21 cutime:0 cstime: 0 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/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6fc56b0 (LWP 3333)] [New Thread 0xb606cb90 (LWP 3418)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 172582
Thread 1 (Thread 0xb6fc56b0 (LWP 3333))
----------- .xsession-errors (14 sec old) --------------------- http://www.gtk.org/setuid.html Refusing to initialize GTK+. /etc/gdm/Xsession: Beginning session setup... SESSION_MANAGER=local/debian:/tmp/.ICE-unix/3276 Conky: forked to background, pid is 3346 Conky: desktop window (188) is root window Conky: window type - normal Conky: drawing to created window (1400001) Conky: drawing to double buffer Openbox-Message: Impossible de trouver un fichier de menus valide 'debian-menu.xml' Initializing nautilus-open-terminal extension Initializing gnome-mount extension --------------------------------------------------
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 476299 ***