GNOME Bugzilla – Bug 498888
crash in System Log: rebooting, sometime dur...
Last modified: 2007-11-24 17:41:14 UTC
Version: 2.18.1 What were you doing when the application crashed? rebooting, sometime during run my desktop icons disappeared Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 42299392 vsize: 42299392 resident: 24395776 share: 15376384 rss: 24395776 rss_rlim: 4294967295 CPU usage: start_time: 1195695963 rtime: 171 utime: 159 stime: 12 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/sbin/gnome-system-log' (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 -1208461600 (LWP 19429)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 179196
Thread 1 (Thread -1208461600 (LWP 19429))
----------- .xsession-errors (109 sec old) --------------------- ** (yelp:2892): WARNING **: failure: no device event controller found. (yelp:2892): Bonobo-CRITICAL **: bonobo_object_corba_objref: assertion `BONOBO_IS_OBJECT (object)' failed (gnome-help:12962): Bonobo-CRITICAL **: bonobo_object_corba_objref: assertion `BONOBO_IS_OBJECT (object)' failed The program 'gtk-window-decorator' received an X Window System error. This probably reflects a bug in the program. The error was 'BadLength (poly request too large or internal Xlib length erro'. (Details: serial 173734 error_code 16 request_code 155 minor_code 34) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) --------------------------------------------------
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 442846 ***