GNOME Bugzilla – Bug 499684
crash in System Log: After logging in as root...
Last modified: 2007-12-01 09:02:39 UTC
Version: 2.18.0 What were you doing when the application crashed? After logging in as root when i tried to open system log using system->administrator->systemlog menu it got crashed Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 34537472 vsize: 34537472 resident: 11739136 share: 8839168 rss: 11739136 rss_rlim: 4294967295 CPU usage: start_time: 1196099534 rtime: 23 utime: 19 stime: 4 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 -1208969504 (LWP 2808)] (no debugging symbols found) 0x00859402 in __kernel_vsyscall ()
+ Trace 179661
Thread 1 (Thread -1208969504 (LWP 2808))
----------- .xsession-errors (37 sec old) --------------------- localuser:root being added to access control list SESSION_MANAGER=local/webserver:/tmp/.ICE-unix/2541 ** (gnome-session:2541): WARNING **: Host name lookup failure on localhost. ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name 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 0x4d specified for 0xc005c6 (). --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 364106 ***