GNOME Bugzilla – Bug 425417
crash in Panel:
Last modified: 2007-04-02 16:26:00 UTC
Version: 2.18.0 What were you doing when the application crashed? Distribution: Unknown Gnome Release: 2.18.0 2007-03-19 (Archlinux) BugBuddy Version: 2.18.0 System: Linux 2.6.20-ARCH #1 SMP PREEMPT Sat Mar 24 10:51:35 CET 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Tango-Aluminium Memory status: size: 32157696 vsize: 32157696 resident: 20107264 share: 12857344 rss: 20107264 rss_rlim: 4294967295 CPU usage: start_time: 1175494387 rtime: 644 utime: 580 stime: 64 cutime:0 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/opt/gnome/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 -1208359232 (LWP 5526)] (no debugging symbols found) 0xb7fc6410 in __kernel_vsyscall ()
+ Trace 124280
Thread 1 (Thread -1208359232 (LWP 5526))
----------- .xsession-errors (3507 sec old) --------------------- ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ...Too much output, ignoring rest... --------------------------------------------------
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 422662 ***