GNOME Bugzilla – Bug 444420
crash in Panel:
Last modified: 2007-06-06 10:33:59 UTC
Version: 2.18.1 What were you doing when the application crashed? Distribution: Unknown Gnome Release: 2.18.1 2007-04-11 (Archlinux) BugBuddy Version: 2.18.1 System: Linux 2.6.21-ARCH #1 SMP PREEMPT Fri May 25 18:51:33 CEST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: Echo Memory status: size: 28835840 vsize: 28835840 resident: 16449536 share: 12488704 rss: 16449536 rss_rlim: 4294967295 CPU usage: start_time: 1181075269 rtime: 95 utime: 79 stime: 16 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/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1225279808 (LWP 6408)] (no debugging symbols found) 0xb7fa7410 in __kernel_vsyscall ()
+ Trace 138503
Thread 1 (Thread -1225279808 (LWP 6408))
----------- .xsession-errors --------------------- ** Message: drive = 0 ** Message: volume = 0 Pencere yöneticisi uyarısı: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2a00062 (OpenOffice) Pencere yöneticisi uyarısı: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Pencere yöneticisi uyarısı: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2a00062 (OpenOffice) Pencere yöneticisi uyarısı: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. err:menubuilder:InvokeShellLinker failed to fork and exec wineshelllink err:menubuilder:InvokeShellLinker failed to fork and exec wineshelllink err:menubuilder:InvokeShellLinker failed to fork and exec wineshelllink ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 --------------------------------------------------
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 422966 ***