Page 1 of 3 123 LastLast
Results 1 to 10 of 26

Thread: after about 24 48 hours of uptime cannot unlock screen, how to investigate?

  1. #1

    Default after about 24 48 hours of uptime cannot unlock screen, how to investigate?

    Hi, on my desktop PC running 15.4 and KDE that I use as home ssh server I usually lock it and switch off the screen and after 12 48 hours I login again,
    very often I found the login screen not usable, the screensaver is there but I cannot insert password to unlock it,
    I can ctrl>alt>F2 and
    Code:
    shutdown -r now
    so I can access it via commandline, how can I investigate why the login screen result not usable?

  2. #2
    Join Date
    Dec 2008
    Location
    FL, USA
    Posts
    4,299
    Blog Entries
    1

    Default Re: after about 24 48 hours of uptime cannot login, how to investigate?

    Quote Originally Posted by pier_andreit View Post
    I can ctrl>alt>F2 and
    Code:
    shutdown -r now
    so I can access it via commandline, how can I investigate why the login screen result not usable?
    I don't know your answer, but you don't need to reboot. Instead of shutdown command, restart X:
    Code:
    systemctl restart xdm
    Reg. Linux User 211409 *** multibooting since 1992
    Primary: 15.4, TW, 15.1 & 13.1 on Haswell @earthlink.net
    Secondary: eComStation (OS/2) &15.4 on i965P/Radeon
    Tertiary: Debian, Fedora, Mageia, more on Rocket Lake & older Intel, AMD, NVidia....

  3. #3
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    31,784

    Default Re: after about 24 48 hours of uptime cannot login, how to investigate?

    The title and the description are contradictory.

    May we assume that it is about "screen unlock" and NOT about "login"?

    When that is correct, I would like to change the thread title for you things are less confusing.
    Henk van Velden

  4. #4
    Join Date
    Feb 2010
    Location
    Germany
    Posts
    5,151

    Default Re: after about 24 48 hours of uptime cannot login, how to investigate?

    Quote Originally Posted by mrmazda View Post
    restart X:
    Code:
    systemctl restart xdm
    Code:
      # systemctl restart display-manager.service
    Or “<Control>+<Alt>+<Delete>+<Delete>” – hit the Delete key twice

  5. #5
    Join Date
    Dec 2008
    Location
    FL, USA
    Posts
    4,299
    Blog Entries
    1

    Default Re: after about 24 48 hours of uptime cannot login, how to investigate?

    Quote Originally Posted by dcurtisfra View Post
    Code:
      # systemctl restart display-manager.service
    Or “<Control>+<Alt>+<Delete>+<Delete>” – hit the Delete key twice
    I think this only works on upgrades from legacy versions, and in newer installations needs to be enabled via /etc/X11/xorg.conf.d/00-keyboard.conf. Lately I've found adding Option "XkbOptions" "terminate:ctrl_alt_bksp" necessary several times.
    Reg. Linux User 211409 *** multibooting since 1992
    Primary: 15.4, TW, 15.1 & 13.1 on Haswell @earthlink.net
    Secondary: eComStation (OS/2) &15.4 on i965P/Radeon
    Tertiary: Debian, Fedora, Mageia, more on Rocket Lake & older Intel, AMD, NVidia....

  6. #6
    Join Date
    Feb 2010
    Location
    Germany
    Posts
    5,151

    Default Re: after about 24 48 hours of uptime cannot login, how to investigate?

    Quote Originally Posted by mrmazda View Post
    Lately I've found adding Option "XkbOptions" "terminate:ctrl_alt_bksp" necessary several times.
    Code:
     > cat /etc/X11/xorg.conf.d/00-keyboard.conf 
    # Written by systemd-localed(8), read by systemd-localed and Xorg. It's
    # probably wise not to edit this file manually. Use localectl(1) to
    # instruct systemd-localed to update it.
    Section "InputClass"
            Identifier "system-keyboard"
            MatchIsKeyboard "on"
            Option "XkbLayout" "de"
            Option "XkbModel" "pc105"
            Option "XkbVariant" "nodeadkeys"
            Option "XkbOptions" "terminate:ctrl_alt_bksp"
    EndSection
     > rpm --query --whatprovides /etc/X11/xorg.conf.d/00-keyboard.conf
    systemd-249.12-150400.8.10.1.x86_64
    >
    Seems to be the default Leap 15.4 and previous setting …
    • I forcibly reinstalled the “systemd” package and, nothing changed – the “XkbOptions” value remained as it was – “terminate:ctrl_alt_bksp” …

  7. #7

    Default Re: after about 24 48 hours of uptime cannot login, how to investigate?

    Quote Originally Posted by hcvv View Post
    The title and the description are contradictory.

    May we assume that it is about "screen unlock" and NOT about "login"?

    When that is correct, I would like to change the thread title for you things are less confusing.
    yes, you are right, I refere to screen unlock not to login, sorry for my technically-poor description, please change the thread title

  8. #8
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    31,784

    Default Re: after about 24 48 hours of uptime cannot login, how to investigate?

    Quote Originally Posted by pier_andreit View Post
    yes, you are right, I refere to screen unlock not to login, sorry for my technically-poor description, please change the thread title
    Done......
    Henk van Velden

  9. #9

    Default Re: after about 24 48 hours of uptime cannot login, how to investigate?

    Quote Originally Posted by mrmazda View Post
    I don't know your answer, but you don't need to reboot. Instead of shutdown command, restart X:
    Code:
    systemctl restart xdm
    Hi, manythanks, I did
    Code:
    systemctl restart xdm
    but it closes all the opened windows, practically is almost the same as to reboot, I would like to unlock the screen and have access at the desktop with all the opened windows,
    or how to investigate why and or what block thescreen unlocking

  10. #10

    Default Re: after about 24 48 hours of uptime cannot login, how to investigate?

    Quote Originally Posted by hcvv View Post
    Done......
    manythanks

Page 1 of 3 123 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •