How to unlock locked session?Authentication Failure Switch to greeterLock Tmux Session With VlockLock and...
Avoid page break between paragraphs
How can a large fleets maintain formation in interstellar space?
How do you funnel food off a cutting board?
Dilemma of explaining to interviewer that he is the reason for declining second interview
How to remove the Data item from the Datasource selection
How should I handle players who ignore the session zero agreement?
Does Skippy chunky peanut butter contain trans fat?
Has any human ever had the choice to leave Earth permanently?
General past possibility with 'could'
Is it possible to grant users sftp access without shell access? If yes, how is it implemented?
In Linux what happens if 1000 files in a directory are moved to another location while another 300 files were added to the source directory?
Crontab: Ubuntu running script (noob)
How would an AI self awareness kill switch work?
What is a good reason for every spaceship to carry a weapon on board?
Non-Cancer terminal illness that can affect young (age 10-13) girls?
Why avoid shared user accounts?
How much mayhem could I cause as a sentient fish?
Potential client has a problematic employee I can't work with
What happens when a creature with flying blocks my non-flying attacker?
Play Zip, Zap, Zop
Which communication protocol is used in AdLib sound card?
Ellipses aligned on the same boundary point
Early credit roll before the end of the film
How to deal with possible delayed baggage?
How to unlock locked session?
Authentication Failure Switch to greeterLock Tmux Session With VlockLock and Unlock from USB disk (pendrive)How to unlock screen in Kubuntu 11.10?I seem to be locked out of my accountComputer has locked up, will it recover?iOS 7 Locked Bug via Ubuntu 13.10Put monitor to sleep when locked?How to unlock file, locked by a processHow do I unlock /var/lib/dpkg/lock?Laptop sometimes not locked on resume from sleep (lid action)
I'm using xubuntu 14.04 on AMD based hardware. It is configured not to lock a session and not to power down automatically on longer idle times.
There have been no recent changes or new software installations other than notified security updates.
I also have the kde desktop installed. The display manager is LightDM, AFAIK.
The system has been behaving nicely for some months, until a couple of days ago. Now, after about ten minutes idle the session is locked automatically. The screen presents a dialog with the caption "This session is locked".
Attempting to "unlock" with the session's username and password results with the message
"You'll be redirected to the unlock dialog in a few seconds" and the cycle starts over. Unable to log in, the only option seems to be to reboot. (I won't mention the work I have just lost":-( )
Does anyone have any idea what's going on here, bearing in mind that AFAIK the power managers are configured NOT to lock sessions and not to power down on idle?
Thanks
lock
asked Dec 7 '14 at 22:35
user215199user215199
178128
add a comment |
I'm using xubuntu 14.04 on AMD based hardware. It is configured not to lock a session and not to power down automatically on longer idle times.
There have been no recent changes or new software installations other than notified security updates.
I also have the kde desktop installed. The display manager is LightDM, AFAIK.
The system has been behaving nicely for some months, until a couple of days ago. Now, after about ten minutes idle the session is locked automatically. The screen presents a dialog with the caption "This session is locked".
Attempting to "unlock" with the session's username and password results with the message
"You'll be redirected to the unlock dialog in a few seconds" and the cycle starts over. Unable to log in, the only option seems to be to reboot. (I won't mention the work I have just lost":-( )
Does anyone have any idea what's going on here, bearing in mind that AFAIK the power managers are configured NOT to lock sessions and not to power down on idle?
Thanks
lock
asked Dec 7 '14 at 22:35
user215199user215199
178128
1
OK, seemed to have found a solution to my immediate problem; another thread elsewhere steered me to "Light Locker Setting", which did not appear on any of my desktop menus. I ran it from /usr/bin/light-locker-settings. Setting everything to "never" or no seems to have stopped the session lock. This leaves the question of why the unlock sequence itself failed by going back to the unlock dialog. A bug?
– user215199
Dec 7 '14 at 23:52
same issue here, on a clean xubuntu 14.04, fully updated as of 19 october, 2015 z.z
– hanshenrik
Oct 20 '15 at 1:53
Same problem on fresh install of Debian testing
– hochl
Feb 16 '17 at 12:56
add a comment |
I'm using xubuntu 14.04 on AMD based hardware. It is configured not to lock a session and not to power down automatically on longer idle times.
There have been no recent changes or new software installations other than notified security updates.
I also have the kde desktop installed. The display manager is LightDM, AFAIK.
The system has been behaving nicely for some months, until a couple of days ago. Now, after about ten minutes idle the session is locked automatically. The screen presents a dialog with the caption "This session is locked".
Attempting to "unlock" with the session's username and password results with the message
"You'll be redirected to the unlock dialog in a few seconds" and the cycle starts over. Unable to log in, the only option seems to be to reboot. (I won't mention the work I have just lost":-( )
Does anyone have any idea what's going on here, bearing in mind that AFAIK the power managers are configured NOT to lock sessions and not to power down on idle?
Thanks
lock
asked Dec 7 '14 at 22:35
user215199user215199
178128
I'm using xubuntu 14.04 on AMD based hardware. It is configured not to lock a session and not to power down automatically on longer idle times.
There have been no recent changes or new software installations other than notified security updates.
I also have the kde desktop installed. The display manager is LightDM, AFAIK.
The system has been behaving nicely for some months, until a couple of days ago. Now, after about ten minutes idle the session is locked automatically. The screen presents a dialog with the caption "This session is locked".
Attempting to "unlock" with the session's username and password results with the message
"You'll be redirected to the unlock dialog in a few seconds" and the cycle starts over. Unable to log in, the only option seems to be to reboot. (I won't mention the work I have just lost":-( )
Does anyone have any idea what's going on here, bearing in mind that AFAIK the power managers are configured NOT to lock sessions and not to power down on idle?
Thanks
lock
lock
asked Dec 7 '14 at 22:35
user215199user215199
178128
asked Dec 7 '14 at 22:35
user215199user215199
178128
asked Dec 7 '14 at 22:35
user215199user215199
178128
asked Dec 7 '14 at 22:35
user215199user215199
178128
asked Dec 7 '14 at 22:35
user215199user215199
178128
178128
1
OK, seemed to have found a solution to my immediate problem; another thread elsewhere steered me to "Light Locker Setting", which did not appear on any of my desktop menus. I ran it from /usr/bin/light-locker-settings. Setting everything to "never" or no seems to have stopped the session lock. This leaves the question of why the unlock sequence itself failed by going back to the unlock dialog. A bug?
– user215199
Dec 7 '14 at 23:52
same issue here, on a clean xubuntu 14.04, fully updated as of 19 october, 2015 z.z
– hanshenrik
Oct 20 '15 at 1:53
Same problem on fresh install of Debian testing
– hochl
Feb 16 '17 at 12:56
add a comment |
1
OK, seemed to have found a solution to my immediate problem; another thread elsewhere steered me to "Light Locker Setting", which did not appear on any of my desktop menus. I ran it from /usr/bin/light-locker-settings. Setting everything to "never" or no seems to have stopped the session lock. This leaves the question of why the unlock sequence itself failed by going back to the unlock dialog. A bug?
– user215199
Dec 7 '14 at 23:52
same issue here, on a clean xubuntu 14.04, fully updated as of 19 october, 2015 z.z
– hanshenrik
Oct 20 '15 at 1:53
Same problem on fresh install of Debian testing
– hochl
Feb 16 '17 at 12:56
1
1
OK, seemed to have found a solution to my immediate problem; another thread elsewhere steered me to "Light Locker Setting", which did not appear on any of my desktop menus. I ran it from /usr/bin/light-locker-settings. Setting everything to "never" or no seems to have stopped the session lock. This leaves the question of why the unlock sequence itself failed by going back to the unlock dialog. A bug?
– user215199
Dec 7 '14 at 23:52
OK, seemed to have found a solution to my immediate problem; another thread elsewhere steered me to "Light Locker Setting", which did not appear on any of my desktop menus. I ran it from /usr/bin/light-locker-settings. Setting everything to "never" or no seems to have stopped the session lock. This leaves the question of why the unlock sequence itself failed by going back to the unlock dialog. A bug?
– user215199
Dec 7 '14 at 23:52
same issue here, on a clean xubuntu 14.04, fully updated as of 19 october, 2015 z.z
– hanshenrik
Oct 20 '15 at 1:53
same issue here, on a clean xubuntu 14.04, fully updated as of 19 october, 2015 z.z
– hanshenrik
Oct 20 '15 at 1:53
Same problem on fresh install of Debian testing
– hochl
Feb 16 '17 at 12:56
Same problem on fresh install of Debian testing
– hochl
Feb 16 '17 at 12:56
add a comment |
6 Answers
6
active
oldest
votes
I do not have the answer to your bug, actually I experience the same thing, but I found here a way to recover the situation without reboot the machine/lightdm.
In your tty1 (Ctrl+Alt+F1), as root, type loginctl unlock-session [id], where [id] is the session id you get by typing loginctl list-sessions.
If it doesn't work with the first ID, try with the other session IDs of your user account.
edited Sep 21 '18 at 9:59
abu_bua
3,45081227
answered Apr 20 '15 at 12:05
JBENOITJBENOIT
40143
Fantastic! Accidentally locked my session while upgrading Ubuntu. I wasn't sure where the upgrade process was up to. Was able to unlock and recover successfully.
– rvdavid
Feb 8 '18 at 1:52
2
I was able to do this as non-root, presumably because I was unlocking my own session.
– Clement Cherlin
Apr 30 '18 at 23:09
loginctl unlock-sessions failed due to incorrect permissions on polkit-agent-helper-1 during my kubuntu 17.10 -> 18.04 upgrade (used to always work whenever the screen locker suggested it during upgrades or similar). The list-sessions and unlock-session [id] trick saved me. Thanks! :)
– KIAaze
May 13 '18 at 12:10
Saved my Day...
– Paflow
Sep 27 '18 at 8:47
add a comment |
I am not able to add comment. here are some words on Ubuntu.
I boot Ubuntu 16.04.1 without login, then I close the lid for going out, and when I am back, reopen the notebook, not able to unlock (light display manager is shown on up-right corner, only password to enter, no user name)
Ctrl+Alt+F1 brings tty1, login my account, then
sudo -i loginctl list-sessions
sudo -i loginctl unlock-session id
As in https://askubuntu.com/a/611611/485005, "If it doesn't work with the first ID, try with the other session IDs"
edited Sep 21 '18 at 10:00
abu_bua
3,45081227
answered Aug 8 '16 at 1:10
Chen Deng-TaChen Deng-Ta
10219
This is constant source of irritation to me. I usually reboot but will try this now.
– dibs
Aug 8 '16 at 2:54
3
as the locked session is of the same user it is not necessary to usesudoin this case.
– logoff
Mar 11 '18 at 15:02
Even simpler: Ctrl+Alt+F1, login, then: killall light-locker. That makes it go away and stay away, at least until you reboot.
– maharvey67
Nov 16 '18 at 1:19
No need to find the correct session id,sudo loginctl unlock-sessionswill unlock your session.
– Benjamin
Jan 17 at 19:17
add a comment |
I think you can simply disable and change the default screensaver locker anyway. Firstly disable light-locker at [LightDM/Xfce] Power Management Preferences followed by:
$ sudo apt-get update && sudo apt-get install xscreensaver && sudo apt-get remove light-locker
then after reboot (restart X) I got the xscreensaver as default screen locker manager.
answered Sep 17 '18 at 6:19
Alex.OAlex.O
211
add a comment |
This worked for me:
sudo service lightdm restart
answered Sep 21 '18 at 9:51
user873818user873818
111
Actually it looks like it's an issue with Nouveau, and with Nvidia proprietary binary drivers. If your video cards are nVidia, blame nvidia. They suck. Restarting lightdm solves the issue but it appears to be an nvidia/nouveau dpmi glitch that causes this.
– Warren P
Oct 25 '18 at 17:39
add a comment |
I had similar issues getting stuck on "You'll be redirected to the unlock dialog in a few seconds" screen in xubuntu 16.04.4 after booting up from a suspended session.
The solve for me is to press Ctrl+Alt+F7
I sometimes have to repeat the above command, but eventually it will allow me to login normally.
edited Sep 21 '18 at 10:01
abu_bua
3,45081227
answered Apr 23 '18 at 1:15
TonyTony
261
Are you using nvidia video card? with nouveau? or proprietary binary drivers?
– Warren P
Oct 25 '18 at 17:40
@WarrenP Using nvidia card with proprietary drivers.
– Tony
Oct 25 '18 at 21:57
I think it's a bad driver or bad interaction between the driver and the display manager. I belive the issue is around DPMI, display power management
– Warren P
Nov 9 '18 at 19:10
add a comment |
Ctrl + Alt + Backspace (pressed twice) will reset the X and kill/close everything you have open on current Desktop session.
On a new log in, please check you screen saver settings and disable lock screen.
answered 10 mins ago
Paul afkPaul afk
413
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f557833%2fhow-to-unlock-locked-session%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
6 Answers
6
active
oldest
votes
6 Answers
6
active
oldest
votes
active
oldest
votes
active
oldest
votes
I do not have the answer to your bug, actually I experience the same thing, but I found here a way to recover the situation without reboot the machine/lightdm.
In your tty1 (Ctrl+Alt+F1), as root, type loginctl unlock-session [id], where [id] is the session id you get by typing loginctl list-sessions.
If it doesn't work with the first ID, try with the other session IDs of your user account.
edited Sep 21 '18 at 9:59
abu_bua
3,45081227
answered Apr 20 '15 at 12:05
JBENOITJBENOIT
40143
Fantastic! Accidentally locked my session while upgrading Ubuntu. I wasn't sure where the upgrade process was up to. Was able to unlock and recover successfully.
– rvdavid
Feb 8 '18 at 1:52
2
I was able to do this as non-root, presumably because I was unlocking my own session.
– Clement Cherlin
Apr 30 '18 at 23:09
loginctl unlock-sessions failed due to incorrect permissions on polkit-agent-helper-1 during my kubuntu 17.10 -> 18.04 upgrade (used to always work whenever the screen locker suggested it during upgrades or similar). The list-sessions and unlock-session [id] trick saved me. Thanks! :)
– KIAaze
May 13 '18 at 12:10
Saved my Day...
– Paflow
Sep 27 '18 at 8:47
add a comment |
I do not have the answer to your bug, actually I experience the same thing, but I found here a way to recover the situation without reboot the machine/lightdm.
In your tty1 (Ctrl+Alt+F1), as root, type loginctl unlock-session [id], where [id] is the session id you get by typing loginctl list-sessions.
If it doesn't work with the first ID, try with the other session IDs of your user account.
edited Sep 21 '18 at 9:59
abu_bua
3,45081227
answered Apr 20 '15 at 12:05
JBENOITJBENOIT
40143
Fantastic! Accidentally locked my session while upgrading Ubuntu. I wasn't sure where the upgrade process was up to. Was able to unlock and recover successfully.
– rvdavid
Feb 8 '18 at 1:52
2
I was able to do this as non-root, presumably because I was unlocking my own session.
– Clement Cherlin
Apr 30 '18 at 23:09
loginctl unlock-sessions failed due to incorrect permissions on polkit-agent-helper-1 during my kubuntu 17.10 -> 18.04 upgrade (used to always work whenever the screen locker suggested it during upgrades or similar). The list-sessions and unlock-session [id] trick saved me. Thanks! :)
– KIAaze
May 13 '18 at 12:10
Saved my Day...
– Paflow
Sep 27 '18 at 8:47
add a comment |
I do not have the answer to your bug, actually I experience the same thing, but I found here a way to recover the situation without reboot the machine/lightdm.
In your tty1 (Ctrl+Alt+F1), as root, type loginctl unlock-session [id], where [id] is the session id you get by typing loginctl list-sessions.
If it doesn't work with the first ID, try with the other session IDs of your user account.
edited Sep 21 '18 at 9:59
abu_bua
3,45081227
answered Apr 20 '15 at 12:05
JBENOITJBENOIT
40143
I do not have the answer to your bug, actually I experience the same thing, but I found here a way to recover the situation without reboot the machine/lightdm.
In your tty1 (Ctrl+Alt+F1), as root, type loginctl unlock-session [id], where [id] is the session id you get by typing loginctl list-sessions.
If it doesn't work with the first ID, try with the other session IDs of your user account.
edited Sep 21 '18 at 9:59
abu_bua
3,45081227
answered Apr 20 '15 at 12:05
JBENOITJBENOIT
40143
edited Sep 21 '18 at 9:59
abu_bua
3,45081227
edited Sep 21 '18 at 9:59
abu_bua
3,45081227
edited Sep 21 '18 at 9:59
abu_bua
3,45081227
3,45081227
answered Apr 20 '15 at 12:05
JBENOITJBENOIT
40143
answered Apr 20 '15 at 12:05
JBENOITJBENOIT
40143
answered Apr 20 '15 at 12:05
JBENOITJBENOIT
40143
40143
Fantastic! Accidentally locked my session while upgrading Ubuntu. I wasn't sure where the upgrade process was up to. Was able to unlock and recover successfully.
– rvdavid
Feb 8 '18 at 1:52
2
I was able to do this as non-root, presumably because I was unlocking my own session.
– Clement Cherlin
Apr 30 '18 at 23:09
loginctl unlock-sessions failed due to incorrect permissions on polkit-agent-helper-1 during my kubuntu 17.10 -> 18.04 upgrade (used to always work whenever the screen locker suggested it during upgrades or similar). The list-sessions and unlock-session [id] trick saved me. Thanks! :)
– KIAaze
May 13 '18 at 12:10
Saved my Day...
– Paflow
Sep 27 '18 at 8:47
add a comment |
Fantastic! Accidentally locked my session while upgrading Ubuntu. I wasn't sure where the upgrade process was up to. Was able to unlock and recover successfully.
– rvdavid
Feb 8 '18 at 1:52
2
I was able to do this as non-root, presumably because I was unlocking my own session.
– Clement Cherlin
Apr 30 '18 at 23:09
loginctl unlock-sessions failed due to incorrect permissions on polkit-agent-helper-1 during my kubuntu 17.10 -> 18.04 upgrade (used to always work whenever the screen locker suggested it during upgrades or similar). The list-sessions and unlock-session [id] trick saved me. Thanks! :)
– KIAaze
May 13 '18 at 12:10
Saved my Day...
– Paflow
Sep 27 '18 at 8:47
Fantastic! Accidentally locked my session while upgrading Ubuntu. I wasn't sure where the upgrade process was up to. Was able to unlock and recover successfully.
– rvdavid
Feb 8 '18 at 1:52
Fantastic! Accidentally locked my session while upgrading Ubuntu. I wasn't sure where the upgrade process was up to. Was able to unlock and recover successfully.
– rvdavid
Feb 8 '18 at 1:52
2
2
I was able to do this as non-root, presumably because I was unlocking my own session.
– Clement Cherlin
Apr 30 '18 at 23:09
I was able to do this as non-root, presumably because I was unlocking my own session.
– Clement Cherlin
Apr 30 '18 at 23:09
loginctl unlock-sessions failed due to incorrect permissions on polkit-agent-helper-1 during my kubuntu 17.10 -> 18.04 upgrade (used to always work whenever the screen locker suggested it during upgrades or similar). The list-sessions and unlock-session [id] trick saved me. Thanks! :)
– KIAaze
May 13 '18 at 12:10
loginctl unlock-sessions failed due to incorrect permissions on polkit-agent-helper-1 during my kubuntu 17.10 -> 18.04 upgrade (used to always work whenever the screen locker suggested it during upgrades or similar). The list-sessions and unlock-session [id] trick saved me. Thanks! :)
– KIAaze
May 13 '18 at 12:10
Saved my Day...
– Paflow
Sep 27 '18 at 8:47
Saved my Day...
– Paflow
Sep 27 '18 at 8:47
add a comment |
I am not able to add comment. here are some words on Ubuntu.
I boot Ubuntu 16.04.1 without login, then I close the lid for going out, and when I am back, reopen the notebook, not able to unlock (light display manager is shown on up-right corner, only password to enter, no user name)
Ctrl+Alt+F1 brings tty1, login my account, then
sudo -i loginctl list-sessions
sudo -i loginctl unlock-session id
As in https://askubuntu.com/a/611611/485005, "If it doesn't work with the first ID, try with the other session IDs"
edited Sep 21 '18 at 10:00
abu_bua
3,45081227
answered Aug 8 '16 at 1:10
Chen Deng-TaChen Deng-Ta
10219
This is constant source of irritation to me. I usually reboot but will try this now.
– dibs
Aug 8 '16 at 2:54
3
as the locked session is of the same user it is not necessary to usesudoin this case.
– logoff
Mar 11 '18 at 15:02
Even simpler: Ctrl+Alt+F1, login, then: killall light-locker. That makes it go away and stay away, at least until you reboot.
– maharvey67
Nov 16 '18 at 1:19
No need to find the correct session id,sudo loginctl unlock-sessionswill unlock your session.
– Benjamin
Jan 17 at 19:17
add a comment |
I am not able to add comment. here are some words on Ubuntu.
I boot Ubuntu 16.04.1 without login, then I close the lid for going out, and when I am back, reopen the notebook, not able to unlock (light display manager is shown on up-right corner, only password to enter, no user name)
Ctrl+Alt+F1 brings tty1, login my account, then
sudo -i loginctl list-sessions
sudo -i loginctl unlock-session id
As in https://askubuntu.com/a/611611/485005, "If it doesn't work with the first ID, try with the other session IDs"
edited Sep 21 '18 at 10:00
abu_bua
3,45081227
answered Aug 8 '16 at 1:10
Chen Deng-TaChen Deng-Ta
10219
This is constant source of irritation to me. I usually reboot but will try this now.
– dibs
Aug 8 '16 at 2:54
3
as the locked session is of the same user it is not necessary to usesudoin this case.
– logoff
Mar 11 '18 at 15:02
Even simpler: Ctrl+Alt+F1, login, then: killall light-locker. That makes it go away and stay away, at least until you reboot.
– maharvey67
Nov 16 '18 at 1:19
No need to find the correct session id,sudo loginctl unlock-sessionswill unlock your session.
– Benjamin
Jan 17 at 19:17
add a comment |
I am not able to add comment. here are some words on Ubuntu.
I boot Ubuntu 16.04.1 without login, then I close the lid for going out, and when I am back, reopen the notebook, not able to unlock (light display manager is shown on up-right corner, only password to enter, no user name)
Ctrl+Alt+F1 brings tty1, login my account, then
sudo -i loginctl list-sessions
sudo -i loginctl unlock-session id
As in https://askubuntu.com/a/611611/485005, "If it doesn't work with the first ID, try with the other session IDs"
edited Sep 21 '18 at 10:00
abu_bua
3,45081227
answered Aug 8 '16 at 1:10
Chen Deng-TaChen Deng-Ta
10219
I am not able to add comment. here are some words on Ubuntu.
I boot Ubuntu 16.04.1 without login, then I close the lid for going out, and when I am back, reopen the notebook, not able to unlock (light display manager is shown on up-right corner, only password to enter, no user name)
Ctrl+Alt+F1 brings tty1, login my account, then
sudo -i loginctl list-sessions
sudo -i loginctl unlock-session id
As in https://askubuntu.com/a/611611/485005, "If it doesn't work with the first ID, try with the other session IDs"
edited Sep 21 '18 at 10:00
abu_bua
3,45081227
answered Aug 8 '16 at 1:10
Chen Deng-TaChen Deng-Ta
10219
edited Sep 21 '18 at 10:00
abu_bua
3,45081227
edited Sep 21 '18 at 10:00
abu_bua
3,45081227
edited Sep 21 '18 at 10:00
abu_bua
3,45081227
3,45081227
answered Aug 8 '16 at 1:10
Chen Deng-TaChen Deng-Ta
10219
answered Aug 8 '16 at 1:10
Chen Deng-TaChen Deng-Ta
10219
answered Aug 8 '16 at 1:10
Chen Deng-TaChen Deng-Ta
10219
10219
This is constant source of irritation to me. I usually reboot but will try this now.
– dibs
Aug 8 '16 at 2:54
3
as the locked session is of the same user it is not necessary to usesudoin this case.
– logoff
Mar 11 '18 at 15:02
Even simpler: Ctrl+Alt+F1, login, then: killall light-locker. That makes it go away and stay away, at least until you reboot.
– maharvey67
Nov 16 '18 at 1:19
No need to find the correct session id,sudo loginctl unlock-sessionswill unlock your session.
– Benjamin
Jan 17 at 19:17
add a comment |
This is constant source of irritation to me. I usually reboot but will try this now.
– dibs
Aug 8 '16 at 2:54
3
as the locked session is of the same user it is not necessary to usesudoin this case.
– logoff
Mar 11 '18 at 15:02
Even simpler: Ctrl+Alt+F1, login, then: killall light-locker. That makes it go away and stay away, at least until you reboot.
– maharvey67
Nov 16 '18 at 1:19
No need to find the correct session id,sudo loginctl unlock-sessionswill unlock your session.
– Benjamin
Jan 17 at 19:17
This is constant source of irritation to me. I usually reboot but will try this now.
– dibs
Aug 8 '16 at 2:54
This is constant source of irritation to me. I usually reboot but will try this now.
– dibs
Aug 8 '16 at 2:54
3
3
as the locked session is of the same user it is not necessary to use
sudo in this case.– logoff
Mar 11 '18 at 15:02
as the locked session is of the same user it is not necessary to use
sudo in this case.– logoff
Mar 11 '18 at 15:02
Even simpler: Ctrl+Alt+F1, login, then: killall light-locker. That makes it go away and stay away, at least until you reboot.
– maharvey67
Nov 16 '18 at 1:19
Even simpler: Ctrl+Alt+F1, login, then: killall light-locker. That makes it go away and stay away, at least until you reboot.
– maharvey67
Nov 16 '18 at 1:19
No need to find the correct session id,
sudo loginctl unlock-sessions will unlock your session.– Benjamin
Jan 17 at 19:17
No need to find the correct session id,
sudo loginctl unlock-sessions will unlock your session.– Benjamin
Jan 17 at 19:17
add a comment |
I think you can simply disable and change the default screensaver locker anyway. Firstly disable light-locker at [LightDM/Xfce] Power Management Preferences followed by:
$ sudo apt-get update && sudo apt-get install xscreensaver && sudo apt-get remove light-locker
then after reboot (restart X) I got the xscreensaver as default screen locker manager.
answered Sep 17 '18 at 6:19
Alex.OAlex.O
211
add a comment |
I think you can simply disable and change the default screensaver locker anyway. Firstly disable light-locker at [LightDM/Xfce] Power Management Preferences followed by:
$ sudo apt-get update && sudo apt-get install xscreensaver && sudo apt-get remove light-locker
then after reboot (restart X) I got the xscreensaver as default screen locker manager.
answered Sep 17 '18 at 6:19
Alex.OAlex.O
211
add a comment |
I think you can simply disable and change the default screensaver locker anyway. Firstly disable light-locker at [LightDM/Xfce] Power Management Preferences followed by:
$ sudo apt-get update && sudo apt-get install xscreensaver && sudo apt-get remove light-locker
then after reboot (restart X) I got the xscreensaver as default screen locker manager.
answered Sep 17 '18 at 6:19
Alex.OAlex.O
211
I think you can simply disable and change the default screensaver locker anyway. Firstly disable light-locker at [LightDM/Xfce] Power Management Preferences followed by:
$ sudo apt-get update && sudo apt-get install xscreensaver && sudo apt-get remove light-locker
then after reboot (restart X) I got the xscreensaver as default screen locker manager.
answered Sep 17 '18 at 6:19
Alex.OAlex.O
211
answered Sep 17 '18 at 6:19
Alex.OAlex.O
211
answered Sep 17 '18 at 6:19
Alex.OAlex.O
211
answered Sep 17 '18 at 6:19
Alex.OAlex.O
211
211
add a comment |
add a comment |
This worked for me:
sudo service lightdm restart
answered Sep 21 '18 at 9:51
user873818user873818
111
Actually it looks like it's an issue with Nouveau, and with Nvidia proprietary binary drivers. If your video cards are nVidia, blame nvidia. They suck. Restarting lightdm solves the issue but it appears to be an nvidia/nouveau dpmi glitch that causes this.
– Warren P
Oct 25 '18 at 17:39
add a comment |
This worked for me:
sudo service lightdm restart
answered Sep 21 '18 at 9:51
user873818user873818
111
Actually it looks like it's an issue with Nouveau, and with Nvidia proprietary binary drivers. If your video cards are nVidia, blame nvidia. They suck. Restarting lightdm solves the issue but it appears to be an nvidia/nouveau dpmi glitch that causes this.
– Warren P
Oct 25 '18 at 17:39
add a comment |
This worked for me:
sudo service lightdm restart
answered Sep 21 '18 at 9:51
user873818user873818
111
This worked for me:
sudo service lightdm restart
answered Sep 21 '18 at 9:51
user873818user873818
111
answered Sep 21 '18 at 9:51
user873818user873818
111
answered Sep 21 '18 at 9:51
user873818user873818
111
answered Sep 21 '18 at 9:51
user873818user873818
111
111
Actually it looks like it's an issue with Nouveau, and with Nvidia proprietary binary drivers. If your video cards are nVidia, blame nvidia. They suck. Restarting lightdm solves the issue but it appears to be an nvidia/nouveau dpmi glitch that causes this.
– Warren P
Oct 25 '18 at 17:39
add a comment |
Actually it looks like it's an issue with Nouveau, and with Nvidia proprietary binary drivers. If your video cards are nVidia, blame nvidia. They suck. Restarting lightdm solves the issue but it appears to be an nvidia/nouveau dpmi glitch that causes this.
– Warren P
Oct 25 '18 at 17:39
Actually it looks like it's an issue with Nouveau, and with Nvidia proprietary binary drivers. If your video cards are nVidia, blame nvidia. They suck. Restarting lightdm solves the issue but it appears to be an nvidia/nouveau dpmi glitch that causes this.
– Warren P
Oct 25 '18 at 17:39
Actually it looks like it's an issue with Nouveau, and with Nvidia proprietary binary drivers. If your video cards are nVidia, blame nvidia. They suck. Restarting lightdm solves the issue but it appears to be an nvidia/nouveau dpmi glitch that causes this.
– Warren P
Oct 25 '18 at 17:39
add a comment |
I had similar issues getting stuck on "You'll be redirected to the unlock dialog in a few seconds" screen in xubuntu 16.04.4 after booting up from a suspended session.
The solve for me is to press Ctrl+Alt+F7
I sometimes have to repeat the above command, but eventually it will allow me to login normally.
edited Sep 21 '18 at 10:01
abu_bua
3,45081227
answered Apr 23 '18 at 1:15
TonyTony
261
Are you using nvidia video card? with nouveau? or proprietary binary drivers?
– Warren P
Oct 25 '18 at 17:40
@WarrenP Using nvidia card with proprietary drivers.
– Tony
Oct 25 '18 at 21:57
I think it's a bad driver or bad interaction between the driver and the display manager. I belive the issue is around DPMI, display power management
– Warren P
Nov 9 '18 at 19:10
add a comment |
I had similar issues getting stuck on "You'll be redirected to the unlock dialog in a few seconds" screen in xubuntu 16.04.4 after booting up from a suspended session.
The solve for me is to press Ctrl+Alt+F7
I sometimes have to repeat the above command, but eventually it will allow me to login normally.
edited Sep 21 '18 at 10:01
abu_bua
3,45081227
answered Apr 23 '18 at 1:15
TonyTony
261
Are you using nvidia video card? with nouveau? or proprietary binary drivers?
– Warren P
Oct 25 '18 at 17:40
@WarrenP Using nvidia card with proprietary drivers.
– Tony
Oct 25 '18 at 21:57
I think it's a bad driver or bad interaction between the driver and the display manager. I belive the issue is around DPMI, display power management
– Warren P
Nov 9 '18 at 19:10
add a comment |
I had similar issues getting stuck on "You'll be redirected to the unlock dialog in a few seconds" screen in xubuntu 16.04.4 after booting up from a suspended session.
The solve for me is to press Ctrl+Alt+F7
I sometimes have to repeat the above command, but eventually it will allow me to login normally.
edited Sep 21 '18 at 10:01
abu_bua
3,45081227
answered Apr 23 '18 at 1:15
TonyTony
261
I had similar issues getting stuck on "You'll be redirected to the unlock dialog in a few seconds" screen in xubuntu 16.04.4 after booting up from a suspended session.
The solve for me is to press Ctrl+Alt+F7
I sometimes have to repeat the above command, but eventually it will allow me to login normally.
edited Sep 21 '18 at 10:01
abu_bua
3,45081227
answered Apr 23 '18 at 1:15
TonyTony
261
edited Sep 21 '18 at 10:01
abu_bua
3,45081227
edited Sep 21 '18 at 10:01
abu_bua
3,45081227
edited Sep 21 '18 at 10:01
abu_bua
3,45081227
3,45081227
answered Apr 23 '18 at 1:15
TonyTony
261
answered Apr 23 '18 at 1:15
TonyTony
261
answered Apr 23 '18 at 1:15
TonyTony
261
261
Are you using nvidia video card? with nouveau? or proprietary binary drivers?
– Warren P
Oct 25 '18 at 17:40
@WarrenP Using nvidia card with proprietary drivers.
– Tony
Oct 25 '18 at 21:57
I think it's a bad driver or bad interaction between the driver and the display manager. I belive the issue is around DPMI, display power management
– Warren P
Nov 9 '18 at 19:10
add a comment |
Are you using nvidia video card? with nouveau? or proprietary binary drivers?
– Warren P
Oct 25 '18 at 17:40
@WarrenP Using nvidia card with proprietary drivers.
– Tony
Oct 25 '18 at 21:57
I think it's a bad driver or bad interaction between the driver and the display manager. I belive the issue is around DPMI, display power management
– Warren P
Nov 9 '18 at 19:10
Are you using nvidia video card? with nouveau? or proprietary binary drivers?
– Warren P
Oct 25 '18 at 17:40
Are you using nvidia video card? with nouveau? or proprietary binary drivers?
– Warren P
Oct 25 '18 at 17:40
@WarrenP Using nvidia card with proprietary drivers.
– Tony
Oct 25 '18 at 21:57
@WarrenP Using nvidia card with proprietary drivers.
– Tony
Oct 25 '18 at 21:57
I think it's a bad driver or bad interaction between the driver and the display manager. I belive the issue is around DPMI, display power management
– Warren P
Nov 9 '18 at 19:10
I think it's a bad driver or bad interaction between the driver and the display manager. I belive the issue is around DPMI, display power management
– Warren P
Nov 9 '18 at 19:10
add a comment |
Ctrl + Alt + Backspace (pressed twice) will reset the X and kill/close everything you have open on current Desktop session.
On a new log in, please check you screen saver settings and disable lock screen.
answered 10 mins ago
Paul afkPaul afk
413
add a comment |
Ctrl + Alt + Backspace (pressed twice) will reset the X and kill/close everything you have open on current Desktop session.
On a new log in, please check you screen saver settings and disable lock screen.
answered 10 mins ago
Paul afkPaul afk
413
add a comment |
Ctrl + Alt + Backspace (pressed twice) will reset the X and kill/close everything you have open on current Desktop session.
On a new log in, please check you screen saver settings and disable lock screen.
answered 10 mins ago
Paul afkPaul afk
413
Ctrl + Alt + Backspace (pressed twice) will reset the X and kill/close everything you have open on current Desktop session.
On a new log in, please check you screen saver settings and disable lock screen.
answered 10 mins ago
Paul afkPaul afk
413
answered 10 mins ago
Paul afkPaul afk
413
answered 10 mins ago
Paul afkPaul afk
413
answered 10 mins ago
Paul afkPaul afk
413
413
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f557833%2fhow-to-unlock-locked-session%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
OK, seemed to have found a solution to my immediate problem; another thread elsewhere steered me to "Light Locker Setting", which did not appear on any of my desktop menus. I ran it from /usr/bin/light-locker-settings. Setting everything to "never" or no seems to have stopped the session lock. This leaves the question of why the unlock sequence itself failed by going back to the unlock dialog. A bug?
– user215199
Dec 7 '14 at 23:52
same issue here, on a clean xubuntu 14.04, fully updated as of 19 october, 2015 z.z
– hanshenrik
Oct 20 '15 at 1:53
Same problem on fresh install of Debian testing
– hochl
Feb 16 '17 at 12:56