GNOME Bugzilla – Bug 450499
crash in Panel: Nothing. I've little to ...
Last modified: 2007-06-24 10:23:17 UTC
Version: 2.18.2 What were you doing when the application crashed? Nothing. I've little to no idea what exactaly crashed. Distribution: Unknown Gnome Release: 2.18.2 2007-05-31 (Archlinux) BugBuddy Version: 2.18.1 System: Linux 2.6.21-ARCH #1 SMP PREEMPT Mon Jun 11 23:47:51 CEST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 26214400 vsize: 26214400 resident: 15798272 share: 11440128 rss: 15798272 rss_rlim: 4294967295 CPU usage: start_time: 1182642435 rtime: 554 utime: 481 stime: 73 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 -1225110832 (LWP 6468)] (no debugging symbols found) 0xb7f08410 in __kernel_vsyscall ()
+ Trace 143240
Thread 1 (Thread -1225110832 (LWP 6468))
----------- .xsession-errors (323 sec old) --------------------- konqueror: WARNING: Can't open /home/froob/.kde/share/apps/konqueror/bookmarks.xml Window manager warning: Invalid WM_TRANSIENT_FOR window 0x44 specified for 0x10023b3 (). ** Message: drive = 0 ** Message: volume = 0 Window manager warning: Invalid WM_TRANSIENT_FOR window 0x44 specified for 0x1003aa2 (). Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2000040 (Desktop Se) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 --------------------------------------------------
*** Bug 450517 has been marked as a duplicate of this bug. ***
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 422966 ***