Dies on resume

[Corey Burger]

Gnome-power-manager is dying on resume after a suspend. However if I manually run it after it has crashed on resume, subsequent suspend/resumes do not cause it to crash.

[Daniel Silverstone (dsilvers)]

I have been investigating this and thought I ought to record my findings here.

gnome-power-manager is very resistant to debugging efforts, which is annoying.

If you strace it over a suspend/resume then it D-states

If you run it under gdb then it seems to "exit normally" which is rather strange.

If you run it --no-daemon then it works fine but reports a bizarre warning of:

gpm_hal_suspend: An unknown error occured
org.freedesktop.Hal.Device.SystemPowerManagement.Suspend failed (HAL error)

yet it still suspends, and indeed those messages don't appear until after resume

Unfortunately the harder I attempted to debug, the less and less it crashed for me.

[Daniel Silverstone (dsilvers)]

I believe I have tracked this down somewhat.

On a fresh bootup, gnome-power-manager will have been started with the --sm-disable option (for some reason I have yet to discover)

When started in this way, it will exit when the power button is pressed because it tries to invoke a sessionful logout only to discover it has no connection to the session.

Obviously it shouldn't be receiving a powerbutton event on resume but that is a separate issue

[Corey Burger (corey.burger)]

I can confirm that -sm-disable kills gpm, even when launched manually. Thanks Daniel *hugs*

[Daniel Silverstone (dsilvers)]

Right, so the issue now is to work out why it was launched --sm-disable and how to fix this.

[Daniel Silverstone (dsilvers)]

The latest upload (0.3.4-0ubuntu10) should fix this behavioural mishap