GNOME Bugzilla – Bug 419511
crash in Power Manager: I had issued 'yum -y upd...
Last modified: 2007-03-20 21:12:47 UTC
What were you doing when the application crashed? I had issued 'yum -y update' from a terminal as root, it was updating fine, the screen saver (just blank) came on, so I jiggled the cursor to wake it up again, and power manager crashed. 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.2986.fc7 #1 SMP Tue Mar 13 17:11:26 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10299901 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Echo Memory status: size: 48971776 vsize: 48971776 resident: 5910528 share: 4259840 rss: 5910528 rss_rlim: 4294967295 CPU usage: start_time: 1174165755 rtime: 50 utime: 27 stime: 23 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 -1209137440 (LWP 2123)] (no debugging symbols found) 0x003d5402 in __kernel_vsyscall ()
+ Trace 119544
Thread 1 (Thread -1209137440 (LWP 2123))
----------- .xsession-errors (700 sec old) --------------------- (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.Hal was not provided by any .service files ** (nm-applet:2106): 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 ** Message: <info> You are now connected to the wireless network 'Wireless'. ** (nm-applet:2106): 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 --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
*** This bug has been marked as a duplicate of 420419 ***