GNOME Bugzilla – Bug 452347
crash in Panel: Logining in right after ...
Last modified: 2007-06-29 20:23:15 UTC
Version: 2.18.2 What were you doing when the application crashed? Logining in right after a reboot 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: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Clearlooks Memory status: size: 83582976 vsize: 83582976 resident: 34635776 share: 31547392 rss: 34635776 rss_rlim: 4294967295 CPU usage: start_time: 1183145554 rtime: 45 utime: 37 stime: 8 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 -1208379680 (LWP 2790)] (no debugging symbols found) 0x00c1f402 in __kernel_vsyscall ()
+ Trace 144687
Thread 1 (Thread -1208379680 (LWP 2790))
----------- .xsession-errors (8 sec old) --------------------- localuser:herb being added to access control list SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/2662 Error: permissions error in pam_timestamp_check (gnome-panel:2790): 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 ***