GNOME Bugzilla – Bug 420661
crash in Panel: lauching xterm
Last modified: 2007-03-26 08:54:02 UTC
Version: 2.18.0 What were you doing when the application crashed? lauching xterm Distribution: Debian 4.0 Gnome Release: 2.18.0 2007-03-17 (GARNOME) BugBuddy Version: 2.18.0 System: Linux 2.6.20.2-kvm #1 SMP PREEMPT Sat Mar 10 12:13:35 CET 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Enabled GTK+ Theme: Glossy Icon Theme: gnome Memory status: size: 32104448 vsize: 32104448 resident: 22110208 share: 12673024 rss: 22110208 rss_rlim: 4294967295 CPU usage: start_time: 1174417696 rtime: 118 utime: 109 stime: 9 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/home/dzen/garnome/bin/gnome-panel' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1225815232 (LWP 7478)] 0xb7fc3792 in ?? () from /lib/ld-linux.so.2
+ Trace 120455
Thread 1 (Thread -1225815232 (LWP 7478))
----------- .xsession-errors --------------------- *** CLB *** Initializing Google Browser Sync... *** CLB *** Instanciating core objects... *** CLB *** Registering with XPCOM... *** CLB *** Adding categories... *** CLB *** Google Browser Sync initialized succesfully! GTK Accessibility Module initialized Bonobo accessibility support initialized GTK Accessibility Module initialized Bonobo accessibility support initialized GTK Accessibility Module initialized Bonobo accessibility support initialized GTK Accessibility Module initialized Bonobo accessibility support initialized GTK Accessibility Module initialized Bonobo accessibility support initialized --------------------------------------------------
unique 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. Thanks in advance!
Thanks for the bug report. 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 413921 ***