GNOME Bugzilla – Bug 466834
crash in Panel: Just turned on the compu...
Last modified: 2007-09-02 13:03:24 UTC
Version: 2.18.3 What were you doing when the application crashed? Just turned on the computer, then logged into the desktop, and the bug reporting tool came up reporting a crash. Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Bluecurve-Slate Icon Theme: Echo Memory status: size: 100397056 vsize: 100397056 resident: 41918464 share: 38735872 rss: 41918464 rss_rlim: 4294967295 CPU usage: start_time: 1187143435 rtime: 83 utime: 65 stime: 18 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-panel' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1209043232 (LWP 2626)] 0x00110402 in __kernel_vsyscall ()
+ Trace 155297
Thread 1 (Thread -1209043232 (LWP 2626))
----------- .xsession-errors (25 sec old) --------------------- localuser:elliot being added to access control list SESSION_MANAGER=local/medusa:/tmp/.ICE-unix/2497 winscard_clnt.c:3349:SCardCheckDaemonAvailability() PCSC Not Running (gnome-panel:2626): 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 ***