After leaving my laptop for a while, my Kubuntu session closed. (I'm not sure which of the various timeout criteria caused it.) So I got a screen that said my session was locked and I needed to provide my password to unlock it.
HI i am literally locked out. using centos 5.8 and all of a sudden i got this
"Your session only lasted less than 10 seconds. If you have not logged out yourself, this could mean that there is some installation problem or that you may be out of disk space.
Is there a way to create identifiable Byobu sessions so that when I've got multiple sessions running, the byobu-select-session menu gives me a list of sessions I can recognize, as opposed to non-descript tmux port numbers?
In an ideal world, it would be great to be able to both start a session giving it a name and to modify such a session to change a name if it's already running?
Friends--
Lubuntu 12.04 fresh install. I login from the computer. I then login via ssh from another computer. When the first session screen locks after X minutes, my ssh session is killed or at least locked. When I go back to the physical machine and login, then I can continue my ssh session. How can I shut off this behavior so my ssh session is not interrupted?
For example, in X session, I can use Ctrl-Alt-L to lock the screen, so it would ask for password to unlock and prevent somebody from messing with mine computer.
But if I have an open terminal session on one of the tty's (which I can access with Ctrl-Alt-F1, for example) - then it is not locked, and somebody can still use it to do some harm.
Hello,
Although I have no problem with Unity and want to continue using it, my wife is not a fan. So I installed LXDE on our shared desktop and set her session to use it. We usually both remain logged in and switch between the sessions.
I have noticed that when my wife is logged in and leaves the computer for a while the monitor is never put in power save mode.
Back to Windows NT 4.0 there where a screen saver named "Windows logon". It mimic the usual logon screen (but the dialogue box moved randomly on the screen to avoid some burning process). I think it was also available with Windows 2000.
On Windows 2003 it is not longer available.
Is there a way to:
1. lock a session after a defined timeout
2.
I've been messing with some things and the lock screen is not working well at the moment. Since I like the standard login screen much better anyway, I would like to change the action for the Ctrl+Alt+L shortcut. At the moment, it does the same thing as "Lock Screen" in the top-right power/settings menu.
I have created a multiuser screen session and did 'addacl user1'. Now user1 can join the screen session via command like 'screen -x /screen-name' .
Is it possible to prevent this user (user1) from creating new sessions with 'ctrl+a c' ?
Email this page
