gnome-power-manager crashes on AC unplug

Bug #367771 reported by Florian Echtler
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-power-manager (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Hi everyone, I've just upgraded my Acer Aspire One L110 to Jaunty Jackalope, and now my gnome-power-manager applet reliably crashes when I unplug the AC power. Running it with --verbose doesn't give any useful information. I can restart it, and it works also when I reattach the power - until I remove it again.

1. Ubuntu version is 9.04
2. g-p-m version is 2.24.2-2ubuntu8.
3. expected g-p-m to keep running
4. g-p-m quit unexpectedly

UPDATE: I've tried debugging with --no-daemon, and now I'm getting something useful:

TI:09:23:31 TH:0x918c640 FI:gpm-cell.c FN:hal_device_property_modified_cb,273
 - udi=/org/freedesktop/Hal/devices/computer_power_supply_battery_BAT1, key=battery.charge_level.current, added=0, removed=0, finally=0
TI:09:23:31 TH:0x918c640 FI:gpm-cell.c FN:hal_device_property_modified_cb,273
 - udi=/org/freedesktop/Hal/devices/computer_power_supply_battery_BAT1, key=battery.reporting.current, added=0, removed=0, finally=0
TI:09:23:31 TH:0x918c640 FI:gpm-cell.c FN:hal_device_property_modified_cb,273
 - udi=/org/freedesktop/Hal/devices/computer_power_supply_battery_BAT1, key=battery.voltage.current, added=0, removed=0, finally=1
E: socket-client.c: socket(): Address family not supported by protocol
Segmentation fault

I suppose that the "address family not supported" error is caused by the custom kernel I'm running; however, g-p-m should handle that gracefully, as I've used the same kernel in Intrepid without problems.

Florian

UPDATE 2: I've just checked this with the stock 2.6.28-11 kernel, and while the socket() error is gone, g-p-m still crashes at the same point.

Florian Echtler (floe)
description: updated
Revision history for this message
Chris Coulson (chrisccoulson) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.
If you are using Kubuntu or Xubuntu you can file the crash using /usr/share/apport/apport-qt --crash-file=/var/crash/_my_crash_report.crash in a terminal - where _my_crash_report.crash is the crash you would like to report.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

Changed in gnome-power-manager (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.