On Tue, 2006-10-31 at 19:45 +0100, Stefan Seyfried wrote: > On Tue, Oct 31, 2006 at 06:09:01PM +0000, Richard Hughes wrote: > > > Maybe we can even get gnome-power-manager and kpowersave or whatever > > > to look if there is a $INHIBIT file after a suspend attempt and > > > present its content to the user? But that is something for "later", > > > and maybe there are better ways to communicate this error up the > > > caller chain. > > > > Yes, I think for the gnome-power-manager use case it should go back up > > through HAL (which then gives a nice DBUS message) to g-p-m. > > this would probably fit kpowersave (or any other desktop applet that > wants to engage in power management) well, too.
Sure, agreed. > > All hal-system-power-suspend has to do is check the return val of > > pm-suspend and cat an error file to stderr for HAL, or return true for > > success. > > Ok, so we do not even need to take care of the "communicate it back through > HAL" step in pm-utils _now_ (we could later, but it will be easy to get > it working without much effort now), which is IMO great because it gives > us one less thing to worry about. See attached file. I'm sure you guys can do much better. :-) > As you can probably guess, i am not too much into the HAL / dbus / IPC > stuff yet :-) No problem, you and Peter keep doing good things with shell I don't quite understand. :-) Richard.
hal-system-power-suspend
Description: application/shellscript
_______________________________________________ Pm-utils mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/pm-utils
