Re: DBUS signals?

[Bruce Steers <bsteers4@xxxxxxxxx>]

I think of Login1 shutdown signals like Toolkit Mouse event signals.

And the desktop (kde, gnome2, gnome3, etc) as a custom gambas control.

Will the shutdown event fire with that control? Or does the control swallow
that event for it's own purposes and not allow the signal to fire the
normal way up the chain for the programmer to see?  who knows?

I researched Inhibit for a while and found It's like that.
I don't think you can generically handle Inhibit one way (login1) ,it needs
to be programmed desktop specific.

So maybe the system shutdown signal from login1 is being used by the
desktop?
And maybe even if you could detect it it won't work because of the desktops
own use of it.

Are you wanting a generic way for all desktops?
I personally struggled to find any way to do it except for Gnome session
manager inhibit with gnome2 variants.

Benoit is DBus fd type usable now?
I found login1 and i think Desktop.Portal need a file descriptor <fd> type
and that's where i hit a roadblock.
I'm hoping I'm wrong about this and there is a generic way to use Inhibit
it soooo needs adding to the IDE, my IDE inhibitor only works on
MATE/Cinnamon,which is great for me as i'm a MATE fan but it doesn't help
everyone else.


Respects
BruceS



On Fri, 27 Sept 2024 at 05:20, BB <adamnt42@xxxxxxxxx> wrote:

>
> On 27/9/24 9:36 am, Benoît Minisini wrote:
> > Strange... Maybe the system shutdown is too fast to let 'dbus-monitor'
> > or my little program write into its file? What's the point of this
> > signal then, if it does not give any program enough time to do anything?
>
> Generally, shutdown needs to be run with a delay for it to raise the
> signal. So it depends on how your shutdown was initiated.
>
> Also, you may need to use the login1 Inhibit method to give you the time
> needed to do stuff.
>
> regards
>
> b
>
>
>