[arch-general] Screen lock stopped working
I've noticed that my screen lock / screensaver has stopped engaging as of a couple of days ago. I check the settings (which I haven't changed recently), but they seem to be set correctly. Anyone have an idea what package upgrade might have caused this and/or which bugs I should watch for a resolution? I'm running XFCE desktop btw. Thanks, DR
On Fri, 16 Sep 2016 12:14:30 -0400, David Rosenstrauch wrote:
I'm running XFCE desktop btw.
On Arch Linux using Xfce not necessarily explains what screen lock / screensaver you are using.
On Sun, Sep 18, 2016 at 1:22 AM, Ralf Mardorf <silver.bullet@zoho.com> wrote:
On Fri, 16 Sep 2016 12:14:30 -0400, David Rosenstrauch wrote:
I'm running XFCE desktop btw.
On Arch Linux using Xfce not necessarily explains what screen lock / screensaver you are using.
Personally, I noticed that using xscreensaver, the screen locks but never enters standby, suspend, or off DPMS power saving modes. If I run "xset dpms force off" the monitor immediately powers off and comes back on when I hit a key or move the mouse. Also, xautolock is failing to detect inactivity and suspend my computer as I have it configured to do. This happened since upgrading from linux 4.6.4 to 4.7.2 and continues to occur with 4.7.4. I've noticed this on two separate computers, one running Intel graphics and the other running the nvidia driver. The version of xscreensaver has been unchanged for me at 5.35 since 1 July. -Eric
On Sun, 18 Sep 2016 10:23:41 -0400, David Rosenstrauch wrote:
On 09/18/2016 01:22 AM, Ralf Mardorf wrote:
On Fri, 16 Sep 2016 12:14:30 -0400, David Rosenstrauch wrote:
I'm running XFCE desktop btw.
On Arch Linux using Xfce not necessarily explains what screen lock / screensaver you are using.
xflock4/xscreensaver
Ok... [rocketmouse@archlinux ~]$ pacman -Si xfce4-session | grep lock xscreensaver: for locking screen with xflock4 gnome-screensaver: for locking screen with xflock4 xlockmore: for locking screen with xflock4 slock: for locking screen with xflock4 https://wiki.archlinux.org/index.php/xfce#Lock_the_screen ... and from where did you get the information that xscreensaver is used? Is nothing lese installed? I don't know how to find out, I'm neither using a screensaver, nor do I use Xfce4 anymore. Perhaps xfconf-query -l xfconf-query -c xfce4-power-manager -lv ? Regards, Ralf
On 09/18/2016 10:45 AM, Ralf Mardorf wrote:
On Sun, 18 Sep 2016 10:23:41 -0400, David Rosenstrauch wrote:
On 09/18/2016 01:22 AM, Ralf Mardorf wrote:
On Fri, 16 Sep 2016 12:14:30 -0400, David Rosenstrauch wrote:
I'm running XFCE desktop btw.
On Arch Linux using Xfce not necessarily explains what screen lock / screensaver you are using.
xflock4/xscreensaver
Ok...
[rocketmouse@archlinux ~]$ pacman -Si xfce4-session | grep lock xscreensaver: for locking screen with xflock4 gnome-screensaver: for locking screen with xflock4 xlockmore: for locking screen with xflock4 slock: for locking screen with xflock4
https://wiki.archlinux.org/index.php/xfce#Lock_the_screen
... and from where did you get the information that xscreensaver is used? Is nothing lese installed?
I don't know how to find out, I'm neither using a screensaver, nor do I use Xfce4 anymore.
Perhaps
xfconf-query -l xfconf-query -c xfce4-power-manager -lv
?
Regards, Ralf
Well I only have xscreensaver installed, not gnome-screensaver, so I'd think it must be using that. Thanks, DR
On 09/16/2016 12:14 PM, David Rosenstrauch wrote:
I've noticed that my screen lock / screensaver has stopped engaging as of a couple of days ago. I check the settings (which I haven't changed recently), but they seem to be set correctly.
Anyone have an idea what package upgrade might have caused this and/or which bugs I should watch for a resolution?
I'm running XFCE desktop btw.
Thanks,
DR
I've discovered something else odd going on that seems to be related to this issue. If I activate the screen lock by hand, and the screensaver starts running, I noticed that within say 30 seconds the screensaver pauses and displays the login box - as if someone pressed a key on the keyboard or moved the mouse. This would explain why the screensaver never engages - it keeps getting keyboard or mouse input (or at least thinks it is) that prevents it. But that makes the problem even more puzzling, as my hands are not on the keyboard or mouse. My next guess was that perhaps there's a broken key on the keyboard that keeps pressing. But I used xev, and it shows no keyboard or mouse events while my hands are off. Is anyone else seeing similar behavior? If not, I guess I'll have to assume this is a hardware problem. But if so, I'd appreciate any suggestion on how I might go about debugging. Thanks, DR
Le 19 Sep, 2016, David Rosenstrauch a écrit:
On 09/16/2016 12:14 PM, David Rosenstrauch wrote:
I've noticed that my screen lock / screensaver has stopped engaging as of a couple of days ago. I check the settings (which I haven't changed recently), but they seem to be set correctly.
Anyone have an idea what package upgrade might have caused this and/or which bugs I should watch for a resolution?
I'm running XFCE desktop btw.
Thanks,
DR
I've discovered something else odd going on that seems to be related to this issue.
If I activate the screen lock by hand, and the screensaver starts running, I noticed that within say 30 seconds the screensaver pauses and displays the login box - as if someone pressed a key on the keyboard or moved the mouse. This would explain why the screensaver never engages - it keeps getting keyboard or mouse input (or at least thinks it is) that prevents it.
But that makes the problem even more puzzling, as my hands are not on the keyboard or mouse. My next guess was that perhaps there's a broken key on the keyboard that keeps pressing. But I used xev, and it shows no keyboard or mouse events while my hands are off.
Is anyone else seeing similar behavior? If not, I guess I'll have to assume this is a hardware problem. But if so, I'd appreciate any suggestion on how I might go about debugging.
Thanks,
DR
Hi! Sorry for being so late. I had a similar problem a few weeks ago. I had just started using a HDMI cable, and there are two HDMI inputs on the monitor. When the screen locker was activated, the monitor simply switched to the other HDMI input which defeated the screen lock. The solution was to turn auto-switch input to off. RB
I was able to pin this down to an issue with xfce4-power-manager: https://bugzilla.xfce.org/show_bug.cgi?id=12857 DR On 12/22/2016 09:51 AM, yaky83--- via arch-general wrote:
Le 19 Sep, 2016, David Rosenstrauch a écrit:
On 09/16/2016 12:14 PM, David Rosenstrauch wrote:
I've noticed that my screen lock / screensaver has stopped engaging as of a couple of days ago. I check the settings (which I haven't changed recently), but they seem to be set correctly.
Anyone have an idea what package upgrade might have caused this and/or which bugs I should watch for a resolution?
I'm running XFCE desktop btw.
Thanks,
DR
I've discovered something else odd going on that seems to be related to this issue.
If I activate the screen lock by hand, and the screensaver starts running, I noticed that within say 30 seconds the screensaver pauses and displays the login box - as if someone pressed a key on the keyboard or moved the mouse. This would explain why the screensaver never engages - it keeps getting keyboard or mouse input (or at least thinks it is) that prevents it.
But that makes the problem even more puzzling, as my hands are not on the keyboard or mouse. My next guess was that perhaps there's a broken key on the keyboard that keeps pressing. But I used xev, and it shows no keyboard or mouse events while my hands are off.
Is anyone else seeing similar behavior? If not, I guess I'll have to assume this is a hardware problem. But if so, I'd appreciate any suggestion on how I might go about debugging.
Thanks,
DR
Hi!
Sorry for being so late.
I had a similar problem a few weeks ago. I had just started using a HDMI cable, and there are two HDMI inputs on the monitor. When the screen locker was activated, the monitor simply switched to the other HDMI input which defeated the screen lock. The solution was to turn auto-switch input to off.
RB
participants (4)
-
David Rosenstrauch
-
Eric Blau
-
Ralf Mardorf
-
yaky83＠gmail.com