GNOME Bugzilla – Bug 419771
crash in Power Manager: PC was sitting idle. Af...
Last modified: 2007-03-20 21:12:00 UTC
What were you doing when the application crashed? PC was sitting idle. After long enough idle time, display went black. Upon touching the mouse to resume, bug tool popped. Distribution: Fedora release 6.91 (Rawhide) Gnome Release: 2.18.0 2007-03-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.20-1.2997.fc7 #1 SMP Fri Mar 16 22:29:02 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10299901 Selinux: No Accessibility: Disabled GTK+ Theme: Bluecurve Icon Theme: Bluecurve Memory status: size: 64581632 vsize: 64581632 resident: 5861376 share: 4280320 rss: 5861376 rss_rlim: 4294967295 CPU usage: start_time: 1174233035 rtime: 12 utime: 8 stime: 4 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-power-manager' (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 2946)] (no debugging symbols found) 0x005eb402 in __kernel_vsyscall ()
+ Trace 119748
Thread 1 (Thread -1208564000 (LWP 2946))
----------- .xsession-errors (1194 sec old) --------------------- ** (nm-applet:2934): WARNING **: <WARN> hal_net_physdev_cb(): dbus returned an error. (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.Hal was not provided by any .service files You can not run beagle as root. Beagle is designed to run from your own user account. If you want to create multiuser or system-wide indexes, use the beagle-build-index tool. You can override this setting using the beagle-config or beagle-settings tools. (gnome-panel:2912): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GtkMenuShell' (gnome-panel:2912): Gtk-CRITICAL **: gtk_menu_shell_insert: assertion `GTK_IS_MENU_SHELL (menu_shell)' failed error getting update info: Cannot find a valid baseurl for repo: development --------------------------------------------------
*** This bug has been marked as a duplicate of 420419 ***