GNOME Bugzilla – Bug 487763
crash in Panel: je ne sais pas
Last modified: 2007-10-18 23:21:53 UTC
Version: 2.20.0.1 What were you doing when the application crashed? je ne sais pas Distribution: Debian lenny/sid Gnome Release: 2.20.0 2007-09-21 (Debian) BugBuddy Version: 2.20.0 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: Clearlooks Icon Theme: gnome Memory status: size: 40103936 vsize: 40103936 resident: 24125440 share: 13099008 rss: 24125440 rss_rlim: 4294967295 CPU usage: start_time: 1192681552 rtime: 374 utime: 316 stime: 58 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 0xb6fcf6b0 (LWP 3462)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 171033
Thread 1 (Thread 0xb6fcf6b0 (LWP 3462))
----------- .xsession-errors --------------------- ** (gdmsetup:3667): DEBUG: Sending command: 'GET_SERVER_DETAILS Standard CHOOSER' ** (gdmsetup:3667): DEBUG: Got response: 'OK false' ** (gdmsetup:3667): DEBUG: Sending command: 'GET_SERVER_DETAILS Standard PRIORITY' ** (gdmsetup:3667): DEBUG: Got response: 'OK 0' ** (gdmsetup:3667): DEBUG: Sending command: 'CLOSE' ** (gdmsetup:3667): DEBUG: Sending command: 'VERSION' ** (gdmsetup:3667): DEBUG: Got response: 'GDM 2.20.0' ** (gdmsetup:3667): DEBUG: Sending command: 'GET_CONFIG greeter/Include :0.0' ** (gdmsetup:3667): DEBUG: Got response: 'OK ' ** (gdmsetup:3667): DEBUG: Sending command: 'CLOSE' ** (gdmsetup:3667): DEBUG: Sending command: 'VERSION' ** (gdmsetup:3667): DEBUG: Got response: 'GDM 2.20.0' ** (gdmsetup:3667): DEBUG: Sending command: 'GET_CONFIG greeter/Include :0.0' ** (gdmsetup:3667): DEBUG: Got response: 'OK ' ** (gdmsetup:3667): DEBUG: Sending command: 'CLOSE' --------------------------------------------------
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 ***