GNOME Bugzilla – Bug 554788
crash in Panel: Login
Last modified: 2008-10-03 06:26:37 UTC
Version: 2.22.2 What were you doing when the application crashed? Login Distribution: Fedora release 9 (Sulphur) Gnome Release: 2.22.3 2008-07-01 (Red Hat, Inc) BugBuddy Version: 2.22.0 System: Linux 2.6.26.5-45.fc9.i686.debug #1 SMP Sat Sep 20 03:12:10 EDT 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10500000 Selinux: No Accessibility: Disabled GTK+ Theme: Nodoka Icon Theme: Fedora Memory status: size: 60801024 vsize: 60801024 resident: 15790080 share: 11169792 rss: 15790080 rss_rlim: 4294967295 CPU usage: start_time: 1222995898 rtime: 233 utime: 151 stime: 82 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-panel' [Thread debugging using libthread_db enabled] [New Thread 0xb7f3b760 (LWP 2473)] 0x00110416 in __kernel_vsyscall ()
+ Trace 207680
Thread 1 (Thread 0xb7f3b760 (LWP 2473))
Backtrace stopped: frame did not save the PC The program is running. Quit anyway (and detach it)? (y or n) [answered Y; input not from terminal] ----------- .xsession-errors (9 sec old) --------------------- (nautilus:2472): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (gnome-session:2254): Gdk-WARNING **: gdk_xsettings_watch_cb(): Couldn't find window to unwatch DCOPClient::attachInternal. Attach failed Could not open network socket (gnome-panel:2473): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (gnome-panel:2473): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed kbuildsycoca running... warning: the debug information found in "/usr/lib/debug//lib/libgio-2.0.so.0.0.0.debug" does not match "/lib/libgio-2.0.so.0" (CRC mismatch). warning: the debug information found in "/usr/lib/debug/lib/libgio-2.0.so.0.0.0.debug" does not match "/lib/libgio-2.0.so.0" (CRC mismatch). --------------------------------------------------
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 446183 ***