[SOLVED] Debian not excepting password when screen is locked unless i restart.
DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Debian not excepting password when screen is locked unless i restart.
Does anyone have a solution or explanation to this problem. My problem is that when i leave Debian on for several hours with the default screen saver on it won`t take the password but if i re-start or re-boot it does like it normally would. Yes, i know the password & entered it several times but it would not take it ** Same password ** until re-start.
It`s a new install only a few days old. I think it has been doing it from the beginning i noticed it when i leave it on several hours with no activity.
I've had once a similar problem with Xubuntu 20.04. Logging in on a virtual console (Ctrl+Alt+F1) and issuing xfce4-screensaver-command --exit helped. Didn't investigate it any further.
I've had once a similar problem with Xubuntu 20.04. Logging in on a virtual console (Ctrl+Alt+F1) and issuing xfce4-screensaver-command --exit helped. Didn't investigate it any further.
Unless you specifically configured X to disable them, virtual consoles should be accessible when the screen is locked. See the section Magic Backdoor Keystrokes in the xscreensaver(1) manual page:
Quote:
The XFree86 X server and the Linux kernel both trap certain magic keystrokes before X11 client programs ever see them. If you care about keeping your screen locked, this is a big problem.
Ctrl+Alt+Backspace
This keystroke kills the X server, and on some systems, leaves you at a text console. If the user launched X11 manually, that text console will still be logged in. To disable this keystroke globally and permanently, you need to set the DontZap flag in your xorg.conf or XF86Config or XF86Config-4 file, depending which is in use on your system. See XF86Config(5) for details.
Ctrl-Alt-F1, Ctrl-Alt-F2, etc.
These keystrokes will switch to a different virtual console, while leaving the console that X11 is running on locked. If you left a shell logged in on another virtual console, it is unprotected. So don't leave yourself logged in on other consoles. You can disable VT switching globally and permanently by setting DontVTSwitch in your xorg.conf, but that might make your system harder to use, since VT switching is an actual useful feature.
There is no way to disable VT switching only when the screen is locked. It's all or nothing.
Ctrl-Alt-KP_Multiply
This keystroke kills any X11 app that holds a lock, so typing this will kill xscreensaver and unlock the screen. This so-called "feature" showed up in the X server in 2008, and as of 2011, some vendors are shipping it turned on by default. How nice. You can disable it by turning off AllowClosedownGrabs in xorg.conf.
Alt-SysRq-F
This is the Linux kernel "OOM-killer" keystroke. It shoots down random long-running programs of its choosing, and so might might target and kill xscreensaver, and there's no way for xscreensaver to protect itself from that. You can disable it globally with:
Code:
echo 176 > /proc/sys/kernel/sysrq
This text is quite dated. Nowadays, most vendors (I believe Debian, too) ship their systems with Ctrl+Alt+Backspace and Ctrl+Alt+KP_Multiply disabled by default. But virtual consoles and the Magic SysRq key should be enabled in Debian.
Unless you specifically configured X to disable them, virtual consoles should be accessible when the screen is locked. See the section Magic Backdoor Keystrokes in the xscreensaver(1) manual page:
This text is quite dated. Nowadays, most vendors (I believe Debian, too) ship their systems with Ctrl+Alt+Backspace and Ctrl+Alt+KP_Multiply disabled by default. But virtual consoles and the Magic SysRq key should be enabled in Debian.
Thank`s i`ll look into it.
From your post the screen saver even though locked can be bypassed with the procedures above. Being a newbie can you specify what and where to post any specific code to disable the screen save from being bypassed ?
From your post the screen saver even though locked can be bypassed with the procedures above.
Except for people who launch X from the command line (which is rare these days and which you are not doing), it can only be "bypassed" by entering username and password at the virtual console.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.