Results 1 to 6 of 6

Thread: Leap 15.2 stuck on login

  1. #1

    Default Leap 15.2 stuck on login

    This is a new install of Leap 15.2.
    I have used nvidia driver G03 on Leap 15.1 but now it is not available on Leap 15.2. I had not got a problem with login.
    When I try to login I can type my password but then system freezes. This is happens on Plasma session. I can only move my mouse pointer on screen.

    When I change to Wayland session I can login but system is not usable like on Plasma session and freezes sometimes.


    I do not have this issue on Tumbleweed.

  2. #2
    Join Date
    Feb 2010
    Location
    Germany
    Posts
    4,363

    Default Re: Leap 15.2 stuck on login

    Quote Originally Posted by rektal View Post
    When I change to Wayland session I can login but system is not usable like on Plasma session and freezes sometimes.
    Before you login via the Display Manager, login via a Virtual Terminal (VT) – tty1 .. tty6 – and change to the ~./config/ directory.
    • Delete all the configuration files.

    Do the same for anything in the ~/.kde4/ directory.
    Also remove everything in the ~/.cache/ directory.
    Check for files owned by you in /tmp/ and /var/tmp/.

    You could also move the Display Manager's log file – ~/.local/share/sddm/xorg-session.log – off to another directory and rename it to include a time-stamp in the file name.

    Move back the Display Manager – it's usually running on tty7 – and attempt to login.

    The current “normal” contents of the xorg-session.log file should be something similar to this:
    Code:
    gpg-connect-agent: Der gpg-agent läuft nicht für diese Session
    gpg-connect-agent: Der gpg-agent läuft nicht für diese Session
    gpg-agent[15295]: enabled debug flags: ipc
    Could not open kded5 using a library: Cannot load library libkdeinit5_kded5: (libkdeinit5_kded5: Kann die Shared-Object-Datei nicht öffnen: Datei oder Verzeichnis nicht gefunden)
    xsettingsd: Loaded 0 settings from /home/Users/dcu/.config/xsettingsd/xsettingsd.conf
    xsettingsd: Created window 0x1400001 on screen 0 with timestamp 8386876
    xsettingsd: Selection _XSETTINGS_S0 is owned by 0x0
    xsettingsd: Took ownership of selection _XSETTINGS_S0
    xsettingsd: Reloading configuration
    xsettingsd: Loaded 10 settings from /home/Users/dcu/.config/xsettingsd/xsettingsd.conf
    xsettingsd: Reloading configuration
    xsettingsd: Loaded 10 settings from /home/Users/dcu/.config/xsettingsd/xsettingsd.conf
    xsettingsd: Reloading configuration
    xsettingsd: Loaded 10 settings from /home/Users/dcu/.config/xsettingsd/xsettingsd.conf
    xsettingsd: Reloading configuration
    xsettingsd: Loaded 10 settings from /home/Users/dcu/.config/xsettingsd/xsettingsd.conf
    xsettingsd: Reloading configuration
    xsettingsd: Loaded 10 settings from /home/Users/dcu/.config/xsettingsd/xsettingsd.conf
    xsettingsd: Reloading configuration
    xsettingsd: Loaded 10 settings from /home/Users/dcu/.config/xsettingsd/xsettingsd.conf
    xsettingsd: Reloading configuration
    xsettingsd: Loaded 10 settings from /home/Users/dcu/.config/xsettingsd/xsettingsd.conf
    xsettingsd: Reloading configuration
    xsettingsd: Loaded 10 settings from /home/Users/dcu/.config/xsettingsd/xsettingsd.conf

  3. #3

    Default Re: Leap 15.2 stuck on login

    I have upgraded to Tumbleweed. It worked.
    After today's update there is the same problem as on Leap 15.2. I cannot login anymore on plasma session.

    I have got a MX Linux KDE on the second drive. I am just trying it. Maybe I will switch to it in the future..

  4. #4

    Default Re: Leap 15.2 stuck on login

    I removed everything from ~/.kde4/ directory and ~/.cache/ directory and it helped.

    Thanks.

  5. #5

    Default Re: Leap 15.2 stuck on login

    And here we go again.
    After last update I can't logging in using plasma session. I have to switch to wayland session.

    Maybe Tumbleweed is not for older graphics.

    I have to switch to another kde distribiution.

  6. #6

    Default Re: Leap 15.2 stuck on login

    I removed again everything from ~/.kde4/ directory and ~/.cache/ directory and it helped.

    But I can't do it every single update.

Tags for this Thread

Posting Permissions

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