Description of problem: gnome-power-manager crashes at every startup. Version-Release number of selected component (if applicable): gnome-power-manager-2.17.2.1-1.fc7 How reproducible: Every time Steps to Reproduce: 1. run 'gnome-power-manager' 2. 3. Actual results: Expected results: Additional info:
Created attachment 140402 [details] Bug report from crash
When this happens, haldaemon (hal-0.5.8.1-4.fc6) seems to crash.
I got it to work again by moving the existing ~/.gconf/apps/gnome-power-manager directory out of the way. Running g-p-m creates a new one. Here is diff output of 'new' against 'old': [tbl@localhost apps]$ diff gnome-power-manager ../gnome-power-manager diff gnome-power-manager/%gconf.xml ../gnome-power-manager/%gconf.xml 3,4c3 < <entry name="display_icon_policy" mtime="1162753313" type="string"> < <stringvalue>always</stringvalue> --- > <entry name="enable_pcskr_beeping" mtime="1162168018" type="bool" value="false"> 6,8c5 < <entry name="enable_pcskr_beeping" mtime="1162753305" type="bool" value="false"> < </entry> < <entry name="action_ups_low" mtime="1162753305" type="string"> --- > <entry name="action_ups_low" mtime="1162168018" type="string"> 11c8 < <entry name="action_ups_critical" mtime="1162753305" type="string"> --- > <entry name="action_ups_critical" mtime="1162168018" type="string"> 14c11 < <entry name="action_battery_critical" mtime="1162753305" type="string"> --- > <entry name="action_battery_critical" mtime="1162168018" type="string"> 17c14 < <entry name="use_lowpower_battery" mtime="1162753305" type="bool" value="true"> --- > <entry name="use_lowpower_battery" mtime="1162168018" type="bool" value="true"> 19,20c16,17 < <entry name="action_battery_button_lid" mtime="1162753305" type="string"> < <stringvalue>blank</stringvalue> --- > <entry name="action_battery_button_lid" mtime="1162168018" type="string"> > <stringvalue>suspend</stringvalue> 22,23c19,20 < <entry name="action_button_suspend" mtime="1162753305" type="string"> < <stringvalue>nothing</stringvalue> --- > <entry name="action_button_suspend" mtime="1162168018" type="string"> > <stringvalue>suspend</stringvalue> 25c22 < <entry name="action_button_power" mtime="1162753305" type="string"> --- > <entry name="action_button_power" mtime="1162168018" type="string"> 34c31 < <entry name="display_state_change" mtime="1162753305" type="bool" value="true"> --- > <entry name="display_state_change" mtime="1162168018" type="bool" value="true"> 36c33 < <entry name="display_dim_on_idle" mtime="1162753305" type="bool" value="true"> --- > <entry name="display_dim_on_idle" mtime="1162168018" type="bool" value="true"> 40,41c37,38 < <entry name="action_battery_sleep_type" mtime="1162753305" type="string"> < <stringvalue>nothing</stringvalue> --- > <entry name="action_battery_sleep_type" mtime="1162168017" type="string"> > <stringvalue>suspend</stringvalue> 43c40 < <entry name="action_ac_sleep_type" mtime="1162753305" type="string"> --- > <entry name="action_ac_sleep_type" mtime="1162168017" type="string"> 46,47c43,44 < <entry name="action_ac_button_lid" mtime="1162753305" type="string"> < <stringvalue>blank</stringvalue> --- > <entry name="action_ac_button_lid" mtime="1162168018" type="string"> > <stringvalue>suspend</stringvalue> [tbl@localhost apps]$
Created attachment 140407 [details] Another crash bug report Sorry, next reboot reproduces original problem: g-p-m crashes. dump looks about the same (attached), and haldaemon is dead.
Booting again with the power cord pulled and with battery at 95% both haldaemon and g-p-m are running..... Above aborts were with power cord inserted and with battery at 100%. Probably pulling at straws, but .....
Thanks Tom. Could you install the debuginfo files for both HAL and gnome-power-manager please, and try to get the segfault again. Many thanks. Richard,
I installed the debuginfo packages, and of course, first reboot didn't produce the crash.... sigh.
Created attachment 140427 [details] debuginfo bug report of g-p-m crashing on gdm startup I think I got one with debuginfo.... Bug buddy report attached.....
I ran 'gdb hald' (and run --daemon=no), and after it settled, I ran 'gnome-power-manager' in another window. Got this from gdb/hald: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1208088896 (LWP 3972)] 0x4edecc88 in strcmp () from /lib/libc.so.6 (gdb) (gdb) (gdb) (gdb) (gdb) (gdb) where #0 0x4edecc88 in strcmp () from /lib/libc.so.6 #1 0x0805cc6f in hald_dbus_filter_handle_methods (connection=0x96cbf30, message=0x96cc000, user_data=0x0, local_interface=0) at hald_dbus.c:3822 #2 0x0805d38b in hald_dbus_filter_function (connection=0x96cbf30, message=0x96cc000, user_data=0x0) at hald_dbus.c:3934 #3 0x4fac34cb in dbus_connection_dispatch () from /lib/libdbus-1.so.3 #4 0x4fca5cfd in dbus_server_setup_with_g_main () from /usr/lib/libdbus-glib-1.so.2 #5 0x4ef532d2 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #6 0x4ef562af in g_main_context_check () from /lib/libglib-2.0.so.0 #7 0x4ef56659 in g_main_loop_run () from /lib/libglib-2.0.so.0 #8 0x08055fce in main (argc=2, argv=0xbfc65f84) at hald.c:582 #9 0x4ed96e5c in __libc_start_main () from /lib/libc.so.6 #10 0x0804c341 in _start () (gdb)
Cool, thanks for that, that's 600% better to debug :-) You're not running the latest DBUS are you? Richard.
Created attachment 140478 [details] Another crash bug report from bug buddy (not sure if it is different) Attaching another crash report. I am running (believe latest dbus): dbus-devel-0.95-1.fc7 dbus-0.95-1.fc7 dbus-sharp-0.63-6.fc6 dbus-x11-0.95-1.fc7 dbus-glib-0.71-1.fc7 dbus-glib-devel-0.71-1.fc7 dbus-python-0.70-6 I see there are newer dbus-glib and dbus-glib-devel in today's updates (0.71-2.fc7); I'll install them now ...
please see also bug 214027 this problem doesn't happen in dbus-0.94-1.fc7.
No joy. I created /var/lib/dbus, and now /var/lib/dbus/machine-id gets created (and no boot time message), but the other symptoms are the same: haldaemon/g-p-m crashes. I have /etc/dbus-1/machine-id, but it hasn't been touched since 25 October. Richard, you want me to revert to dbus-0.94-1.fc7 or leave as is for debugging?
Tom, if you are running over DBUS 0.94 you'll need the HAL patches merged into CVS about a week ago. See http://lists.freedesktop.org/archives/hal/2006-November/006464.html Richard.
I'd just like to confirm that I'm getting the same thing as Tom with todays Rawhide. I didn't get it yesterday, so I guess it has to be dbus (as it's the only thing that seems relevant in what was updated). Any way to provide any more useful information?
Created attachment 140947 [details] gnome-power-manager backtrace
I'm experiencing the same indications as the OP. Comment #16 contains a backtrace with debuginfo packages installed.
With today's rawhide (hal 0.5.8.1-6.fc7) everything seems to work fine for me again.