Bug#1014782: The problem remains
> The DEACTIVATE events I found, that are apparently sent by the Xfce > Power Manager, are not preceeded by xscreensaver-systemd lines, > although other DEACTIVATE lines are, e.g. "inhibited by "chromium"". So > apparently the systemd integration is working, but Xfce isn't using it? Sounds that way! Which is surprising, from reading the code, but not actually a problem, I guess. -- Jamie Zawinski • jwz.org • dnalounge.com
Bug#1014782: The problem remains
On Mon, 20 Feb 2023 16:58:37 -0800 Jamie Zawinski wrote: > If blanking is being inhibited by dbus, the verbose log will look like this: > > xscreensaver-systemd: 16:54:30: inhibited by "firefox-esr" (:1.48) with > "video-playing" cookie "0C765C49" > xscreensaver-systemd: 16:54:30: inhibited by "firefox-esr" since Mon Feb 20 > 16:54:30 2023 > xscreensaver-systemd: 16:54:30: exec: xscreensaver-command --verbose > -deactivate > xscreensaver: 16:54:30: ClientMessage DEACTIVATE: already inactive, resetting > activity time > xscreensaver-command: already inactive, resetting activity time > xscreensaver-systemd: 16:54:32: uninhibited by "firefox-esr" (:1.48) with > "video-playing" cookie "0C765C49" > > If blanking is being inhibited directly, you'll see only the "deactivate" > line. The DEACTIVATE events I found, that are apparently sent by the Xfce Power Manager, are not preceeded by xscreensaver-systemd lines, although other DEACTIVATE lines are, e.g. "inhibited by "chromium"". So apparently the systemd integration is working, but Xfce isn't using it? -- Celejar
Bug#1014782: The problem remains
If blanking is being inhibited by dbus, the verbose log will look like this: xscreensaver-systemd: 16:54:30: inhibited by "firefox-esr" (:1.48) with "video-playing" cookie "0C765C49" xscreensaver-systemd: 16:54:30: inhibited by "firefox-esr" since Mon Feb 20 16:54:30 2023 xscreensaver-systemd: 16:54:30: exec: xscreensaver-command --verbose -deactivate xscreensaver: 16:54:30: ClientMessage DEACTIVATE: already inactive, resetting activity time xscreensaver-command: already inactive, resetting activity time xscreensaver-systemd: 16:54:32: uninhibited by "firefox-esr" (:1.48) with "video-playing" cookie "0C765C49" If blanking is being inhibited directly, you'll see only the "deactivate" line.
Bug#1014782: The problem remains
On Mon, 20 Feb 2023 11:13:58 -0800 Jamie Zawinski wrote: > On Feb 20, 2023, at 9:44 AM, Celejar wrote: > > > > It turns out that the DEACTIVATEs were being sent by the Xfce Power > > Manager's Presentation Mode. I'm not sure I was even aware of that > > mode's existence, but it apparently has a long history of becoming > > turned on without the conscious intention or awareness of the user :) > > Good to know! > > So, it sounds like you were seeing XFCE invoking "xscreensaver-command > -deactivate" directly, is that right? That would have been happening here: > > https://gitlab.xfce.org/xfce/xfce4-power-manager/-/blob/2969f0b1ddb60ccda2989c6da6977ab51c75dfd7/src/xfce-screensaver.c#L122 > > However it looks like that's a fallback, and first it would have tried to > connect to DBus, meaning you should have seen diagnostics from > xscreensaver-systemd instead: > > https://gitlab.xfce.org/xfce/xfce4-power-manager/-/blob/2969f0b1ddb60ccda2989c6da6977ab51c75dfd7/src/xfce-screensaver.c#L233 > > Is xscreensaver-systemd not running for you? It's running: ~$ ps ax | grep xscree 145156 pts/6S 0:35 xscreensaver -v -v -v --log /home/username/xsvr-log 145158 pts/6S 0:00 xscreensaver-systemd --verbose 242602 pts/6S+ 0:00 grep xscree I don't know whether I'm seeing "xscreensaver-command -deactivate" or xscreensaver-systemd diagnostics. Where should I look for these? The xscreensaver log just contains lines of the form: xscreensaver: nn:nn:nn: ClientMessage DEACTIVATE: already inactive, resetting activity time I don't see any mentions of "xscreensaver-command -deactivate" or systemd. Should I be looking somewhere else? Thanks for the help, and thanks for your work on xscreensaver! -- Celejar
Bug#1014782: The problem remains
On Feb 20, 2023, at 9:44 AM, Celejar wrote: > > It turns out that the DEACTIVATEs were being sent by the Xfce Power > Manager's Presentation Mode. I'm not sure I was even aware of that > mode's existence, but it apparently has a long history of becoming > turned on without the conscious intention or awareness of the user :) Good to know! So, it sounds like you were seeing XFCE invoking "xscreensaver-command -deactivate" directly, is that right? That would have been happening here: https://gitlab.xfce.org/xfce/xfce4-power-manager/-/blob/2969f0b1ddb60ccda2989c6da6977ab51c75dfd7/src/xfce-screensaver.c#L122 However it looks like that's a fallback, and first it would have tried to connect to DBus, meaning you should have seen diagnostics from xscreensaver-systemd instead: https://gitlab.xfce.org/xfce/xfce4-power-manager/-/blob/2969f0b1ddb60ccda2989c6da6977ab51c75dfd7/src/xfce-screensaver.c#L233 Is xscreensaver-systemd not running for you? -- Jamie Zawinski • jwz.org • dnalounge.com
Bug#1014782: The problem remains
On Sun, 19 Feb 2023 10:21:48 +0100 Tormod Volden wrote: > On Fri, Feb 17, 2023 at 5:48 PM Celejar wrote: > > Sorry - I just saw this. I'm currently on 6.06 (Sid package). The > > "Preview" button is currently working, but the screensaver isn't > > activating on its own. I started it with logging enabled, and I see > > regular deactivate events like the following logged every 20 seconds: > > > > ClientMessage DEACTIVATE: already inactive, resetting activity time > > > > I saw this: > > > > https://www.jwz.org/xscreensaver/faq.html#no-blank > > > > I guess I have to figure out what application is sending these messages? > > Firefox? I do tend to keep a lot of tabs open. > > Yes, try freezing Firefox and see if those DEACTIVATEs stop. I use It turns out that the DEACTIVATEs were being sent by the Xfce Power Manager's Presentation Mode. I'm not sure I was even aware of that mode's existence, but it apparently has a long history of becoming turned on without the conscious intention or awareness of the user :) https://bugzilla.xfce.org/show_bug.cgi?id=14210 > this script when I need to save laptop battery, it might come handy > here: ... Thank you! > BTW, if you keep many tabs open, I can recommend the Auto Tab Discard > extension! Thanks - I think I've tried it in the past, but I don't currently have it installed. Perhaps I'll give it another try. Thanks again for the help. -- Celejar
Bug#1014782: The problem remains
On Fri, Feb 17, 2023 at 5:48 PM Celejar wrote: > Sorry - I just saw this. I'm currently on 6.06 (Sid package). The > "Preview" button is currently working, but the screensaver isn't > activating on its own. I started it with logging enabled, and I see > regular deactivate events like the following logged every 20 seconds: > > ClientMessage DEACTIVATE: already inactive, resetting activity time > > I saw this: > > https://www.jwz.org/xscreensaver/faq.html#no-blank > > I guess I have to figure out what application is sending these messages? > Firefox? I do tend to keep a lot of tabs open. Yes, try freezing Firefox and see if those DEACTIVATEs stop. I use this script when I need to save laptop battery, it might come handy here: : killall -STOP firefox killall -STOP Isolated\ Web\ Con killall -STOP Isolated\ Service killall -STOP Privileged\ Cont killall -STOP WebExtensions killall -STOP Web\ Content echo press enter to resume read dummy killall -CONT Web\ Content killall -CONT WebExtensions killall -CONT Privileged\ Cont killall -CONT Isolated\ Service killall -CONT Isolated\ Web\ Con killall -CONT firefox BTW, if you keep many tabs open, I can recommend the Auto Tab Discard extension! > If you think the log may contain more useful information, I'm happy to > attach it. Unless there is something there to identify the offender, and I guess you already checked, I don't think the full log helps. Tormod
Bug#1014782: The problem remains
On Fri, 27 Jan 2023 22:40:17 +0100 Tormod Volden wrote: > OK. Maybe you can try 6.06, it is in salsa but is awaiting sponsoring > and uploading. In any case, please attach the verbose log from > xscreensaver -v -v -v -log your.log > > I am not able to reproduce the issue. > > Tormod Sorry - I just saw this. I'm currently on 6.06 (Sid package). The "Preview" button is currently working, but the screensaver isn't activating on its own. I started it with logging enabled, and I see regular deactivate events like the following logged every 20 seconds: ClientMessage DEACTIVATE: already inactive, resetting activity time I saw this: https://www.jwz.org/xscreensaver/faq.html#no-blank I guess I have to figure out what application is sending these messages? Firefox? I do tend to keep a lot of tabs open. If you think the log may contain more useful information, I'm happy to attach it. -- Celejar
Bug#1014782: The problem remains
OK. Maybe you can try 6.06, it is in salsa but is awaiting sponsoring and uploading. In any case, please attach the verbose log from xscreensaver -v -v -v -log your.log I am not able to reproduce the issue. Tormod
Bug#1014782: The problem remains
Hello, Just for the record, I want to report that I'm still experiencing the problem I reported in my original report. My /usr/lib/X11 is empty. -- Celejar
