Well, I'm confused about how it got from "blanking" to "unblanking" without
printing why active_at changed. Please try logging with -vvv -log to make sure
it's printing everything.
--
Jamie Zawinski https://www.jwz.org/ https://www.dnalounge.com/
Here's a log of the screen blanking after unactivity, then
spontaneously unblanking (it was not locked) with 6.02. I was nowhere
near the mouse or the keyboard at that time.
xscreensaver: 16:54:33: checking init file
xscreensaver: 16:54:40: XI RawKeyRelease
xscreensaver: 16:54:44: XI
On Thu, Nov 18, 2021 at 01:00:52PM -0800, Jamie Zawinski wrote:
> I don't understand why you are having trouble logging with 6.02. Did
> you launch it as xscreensaver -v -log log.txt?
I was running it without the "-v". Trying again with 6.02
I don't understand why you are having trouble logging with 6.02. Did you launch
it as xscreensaver -v -log log.txt?
Investigating this in 5.x will not be helpful, because the flow of control is
completely different with 6.x's new security model.
On Sun, Nov 07, 2021 at 10:39:46AM -0800, Jamie Zawinski wrote:
> On Nov 7, 2021, at 10:31 AM, Lionel Élie Mamane wrote:
>> I reproduced the issue with 5.45 and more patience, on the scale of
>> ten minutes. The attached log file is from 5.45 and contains at least
>> two occurrences, about 10
I reproduced the issue with 6.02 and more patience, too, but it
doesn't log anything. I locked the screen, and at 20:01 it
spontaneously turned on again, and the XScreenSaver login screen
appeared. At 20:15 I moved the mouse and unlocked (entering my
password), and ran "xscreensaver-command
On Nov 7, 2021, at 10:31 AM, Lionel Élie Mamane wrote:
>
>> I couldn't immediately reproduce the behaviour I as complaining
>> about within a few minutes, also not with 5.45. (...) I will make
>> longer (e.g. overnight) tests.
>
> I reproduced the issue with 5.45 and more patience, on the scale
> I couldn't immediately reproduce the behaviour I as complaining
> about within a few minutes, also not with 5.45. (...) I will make
> longer (e.g. overnight) tests.
I reproduced the issue with 5.45 and more patience, on the scale of
ten minutes. The attached log file is from 5.45 and contains
On Mon, Oct 25, 2021 at 12:51:30PM -0700, Jamie Zawinski wrote:
> First, upgrade to 6.02. Then, run xscreensaver with -log to see
> what's going on. Probably some other app is trying to disable
> blanking while locked.
Version 6.02 compiled directly from sources doesn't immediately turn
off the
On Mon, Oct 25, 2021 at 12:51:30PM -0700, Jamie Zawinski wrote:
> First, upgrade to 6.02.
I see it is not yet packaged for Debian; will try to schedule building
it from sources sometime soon.
> xscreensaver-systemd is also the mechanism by which most movie
> players and web browsers tell
First, upgrade to 6.02. Then, run xscreensaver with -log to see what's going
on. Probably some other app is trying to disable blanking while locked.
> Killing the "xscreensaver-systemd" process fixed it. Being an
> always-running desktop, it is never suspended, so from reading its man
> page, I
Package: xscreensaver
Version: 5.45+dfsg1-2
Severity: important
I took the habit of running "xscreensaver-command -suspend" when
leaving my desk. However, after ten(s of) seconds, xscreensaver
unblanks and shows the password prompt screen. After timeout, it
blanks again, and after some time,
12 matches
Mail list logo
