Daniel Gimpelevich wrote: >>> Also, I think the gnome-power-manager package should be changed to >>> default to "nothing" instead, because then, it would still be OK to >>> install after powernowd, [...] >> I think that could be an option. But this way g-p-m would do nothing >> even if powernowd is not installed. > > Only by default; it could still be changed in gconf, which is how it > should be. It's academic anyway, since powernowd is part of the base > system install, rather than some optional add-on.
I agree. >> Reviewing the postrm/-inst scripts I think it might not be at all >> necessary to test for the presence of g-p-m. [...] >> What HAS to be installed for this to work is gconftool-2. > > Again, this does not account for the case where gconftool-2 is installed > after powernowd. Agreed, too. I'd like somebody with some more experience to have a look at this. Also g-p-m is flawed in a way that the settings of the last logged on user wins. This might not be desirable on a multi-user-system. So there are several options: 1) disable all power management in g-p-m. 2) disable power management in g-p-m by default, but let users change it. 3) disable power management in g-p-m only when powernowd is installed, which is tricky to implement because of install order. affects ubuntu/gnome-power-manager ** Also affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New -- [hardy] Regression: powernowd no longer works with some chipsets https://bugs.launchpad.net/bugs/223812 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs