GNOME Bugzilla – Bug 450296
crash in Panel: When myPC starts up and ...
Last modified: 2007-06-23 10:49:14 UTC
Version: 2.18.2 What were you doing when the application crashed? When myPC starts up and I(=user) log in with ID & password input, Bug Buddy opens. I don't do anything. Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 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: 38096896 vsize: 38096896 resident: 17719296 share: 14417920 rss: 17719296 rss_rlim: 4294967295 CPU usage: start_time: 1182589726 rtime: 48 utime: 37 stime: 11 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 -1208334624 (LWP 2599)] (no debugging symbols found) 0x00261402 in __kernel_vsyscall ()
+ Trace 143077
Thread 1 (Thread -1208334624 (LWP 2599))
----------- .xsession-errors (11 sec old) --------------------- Creating backend ... Loading x11 FrontEnd module ... GTK Panel of SCIM 1.4.5 Starting SCIM as daemon ... SCIM has been successfully launched. Smart Common Input Method 1.4.5 SESSION_MANAGER=local/bbking:/tmp/.ICE-unix/2495 (gnome-panel:2599): GConf-WARNING **: Directory `/apps/panel/toplevels/bottom_panel_screen1/screen' was not being monitored by GConfClient 0x9e07b58 (gnome-panel:2599): GConf-WARNING **: Directory `/apps/panel/toplevels/top_panel_screen1/screen' was not being monitored by GConfClient 0x9e07b58 (gnome-panel:2599): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed --------------------------------------------------
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 446183 ***