How to unlock locked session? Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 23, 2019 at 23:30UTC (7:30pm US/Eastern)Authentication Failure Switch to greeterXubuntu frozen when locking screenLock 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)

Is it fair for a professor to grade us on the possession of past papers?

How do I tell what width chain my used chainring needs?

How to run automated tests after each commit?

Should a wizard buy fine inks every time he want to copy spells into his spellbook?

Draw 4 of the same figure in the same tikzpicture

What to do with repeated rejections for phd position

Dyck paths with extra diagonals from valleys (Laser construction)

How do I find out the mythology and history of my Fortress?

Is multiple magic items in one inherently imbalanced?

What initially awakened the Balrog?

What is the difference between a "ranged attack" and a "ranged weapon attack"?

What are the discoveries that have been possible with the rejection of positivism?

Why do early math courses focus on the cross sections of a cone and not on other 3D objects?

Converted a Scalar function to a TVF function for parallel execution-Still running in Serial mode

Misunderstanding of Sylow theory

AppleTVs create a chatty alternate WiFi network

Putting class ranking in CV, but against dept guidelines

Is there public access to the Meteor Crater in Arizona?

Customizing QGIS plugins

How to write capital alpha?

Why weren't discrete x86 CPUs ever used in game hardware?

How to report t statistic from R

Random body shuffle every night—can we still function?

What is Adi Shankara referring to when he says "He has Vajra marks on his feet"?



How to unlock locked session?



Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 23, 2019 at 23:30UTC (7:30pm US/Eastern)Authentication Failure Switch to greeterXubuntu frozen when locking screenLock 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)



.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








26















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










share|improve this question

















  • 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

















26















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










share|improve this question

















  • 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













26












26








26


12






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










share|improve this question














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






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Dec 7 '14 at 22:35









user215199user215199

193238




193238







  • 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





    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










7 Answers
7






active

oldest

votes


















32














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.






share|improve this answer

























  • 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


















7














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"






share|improve this answer

























  • 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 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












  • No need to find the correct session id, sudo loginctl unlock-sessions will unlock your session.

    – Benjamin
    Jan 17 at 19:17


















2














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.






