GNOME Bugzilla – Bug 609438
crash in Panel: none. computer was just ...
Last modified: 2010-02-09 22:12:45 UTC
Version: 2.28.0 What were you doing when the application crashed? none. computer was just handling some ssh connections Distribution: Debian squeeze/sid Gnome Release: 2.28.2 2009-12-18 (Debian) BugBuddy Version: 2.28.0 System: Linux 2.6.29.4 #3 SMP PREEMPT Wed Jul 15 23:34:05 CEST 2009 i686 X Vendor: The X.Org Foundation X Vendor Release: 10704000 Selinux: No Accessibility: Enabled GTK+ Theme: Glider Icon Theme: gnome GTK+ Modules: gnomebreakpad, gail:atk-bridge Memory status: size: 406216704 vsize: 406216704 resident: 327446528 share: 12525568 rss: 327446528 rss_rlim: 18446744073709551615 CPU usage: start_time: 1265215737 rtime: 284002 utime: 224884 stime: 59118 cutime:0 cstime: 69 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-panel' [Thread debugging using libthread_db enabled] 0xb7fe8424 in __kernel_vsyscall ()
+ Trace 220501
Thread 1 (Thread 0xb6c57ad0 (LWP 13242))
Inferior 1 [process 13242] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ----------- .xsession-errors (511704 sec old) --------------------- (firefox-bin:18305): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:18305): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:18305): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:18305): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:18305): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:18305): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:18305): Gdk-WARNING **: XID collision, trouble ahead ...Too much output, ignoring rest... --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance! This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 606700 ***