SlackwareThis Forum is for the discussion of Slackware 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.
You should know that, well, the routines and API calls used by MPlayer, SDL, and other full-screen apps and games to suspend the screensaver when they're running? They don't work on xscreensaver. They do work on xlockmore.
They don't work on xscreensaver. They do work on xlockmore.
VLC (at least the alien-compiled version I'm using) does work on xscreensaver.
For MPlayer I use a custom script to invoke it which surrounds the actual call with
Due to covid-19, I decided to run BOINC on my laptop (on the server for a while) and I noticed between that and xscreensaver the CPU Temp spikes, even when using a blank screen.
I found this xidle/github.com and using that along with xlock (mode=blank) uses hardly any cpu cycles. The temp is higher than normal, but at least I cannot fry an egg on the CPU now
I'd like a way to disable CTRL+ALT+BACKSPACE which can bypass X altogether when xlock is running.
slock documents how to do this in its manpage
Code:
SECURITY CONSIDERATIONS
To make sure a locked screen can not be bypassed by switching VTs or
killing the X server with Ctrl+Alt+Backspace, it is recommended to dis‐
able both in xorg.conf(5) for maximum security:
Section "ServerFlags"
Option "DontVTSwitch" "True"
Option "DontZap" "True"
EndSection
Thanks Flinch .. my understand is that will disable it completely. I'd only like to disable it while running the screensaver
I do use ctrl+alt+backspace out of habit after all these years legitimately sometimes...
my understand is that will disable it completely. I'd only like to disable it while running the screensaver
I don't know if it's possible to change settings like this when Xorg is already running. I won't dare to claim it's not, but if it is and screensavers aren't doing it, isn't this a security flaw that's going for decades?
Quote:
Originally Posted by tramtrist
I do use ctrl+alt+backspace out of habit after all these years legitimately sometimes...
Isn't hitting Ctrl-Alt-Backspace pretty much the same as doing `killall Xorg` in a console?
In recent years I've wrapped an "xlament" shell script around it so I don't have to remember all the command line options, and I also added some killall commands to suspend/restore select processes while my system is locked:
What's the exact implication of doing this? System using less CPU, thus computer using less power when locked?
Yes, that's most of it. My laptop draws less power and generates less heat. Heat was less of an issue with my T530, but this new P73 runs a lot hotter, even with the CPU speed throttled.
Also, SIGSTOP'ing the browser helps stave off memory leaks. Pale Moon is a lot better about not leaking memory than Firefox, but it still happens a bit.
It makes locking my system a sort of half-way suspend, without the risks or overhead of suspend. All of the processes which would consume measurable CPU are denied CPU quanta by the kernel until SIGCONT is sent, so there's nothing going on.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.