Xfce 4: screensaver disabled but still the screen is locked after some time.
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.
Xfce 4: screensaver disabled but still the screen is locked after some time.
Slackware 14.1
Hi: I disabled the screensaver and still, after some time with no keyboard activity the screen is locked and I must enter my passwd. In 14.0 I just disabled the screensaver in Settings>Screensaver and unchecked the corresponding entry in Settings>Autostart Applications (or something like that). But this seems to be not enough in 14.1. Is there something I should do in addition to what I did?
Distribution: Deb, Mint, Slack, LFS, Fedora, Ubuntu(LXDE)
Posts: 71
Rep:
probably xset
xset is probably what you are looking for; see the man page
'xset -dpms' TO STOP SCREEN BLANKING -or- 'xset dpms 300 0 0' to go standby in 5'. Also 'xset s off' to turn off screen saver.
Can add to /etc/rc.local so you don't have to re-enter the setting after each reboot.
/etc/rc.local is not the right place to put the xset commands. X might get started after rc.local has run, and it will not be re-run if X11 is restarted without a system reboot.
better options include:
/etc/X11/xinit/xinitrc (which is a soft link to whatever DE specific xinitrc you use) if you want the behavior system wide
otherwise you can copy that file to ~/.xinitrc and add it there, to effect only one user account.
An even smarter solution IMHO would be to create a shell script with any xset commands etc you need and run it from your session manager, in XFCE goto session and startup and than the application autostart tab, and add your script. I am sure KDE has something similar but I have not used that in years, so I don't exactly how to do that. The reason I say this is smarted is its possible the desktop environment might step on any settings you have put into xinitrc as part of its own startup. Letting the session manager do it should help ensure they are the amoung last commands to get run after you login.
xset is probably what you are looking for; see the man page
'xset -dpms' TO STOP SCREEN BLANKING -or- 'xset dpms 300 0 0' to go standby in 5'. Also 'xset s off' to turn off screen saver.
Can add to /etc/rc.local so you don't have to re-enter the setting after each reboot.
/etc/rc.local is not the right place to put the xset commands. X might get started after rc.local has run, and it will not be re-run if X11 is restarted without a system reboot.
better options include:
/etc/X11/xinit/xinitrc (which is a soft link to whatever DE specific xinitrc you use) if you want the behavior system wide
otherwise you can copy that file to ~/.xinitrc and add it there, to effect only one user account.
An even smarter solution IMHO would be to create a shell script with any xset commands etc you need and run it from your session manager, in XFCE goto session and startup and than the application autostart tab, and add your script. I am sure KDE has something similar but I have not used that in years, so I don't exactly how to do that. The reason I say this is smarted is its possible the desktop environment might step on any settings you have put into xinitrc as part of its own startup. Letting the session manager do it should help ensure they are the amoung last commands to get run after you login.
Actually, disabling it in the xorg.conf configuration is the right place.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.