GNOME Bugzilla – Bug 420419
crash in Power Manager: Loged in from a locked s...
Last modified: 2009-03-04 14:53:28 UTC
What were you doing when the application crashed? Loged in from a locked screen Distribution: Slackware Slackware 10.2.0 Gnome Release: 2.18.0 2007-03-18 (GARNOME) BugBuddy Version: 2.18.0 System: Linux 2.6.19.2 #1 SMP Mon Jan 22 23:19:38 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70100000 Selinux: No Accessibility: Disabled GTK+ Theme: Brushed Icon Theme: nuoveXT-gnome-1.5 Memory status: size: 24281088 vsize: 24281088 resident: 10395648 share: 7507968 rss: 10395648 rss_rlim: 4294967295 CPU usage: start_time: 1174367490 rtime: 48 utime: 40 stime: 8 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/local/gnome2.18/bin/gnome-power-manager' Using host libthread_db library "/lib/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1227012416 (LWP 27266)] 0xb783804e in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 120264
Thread 1 (Thread -1227012416 (LWP 27266))
----------- .xsession-errors (33 sec old) --------------------- /home/edman007/.themes/Brushed/gtk-2.0/gtkrc:484: Unable to locate image file in pixmap_path: "spin.png" /home/edman007/.themes/Brushed/gtk-2.0/gtkrc:488: Background image options specified without filename /home/edman007/.themes/Brushed/gtk-2.0/gtkrc:495: Unable to locate image file in pixmap_path: "spin.png" /home/edman007/.themes/Brushed/gtk-2.0/gtkrc:499: Background image options specified without filename /home/edman007/.themes/Brushed/gtk-2.0/gtkrc:506: Unable to locate image file in pixmap_path: "spin.png" /home/edman007/.themes/Brushed/gtk-2.0/gtkrc:510: Background image options specified without filename /home/edman007/.themes/Brushed/gtk-2.0/gtkrc:517: Unable to locate image file in pixmap_path: "spin.png" /home/edman007/.themes/Brushed/gtk-2.0/gtkrc:521: Background image options specified without filename /home/edman007/.themes/Brushed/gtk-2.0/gtkrc:528: Unable to locate image file in pixmap_path: "spin.png" /home/edman007/.themes/Brushed/gtk-2.0/gtkrc:532: Background image options specified without filename /home/edman007/.themes/Brushed/gtk-2.0/gtkrc:539: Unable to locate image file in pixmap_path: "spin.png" /home/edman007/.themes/Brushed/gtk-2.0/gtkrc:543: Background image options specified without filename /home/edman007/.themes/Brushed/gtk-2.0/gtkrc:550: Unable to locate image file in pixmap_path: "spin.png" /home/edman007/.themes/Brushed/gtk-2.0/gtkrc:554: Background image options specified without filename /home/edman007/.themes/Brushed/gtk-2.0/progressbar_Clearlooks_animated/progressbar_Clearlooks_animated.rc:30: Clearlooks configuration option "progressbarstyle" is not supported and will be ignored. --------------------------------------------------
Could you please run; killall gnome-power-manager gnome-power-manager --verbose --no-daemon And then try to reproduce. Could you then post the last 15 or so lines please. Many thanks for helping to debug this. Richard.
Created attachment 84997 [details] Another backtrace generated by the bug-reporting thing
Created attachment 84998 [details] The console output of the power manager
Well it appears that it happens when hald is not running, I guess there shouldn't be any crash when that happens, but that seems to be the cause. When I started hald it didn't crash, but when hald isn't running it crashes every time I come back from a locked screen.
Ed, that's fantastic. You've given me enough information to pinpoint exactly the problem. I'll work on a fix now and commit to 2-18. Thanks!
Committed to 2-18: 2007-03-20 Richard Hughes <richard@hughsie.com> * src/gpm-hal.c: (gpm_hal_init): Exit on startup if HAL is not running. We can't do anything. * src/gpm-hal.c: (gpm_hal_error_quark), (gpm_hal_clear_suspend_error): * src/gpm-hal.h: Set an error if HAL is not running. Fixes #84997 and lots of duplicates. Many thanks to Ed Martin for the debuging information. You can grab the latest 2-18 code using SVN: svn checkout http://svn.gnome.org/svn/gnome-power-manager/branches/gnome-2-18 gnome-power-manager Please re-open if this does not fix the issue. Thanks again!
*** Bug 420499 has been marked as a duplicate of this bug. ***
*** Bug 420405 has been marked as a duplicate of this bug. ***
*** Bug 420355 has been marked as a duplicate of this bug. ***
*** Bug 420142 has been marked as a duplicate of this bug. ***
*** Bug 420091 has been marked as a duplicate of this bug. ***
*** Bug 419956 has been marked as a duplicate of this bug. ***
*** Bug 419946 has been marked as a duplicate of this bug. ***
*** Bug 419859 has been marked as a duplicate of this bug. ***
*** Bug 419790 has been marked as a duplicate of this bug. ***
*** Bug 419771 has been marked as a duplicate of this bug. ***
*** Bug 419546 has been marked as a duplicate of this bug. ***
*** Bug 419547 has been marked as a duplicate of this bug. ***
*** Bug 419545 has been marked as a duplicate of this bug. ***
*** Bug 419538 has been marked as a duplicate of this bug. ***
*** Bug 419511 has been marked as a duplicate of this bug. ***
*** Bug 419463 has been marked as a duplicate of this bug. ***
*** Bug 419303 has been marked as a duplicate of this bug. ***
*** Bug 419255 has been marked as a duplicate of this bug. ***
*** Bug 419215 has been marked as a duplicate of this bug. ***
*** Bug 419013 has been marked as a duplicate of this bug. ***
*** Bug 418847 has been marked as a duplicate of this bug. ***
*** Bug 418756 has been marked as a duplicate of this bug. ***
*** Bug 418755 has been marked as a duplicate of this bug. ***
*** Bug 418640 has been marked as a duplicate of this bug. ***
*** Bug 418604 has been marked as a duplicate of this bug. ***
*** Bug 417063 has been marked as a duplicate of this bug. ***
*** Bug 416347 has been marked as a duplicate of this bug. ***
*** Bug 416307 has been marked as a duplicate of this bug. ***
*** Bug 416220 has been marked as a duplicate of this bug. ***
*** Bug 415563 has been marked as a duplicate of this bug. ***
*** Bug 414974 has been marked as a duplicate of this bug. ***
*** Bug 414763 has been marked as a duplicate of this bug. ***
*** Bug 414604 has been marked as a duplicate of this bug. ***
*** Bug 413704 has been marked as a duplicate of this bug. ***
*** Bug 413353 has been marked as a duplicate of this bug. ***
*** Bug 410564 has been marked as a duplicate of this bug. ***
*** Bug 420800 has been marked as a duplicate of this bug. ***
*** Bug 420821 has been marked as a duplicate of this bug. ***
*** Bug 420822 has been marked as a duplicate of this bug. ***
*** Bug 421188 has been marked as a duplicate of this bug. ***
*** Bug 420985 has been marked as a duplicate of this bug. ***
*** Bug 420958 has been marked as a duplicate of this bug. ***
*** Bug 420940 has been marked as a duplicate of this bug. ***
*** Bug 420895 has been marked as a duplicate of this bug. ***
*** Bug 420864 has been marked as a duplicate of this bug. ***
*** Bug 420851 has been marked as a duplicate of this bug. ***
*** Bug 420848 has been marked as a duplicate of this bug. ***
*** Bug 421201 has been marked as a duplicate of this bug. ***
*** Bug 421280 has been marked as a duplicate of this bug. ***
*** Bug 421314 has been marked as a duplicate of this bug. ***
*** Bug 421333 has been marked as a duplicate of this bug. ***
*** Bug 421360 has been marked as a duplicate of this bug. ***
*** Bug 421433 has been marked as a duplicate of this bug. ***
*** Bug 421481 has been marked as a duplicate of this bug. ***
*** Bug 421513 has been marked as a duplicate of this bug. ***
*** Bug 421628 has been marked as a duplicate of this bug. ***
*** Bug 421635 has been marked as a duplicate of this bug. ***
*** Bug 421742 has been marked as a duplicate of this bug. ***
*** Bug 421827 has been marked as a duplicate of this bug. ***
*** Bug 421898 has been marked as a duplicate of this bug. ***
*** Bug 421899 has been marked as a duplicate of this bug. ***
*** Bug 421999 has been marked as a duplicate of this bug. ***
*** Bug 422272 has been marked as a duplicate of this bug. ***
*** Bug 510309 has been marked as a duplicate of this bug. ***
I appear to have experienced this bug in version 2.20.2 under Fedora. (See bug 510309.) If the fix was committed to version 2.18, does that mean it didn't work?
yes, thanks for the heads up! reopening.
*** Bug 423795 has been marked as a duplicate of this bug. ***
*** Bug 426878 has been marked as a duplicate of this bug. ***
*** Bug 488223 has been marked as a duplicate of this bug. ***
*** Bug 504581 has been marked as a duplicate of this bug. ***
*** Bug 515398 has been marked as a duplicate of this bug. ***
*** Bug 514219 has been marked as a duplicate of this bug. ***
*** Bug 505512 has been marked as a duplicate of this bug. ***
*** Bug 510885 has been marked as a duplicate of this bug. ***
*** Bug 505254 has been marked as a duplicate of this bug. ***
*** Bug 505235 has been marked as a duplicate of this bug. ***
*** Bug 498097 has been marked as a duplicate of this bug. ***
*** Bug 520020 has been marked as a duplicate of this bug. ***
*** Bug 530893 has been marked as a duplicate of this bug. ***
*** Bug 542897 has been marked as a duplicate of this bug. ***
*** Bug 543447 has been marked as a duplicate of this bug. ***
Thanks for taking the time to report this bug. However, you are using a version that is too old and not supported anymore. GNOME developers are no longer working on that version, so unfortunately there will not be any bug fixes for the version that you use. By upgrading to a newer version of GNOME you could receive bug fixes and new functionality. You may need to upgrade your Linux distribution to obtain a newer version of GNOME. Please feel free to reopen this bug if the problem still occurs with a newer version of GNOME.