GNOME Bugzilla – Bug 474293
crash in System Log: I tried to view the log....
Last modified: 2007-09-15 11:42:08 UTC
Version: 2.16.0 What were you doing when the application crashed? I tried to view the log. Not much more that I can do here. Please note, I am very new to Linux. Please provide detailed instructions what to do. Thanks a 1000 Thomas Distribution: Fedora Core release 6 (Zod) Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc) BugBuddy Version: 2.16.0 System: Linux 2.6.22.4-45.fc6 #1 SMP Tue Aug 21 18:29:10 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: Enforcing Accessibility: Disabled Memory status: size: 93978624 vsize: 0 resident: 93978624 share: 0 rss: 56803328 rss_rlim: 0 CPU usage: start_time: 1189099244 rtime: 0 utime: 137 stime: 0 cutime:90 cstime: 0 timeout: 47 it_real_value: 0 frequency: 0 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 -1208387888 (LWP 3954)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 160934
Thread 1 (Thread -1208387888 (LWP 3954))
----------- .xsession-errors --------------------- Reusing existing ksycoca DCOP: unregister 'anonymous-3942' DCOP: unregister 'kbuildsycoca' kdeinit: PID 3942 terminated. kdeinit: Got EXT_EXEC 'kbuildsycoca' from launcher. Could not load library! Trying exec.... DCOP: register 'kbuildsycoca' -> number of clients is now 2 kbuildsycoca running... DCOP: register 'anonymous-3950' -> number of clients is now 3 Reusing existing ksycoca DCOP: unregister 'anonymous-3950' DCOP: unregister 'kbuildsycoca' kdeinit: PID 3950 terminated. ** (bug-buddy:3958): WARNING **: Couldn't load icon for Open Folder --------------------------------------------------
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 364106 ***