| Summary: | [gnome-overlay] gnome-extra/gnome-power-manager-2.26.1 fails to detect battery | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Edgardo Rossetto <erossetto> |
| Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
| Status: | RESOLVED NEEDINFO | ||
| Severity: | critical | CC: | chrmag, follettoonip, mrpouet, wolf31o2 |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | Output of gnome-power-bugreport.sh | ||
|
Description
Edgardo Rossetto
2009-05-18 02:16:33 UTC
It seems GPM does indeed detect the battery, but still crashes upon start. Created attachment 191606 [details]
Output of gnome-power-bugreport.sh
You report is not entirely clear. Does gnome-power-manager crash (terminate) when you run it? If so, could you please provide a backtrace as described in: http://www.gentoo.org/proj/en/qa/backtraces.xml It does not terminate, it shows the warnings and the battery tab is missing ** (gnome-power-manager:3440): WARNING **: Error invoking GetAll() to get properties: Failed to execute program /usr/libexec/dbus-daemon-launch-helper: Success I already had this problem, and the battery section was not display too. I solved it by re-emerging DBus, apparently seems to be a SETUID bit problem but i'm not sure (if a dev from freedesktop herd can confirm please), after re-emerged it all worked perfectly. can you try ? please try suggestion from bug #5. It sounds like the dbus permissive issue again. re-emerging dbus-related packages solved for me. My gpm could'n show hibernate and suspend options I've just re-installed my pc and I have the same problem with gnome-power-manager-2.28.1 Re-emerging dbus didn't solve the problem. But it solves this issue: http://bugs.gentoo.org/show_bug.cgi?id=222551 /usr/libexec/dbus-daemon-launch-helper couldn't be executed because its rights are set to -rws--x--- and it was run by the user (which isn't in the messagebus group). To fix this issue, I did: # chmod o+x /usr/libexec/dbus-daemon-launch-helper |