Le Tue, May 09, 2023 at 08:46:39AM +0200, Landry Breuil a écrit :
> Le Mon, May 08, 2023 at 11:22:28PM +0100, Laurence Tratt a écrit :
> > On Mon, May 08, 2023 at 07:04:10PM +0200, Landry Breuil wrote:
> > 
> > Hello Landry,
> > 
> > >> Installing meta/xfce installs xfce4-screensaver. However,
> > >> xfce4-screensaver seems to have the unfortunate behaviour of messing with
> > >> the user's X screensaver settings, even when the screensaver is disabled
> > >> in XFCE. This caused me a certain amount of head-scratching when my
> > >> `.xsession` loaded `xidle` but no matter what idle times I used, another
> > >> timeout was used -- which, AFAICS, is the timeout set by
> > >> xfce4-screensaver. In other words, `xidle -timeout <n>` did not respect
> > >> `n`, although `xidle` did still run its sub-command (just at a timeout
> > >> other than `n`).
> > > what do you mean by "screensaver is disabled in XFCE" ? process not
> > > running, process running, disabled how/where ?
> > 
> > The screensaver is (was...) not enabled in Settings > Screensaver and I also
> > disabled it in Settings > Session & Startup -- yet, I eventually realised,
> > there always seemed to be an xfce4-screensaver process running. I can't rule
> > out that I did something stupid in some way, but I don't tend to do a great
> > deal of configuration with XFCE.
> 
> can you check whether it's "saved in the session" if you use session
> saving ? grep screensa .cache/sessions/*

other things to check:
- is the screensaver process running at the start of the session, or
  only after suspend/resume ?
- is there smth in xfconf-query -c xfce4-session -p /general/LockCommand
  ? What if you try running whatever xlock program you want there ?

in the session code, there's something that might try to lock the screen
when suspending (cf
https://gitlab.xfce.org/xfce/xfce4-session/-/blob/xfce4-session-4.17.1/xfce4-session/xfsm-shutdown-fallback.c#L334)
(but only if /shutdown/LockScreen xfconf property is true ? it doesnt
seem to exist/be set by default here) which might call xflock4 by
default, which in turns might spawn the screensaver by default.

cf 
https://gitlab.xfce.org/xfce/xfce4-session/-/blob/xfce4-session-4.17.1/xfce4-session/xfce-screensaver.c#L495

as https://gitlab.xfce.org/xfce/xfce4-session/-/issues/149 says, yes
it's a mess :)

Landry

Reply via email to