GNOME Bugzilla – Bug 477163
crash in System Log: shutdown
Last modified: 2007-09-15 10:54:41 UTC
Version: 2.18.1 What were you doing when the application crashed? shutdown 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.5-76.fc7 #1 SMP Thu Aug 30 13:47:21 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 37863424 vsize: 37863424 resident: 20267008 share: 15364096 rss: 20267008 rss_rlim: 4294967295 CPU usage: start_time: 1189849689 rtime: 149 utime: 79 stime: 70 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/sbin/gnome-system-log' (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 -1209059616 (LWP 2771)] (no debugging symbols found) 0x0012d402 in __kernel_vsyscall ()
+ Trace 163072
Thread 1 (Thread -1209059616 (LWP 2771))
----------- .xsession-errors (1673 sec old) --------------------- localuser:root being added to access control list SESSION_MANAGER=local/fedora7:/tmp/.ICE-unix/2512 winscard_clnt.c:3349:SCardCheckDaemonAvailability() PCSC Not Running Niet in staat om bureaublad-bestand /usr/share/applications/openoffice.org-1.9-writer.desktop voor paneelstarter : Bestand of map bestaat niet te openen Niet in staat om bureaublad-bestand /usr/share/applications/openoffice.org-1.9-impress.desktop voor paneelstarter : Bestand of map bestaat niet te openen Niet in staat om bureaublad-bestand /usr/share/applications/openoffice.org-1.9-calc.desktop voor paneelstarter : Bestand of map bestaat niet te openen --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 442846 ***