Xlock closes with no password needed after suspend to ram
This is a strange one. I recently bought a Thinkpad T42 to replace my old T21. Pretty much the same setup on both with Slack 12.1
I use exactly the same script to suspend to ram which has an xlock statement in it to require a log in in after resuming. This works fine on the T21 but I find on the T42 xlock will allow access to the desktop just by clicking mouse - ie it doesn't ask for a pass. Stranger still, when I try to test this by suspending and resuming straight away it works fine, but when I suspend and leave the laptop off for a while it doesn't work as it should. Has anyone else found this problem and have any solution or ideas? |
Did you check the xlock permissions on both system ? (ls -al /usr/bin/xlock)
Same xlock version ? (xlock -version) |
Yes they are the same
|
Maybe a power management issue, like the suspend event does not trigger the xlock call on the Thinkpad T42 ? I never tried something like this, could you tell how you have configured your suspend system ?
|
Code:
dive@DarkerStar(~/scripts) cat suspendlock |
Quote:
|
What is the output with: cat /sys/power/state on your system ?
(just for checking if mem is available) Quote:
|
Theres nothing wrong with the suspension itself - that works fine - it's just xlock isnt working. I am going to try xscreensaver-command -lock to see if that works.
|
xscreensaver-command -lock
works so far |
Glad you found a solution :)
Just to be sure, when you enter: ls -l /usr/bin/xlock /usr/bin/xscreensaver ... both programs have the same permissions, no ? |
Yes both perms are the same. I can't explain it unless it's something to do with different kernel versions/hardware.
|
All times are GMT -5. The time now is 08:57 AM. |