share|improve this answer






























    1














    This worked for me:



    sudo service lightdm restart 





    share|improve this answer























    • 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



















    1














    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.






    share|improve this answer

























    • 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



















    1














    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.






    share|improve this answer























    • Only in case you setup Ctrl + Alt + Backspace shortcut in settings.

      – mature
      Feb 27 at 16:48


















    0














    "You'll be redirected to the unlock dialog in a few seconds" is nothing short of a lie (sorry for the subjectivity). Ctl + Alt + F8 will take you to your normal login screen.



    This has been an issue for years. I wonder what it takes to get to the top of the priority fix list. Honestly, Manjaro doesn't have this problem, and its popularity is growing.






    share|improve this answer










    New contributor




    xfce fiend is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.




















      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
      );



      );













      draft saved

      draft discarded


















      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

























      7 Answers
      7






      active

      oldest

      votes








      7 Answers
      7






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      32














      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.






      share|improve this answer

























      • 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















      32














      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.






      share|improve this answer

























      • 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













      32












      32








      32







      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.






      share|improve this answer















      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.







      share|improve this answer














      share|improve this answer



      share|improve this answer








      edited Sep 21 '18 at 9:59









      abu_bua

      4,21981631




      4,21981631










      answered Apr 20 '15 at 12:05









      JBENOITJBENOIT

      42143




      42143












      • 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






      • 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













      7














      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"






      share|improve this answer

























      • 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 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












      • No need to find the correct session id, sudo loginctl unlock-sessions will unlock your session.

        – Benjamin
        Jan 17 at 19:17















      7














      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"






      share|improve this answer

























      • 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 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












      • No need to find the correct session id, sudo loginctl unlock-sessions will unlock your session.

        – Benjamin
        Jan 17 at 19:17













      7












      7








      7







      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"






      share|improve this answer















      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"







      share|improve this answer














      share|improve this answer



      share|improve this answer








      edited Sep 21 '18 at 10:00









      abu_bua

      4,21981631




      4,21981631










      answered Aug 8 '16 at 1:10









      Chen Deng-TaChen Deng-Ta

      11219




      11219












      • 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 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












      • No need to find the correct session id, sudo loginctl unlock-sessions will 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






      • 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











      • 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
















      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











      2














      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.






      share|improve this answer



























        2














        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.






        share|improve this answer

























          2












          2








          2







          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.






          share|improve this answer













          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.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Sep 17 '18 at 6:19









          Alex.OAlex.O

          211




          211





















              1














              This worked for me:



              sudo service lightdm restart 





              share|improve this answer























              • 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
















              1














              This worked for me:



              sudo service lightdm restart 





              share|improve this answer























              • 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














              1












              1








              1







              This worked for me:



              sudo service lightdm restart 





              share|improve this answer













              This worked for me:



              sudo service lightdm restart 






              share|improve this answer












              share|improve this answer



              share|improve this answer










              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


















              • 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












              1














              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.






              share|improve this answer

























              • 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
















              1














              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.






              share|improve this answer

























              • 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














              1












              1








              1







              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.






              share|improve this answer















              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.







              share|improve this answer














              share|improve this answer



              share|improve this answer








              edited Sep 21 '18 at 10:01









              abu_bua

              4,21981631




              4,21981631










              answered Apr 23 '18 at 1:15









              TonyTony

              262




              262












              • 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











              • @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












              1














              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.






              share|improve this answer























              • Only in case you setup Ctrl + Alt + Backspace shortcut in settings.

                – mature
                Feb 27 at 16:48















              1














              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.






              share|improve this answer























              • Only in case you setup Ctrl + Alt + Backspace shortcut in settings.

                – mature
                Feb 27 at 16:48













              1












              1








              1







              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.






              share|improve this answer













              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.







              share|improve this answer












              share|improve this answer



              share|improve this answer










              answered Feb 27 at 15:39









              Paul afkPaul afk

              513




              513












              • Only in case you setup Ctrl + Alt + Backspace shortcut in settings.

                – mature
                Feb 27 at 16:48

















              • Only in case you setup Ctrl + Alt + Backspace shortcut in settings.

                – mature
                Feb 27 at 16:48
















              Only in case you setup Ctrl + Alt + Backspace shortcut in settings.

              – mature
              Feb 27 at 16:48





              Only in case you setup Ctrl + Alt + Backspace shortcut in settings.

              – mature
              Feb 27 at 16:48











              0














              "You'll be redirected to the unlock dialog in a few seconds" is nothing short of a lie (sorry for the subjectivity). Ctl + Alt + F8 will take you to your normal login screen.



              This has been an issue for years. I wonder what it takes to get to the top of the priority fix list. Honestly, Manjaro doesn't have this problem, and its popularity is growing.






              share|improve this answer










              New contributor




              xfce fiend is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
              Check out our Code of Conduct.
























                0














                "You'll be redirected to the unlock dialog in a few seconds" is nothing short of a lie (sorry for the subjectivity). Ctl + Alt + F8 will take you to your normal login screen.



                This has been an issue for years. I wonder what it takes to get to the top of the priority fix list. Honestly, Manjaro doesn't have this problem, and its popularity is growing.






                share|improve this answer










                New contributor




                xfce fiend is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.






















                  0












                  0








                  0







                  "You'll be redirected to the unlock dialog in a few seconds" is nothing short of a lie (sorry for the subjectivity). Ctl + Alt + F8 will take you to your normal login screen.



                  This has been an issue for years. I wonder what it takes to get to the top of the priority fix list. Honestly, Manjaro doesn't have this problem, and its popularity is growing.






                  share|improve this answer










                  New contributor




                  xfce fiend is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.










                  "You'll be redirected to the unlock dialog in a few seconds" is nothing short of a lie (sorry for the subjectivity). Ctl + Alt + F8 will take you to your normal login screen.



                  This has been an issue for years. I wonder what it takes to get to the top of the priority fix list. Honestly, Manjaro doesn't have this problem, and its popularity is growing.







                  share|improve this answer










                  New contributor




                  xfce fiend is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.









                  share|improve this answer



                  share|improve this answer








                  edited 1 hour ago





















                  New contributor




                  xfce fiend is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.









                  answered 1 hour ago









                  xfce fiendxfce fiend

                  11




                  11




                  New contributor




                  xfce fiend is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.





                  New contributor





                  xfce fiend is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.






                  xfce fiend is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.



























                      draft saved

                      draft discarded
















































                      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.




                      draft saved


                      draft discarded














                      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





















































                      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







                      Popular posts from this blog

                      Are there any comparative studies done between Ashtavakra Gita and Buddhim?How is it wrong to believe that a self exists, or that it doesn't?Can you criticise or improve Ven. Bodhi's description of MahayanaWas the doctrine of 'Anatta', accepted as doctrine by modern Buddhism, actually taught by the Buddha?Relationship between Buddhism, Hinduism and Yoga?Comparison of Nirvana, Tao and Brahman/AtmaIs there a distinction between “ego identity” and “craving/hating”?Are there many differences between Taoism and Buddhism?Loss of “faith” in buddhismSimilarity between creation in Abrahamic religions and beginning of life in Earth mentioned Agganna Sutta?Are there studies about the difference between meditating in the morning versus in the evening?Can one follow Hinduism and Buddhism at the same time?Are there any prohibitions on participating in other religion's practices?Psychology of 'flow'

                      fallocate: fallocate failed: Text file busy in Ubuntu 17.04? Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)defragmenting and increasing performance of old lubuntu system with swap partitionIssue with increasing the root partition from the swapthis /usr/bin/dpkg returned error || ubuntu-16.04, 64bitDefault 17.04 swap file locationHow to Resize Ubuntu 17.04 Zesty Swap file size?Ubuntu freezes from online formsMy Laptop is not starting after upgrade ubuntu 16.04 (Kernel 4.8.0-38 to 04.10.0-36)hcp: ERROR: FALLOCATE FAILED!Not sure my swap is being usedWine 3.0 asking for more virtual free swap

                      Where else does the Shulchan Aruch quote an authority by name?Parashat Metzora+HagadolPesach/PassoverShulchan Aruch UTF-8Anonymous glosses in the Shulchan AruchWhy is the Shulchan Aruch definitive?Siman 32, Kitzur Shulchan Aruch: UntranslatedLitvaks/Yeshivish and Shulchan AruchBuying a Shulchan AruchEnglish version of SHULCHAN ARUCHIs there any place where Shulchan Aruch rules with the Rosh against the Rif and Rambam?Are there practices where Sepharadim do not hold by Shulchan Aruch?5th part of the shulchan aruch