As mentioned in my previous comment, it still happens if the user has no gnome-power-manager in his session (which worked fine in Feisty). I'm reopening the bug, just to make sure you know about it since I don't know if you want to support that case.
As mentioned in my previous comment, it still happens if the user has no gnome-power-manager in his session (which worked fine in Feisty). I'm reopening the bug, just to make sure you know about it since I don't know if you want to support that case.