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.
I have two normal login accounts on my desktop computer. I run KDE on one and fluxbox on the other. If I lock the KDE desktop, it stays locked. But the fluxbox desktop often unlocks itself after a few hours.
I don't think that anyone could have the password, but just in case, I've changed it a couple of times over the last week or so. I still find it unlocked sometimes hours after locking it. That said, I'm not ruling out some kind of security issue.
I'm running Slackware 14.1. Has anyone else run into a problem like this? Is there any way I can determine how it is coming unlocked?
For fluxbox I suspect you are using either xscreensaver or xlock. Could it be one of them are crashing (see slacker1337)? If using xscreensaver try adjusting settings using xscreensaver-demo. Some of xscreensaver's modes can be graphically intensive.
For fluxbox I suspect you are using either xscreensaver or xlock. Could it be one of them are crashing (see slacker1337)? If using xscreensaver try adjusting settings using xscreensaver-demo. Some of xscreensaver's modes can be graphically intensive.
Thanks, John. I don't think fluxbox is using xscreensaver. I ran the xcreensaver-demo, and it looks quite different from what I normally see when I lock the screen. I'm using whatever fluxbox is set up to use by default in Slackware 14.1.
I also get this when I run the xscreensaver-demo, but I'm not too concerned about it since I'm pretty sure that fluxbox is actually using xlock.
Code:
(xscreensaver-demo:32639): libglade-WARNING **: Could not load support for `gnome': libgnome.so: cannot open shared object file: No such file or
directory
Thank you. But that just hangs. It doesn't lock the screen or display a screensaver or write anything to the log file. I can terminate it with CTRL+C.
It isn't hanging, it's simply running in the foreground. The lack of output to the log is good as well, since the "2>" redirects only stderr to the log. No output to the log means no errors. Place an ampersand at the end of my recommended command to place it in the background, or use CTRL+Z to suspend the process followed by a "bg" to place it in the background.
If you don't know which screensaver that fluxbox is using, just look in ~/.fluxbox/menu and search for "Lock Screen". For instance, my fluxbox menu has the following at line 196:
Code:
[exec] (Lock screen) {xlock}
Which tells me that my default screen locker was xlock.
Ok, it turns out fluxbox menu system is pretty straightforward. I was able to edit ~/.fluxbox/startup to start xscreensaver when fluxbox starts, then add a menu item to run the {/usr/bin/xscreensaver-command -lock}. I'm leaving the xlock menu item in there until I am satisfied that xscreenserver will do the job for me.
Thank you all for the assistance. I appreciate it.
I also get this when I run the xscreensaver-demo, but I'm not too concerned about it since I'm pretty sure that fluxbox is actually using xlock.
Code:
(xscreensaver-demo:32639): libglade-WARNING **: Could not load support for `gnome': libgnome.so: cannot open shared object file: No such file or
directory
I get that too, I just ignore it. For Fluxbox I have this in file ~/.fluxbox/startup to enable xscreensaver:
Code:
xscreensaver -no-splash &
and in ~/.fluxbox/keys I have this:
Code:
Control Mod1 L :ExecCommand xscreensaver-command -lock
which will enable the screen saver when pressing "<Ctrl><Alt>L".
Thanks for the key shortcut, John. I just added that to the ~/.fluxbox/keys file, but it doesn't seem to have any affect. I'm working on it.
Seems to work with lower case l, but not upper case L, even though the keys file has an uppercase L in the key sequence. Whatever. So long as it works...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.