expanding the inhibit spec
Bastien Nocera
hadess at hadess.net
Thu Jan 9 05:13:43 PST 2014
On Thu, 2014-01-09 at 13:50 +0100, Lennart Poettering wrote:
> On Wed, 08.01.14 09:48, Ryan Lortie (desrt at desrt.ca) wrote:
>
> >
> > hi,
> >
> > On Wed, Jan 8, 2014, at 6:28, Simon McVittie wrote:
> > > Having implemented "delay logout until we've tried to disconnect IM
> > > connections" in telepathy-mission-control, in terms of the logind API
> > > (which only has Inhibit and PrepareToSleep), I'm not sure that a
> > > separate Delay API is really needed.
> >
> > As I mentioned before, I'm concerned that not everyone will be using
> > logind.
> >
> > That said, delay-before-suspend is sort of a separate thing from
> > Inhibit, and I'm not sure I want to support it at all in the API I
> > propose, so my concerns about "able to do all kinds of inhibit from one
> > place" don't necessarily apply here.
> >
> > This would still land us in a place that means that those who want to do
> > tasks before suspend could only do it on logind systems. I don't really
> > consider that to be a substantial problem (particularly because
> > non-logind systems may not even have this ability to begin with), but I
> > guess it would be nice to have a more generic mechanism for that as
> > well... one day...
>
> So, let's turn this around: which operations precisely do you want to
> cover here, and in which modes?
>
> You only want blocking locks, and you want to cover
> suspending/hibernation, and the screenlock, and ...?
The listed inhibit flags in GtkApplication are here:
https://developer.gnome.org/gtk3/stable/GtkApplication.html#GtkApplicationInhibitFlags
Cheers
More information about the xdg
mailing list