GNOME Bugzilla – Bug 504080
crash in System Log:
Last modified: 2007-12-17 22:33:42 UTC
Version: 2.18.1 What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.8-34.fc7 #1 SMP Thu Nov 22 23:05:33 EST 2007 i686 X Vendor: The X.Org Group X Vendor Release: 6600 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 67149824 vsize: 67149824 resident: 49266688 share: 15323136 rss: 49266688 rss_rlim: 4294967295 CPU usage: start_time: 1197911697 rtime: 3534 utime: 3339 stime: 195 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 -1208564000 (LWP 15854)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 182137
Thread 1 (Thread -1208564000 (LWP 15854))
----------- .xsession-errors (775576 sec old) --------------------- localuser:root being added to access control list SESSION_MANAGER=local/unix:/tmp/.ICE-unix/3116 Unable to open desktop file /usr/share/applications/openoffice.org-1.9-writer.desktop for panel launcher: No such file or directory Unable to open desktop file /usr/share/applications/openoffice.org-1.9-impress.desktop for panel launcher: No such file or directory Unable to open desktop file /usr/share/applications/openoffice.org-1.9-calc.desktop for panel launcher: No such file or directory Window manager warning: Invalid WM_TRANSIENT_FOR window 0x3800037 specified for 0x3800020 (Failed to ). External network device eth2 is not ready. Aborting.. Warning: External interface previously configured not found Warning: External interface previously configured not found Firewall script saved as /etc/firestarter/firewall Adding Firestarter startup hook to /etc/dhclient-exit-hooks Firewall started --------------------------------------------------
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 ***