GNOME Bugzilla – Bug 496821
crash in Panel:
Last modified: 2007-11-15 14:57:09 UTC
Version: 2.18.3 What were you doing when the application crashed? Distribution: Gentoo Base System release 1.12.10 Gnome Release: 2.18.3 2007-11-14 (Gentoo) BugBuddy Version: 2.18.1 System: Linux 2.6.21-gentoo #44 SMP PREEMPT Wed Nov 14 03:04:15 GMT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled GTK+ Theme: Crux Icon Theme: Crux Memory status: size: 34189312 vsize: 34189312 resident: 10878976 share: 8421376 rss: 10878976 rss_rlim: 4294967295 CPU usage: start_time: 1195069405 rtime: 49 utime: 47 stime: 2 cutime:7 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) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1225811776 (LWP 28979)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 177710
Thread 1 (Thread -1225811776 (LWP 28979))
----------- .xsession-errors --------------------- SESSION_MANAGER=local/localhost:/tmp/.ICE-unix/28760 Not initializing the Gtk-Qt theme engine Not initializing the Gtk-Qt theme engine Not initializing the Gtk-Qt theme engine Window manager warning: Log level 8: g_object_unref: assertion `G_IS_OBJECT (object)' failed Not initializing the Gtk-Qt theme engine Not initializing the Gtk-Qt theme engine Not initializing the Gtk-Qt theme engine Not initializing the Gtk-Qt theme engine Not initializing the Gtk-Qt theme engine Not initializing the Gtk-Qt theme engine --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 356181 ***