Daniel Moerner wrote: > Independent of the correct solution, something needs to be done to fix > this bug in the interim while the decision is made between system > groups, libpam-foreground, and consolekit. This bug pretty clearly > breaks kpowersave's functionality, without any error message, and > without any warning. > > I suggest that at the very least we should include a README.Debian > that explains potential solutions to this problem, like adding the > user to powerdev, so the user can decide on their own method around > this problem until Debian decides on a more long-term fix. >
This problem is not kpowersave specific. Other programs, like gnome-power-manager or guidance-power-manager have the same issue (as they use hal via dbus for suspend,hibernate) (The same is true for other programs using dbus system services, like network-manager-(gnome,kde)). So we should best look for solving this problem system wide. Adding a README.Debian to kpowersave will surely not harm, but I doubt it will help much As a side note, the hal package already has a README.Debian which explains the necessary steps. One approach we took for etch (and subsequently lenny), is that the installer automatically adds the user, that is created during installation, to all those groups. This obviously doesn't help when you are upgrading existing installations and the group based approach has scalability problems anyways. That's why the alternative approach, via consolekit, was implemented (libpam-foreground is dead, there is no use to further persue this way). I already asked for inclusion into the standard desktop tasks http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=496723 Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
