[Bug 206339] screen should be locked before suspending the system not after
Marek Otahal
markotahal at gmail.com
Sun Jun 26 18:09:03 BST 2011
https://bugs.kde.org/show_bug.cgi?id=206339
--- Comment #8 from Marek Otahal <markotahal gmail com> 2011-06-26 17:09:03 ---
ok, i gave it a throurough test.
*) time interval for evil doing-that is ctr+alt+f7 switching to original
session/or ending the new session- and between the session is locked- i have
2-5s, that is enough with quick fingers ;) to do eg sudo passwd
*) interval between "comming back" to the orig session is imho irrelevant-eg
couple of minutes.
I tried both with swap and with swapoff, so disk activity and swap cannot be an
excuse(and should not be anyway).
I think the essential problem is that the original session(the one that
executes Switch User) should be locked immediately before starting the new
user's session.
My test case:
1/ have default session (maybe some programs running are essential to slow
things down, firefox,kmail and konsole works for me)
2/ Switch user (work as the user, just to let all the post-login processes
settle down) (orig session should be locked right here!)
3/ initiate switch back, either ctrl alt fn, or log out of the new session
4/ the original session is volunerable for some time period before lock-screen
actually kocks in (2-5s what i could reproduce)
I think it is very similar to the cases with suspend/hibernate.
My usecase for needing this is:
i work on my session, now want some programs keep running but let someone else
use the computer.
Thank you, Mark
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the Unassigned-bugs
mailing list