Differences between revisions 1 and 2
Revision 1 as of 2018-10-03 09:33:18
Size: 1234
Editor: maegger
Comment:
Revision 2 as of 2020-09-02 07:31:29
Size: 1308
Editor: maegger
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
#rev 2020-09-02 maegger
Line 2: Line 3:
Your Linux Client was migrated to Debian Stretch and after the first login the screen remains black and nothing more happens. You try to login to your graphical environmentunder linux, but the screen remains black and nothing more happens.
Line 5: Line 6:
It does not matter if you have a vanilla (empty) account or an account with an old KDE/Plasma profile in it.In Debian Stretch there is a bug which prevents the proper first start of Plasma. To circumvent this problem you have to stop the current session and then login again. It does not matter if you have a vanilla (brand new) account (without any profile folders) or an account with an old KDE/Plasma profile in it. In Debian Stretch there is a bug which prevents the proper first start of Plasma. To circumvent this problem you have to stop the current session and then login again.
Line 20: Line 21:

----
[[CategoryLXCL]]

Problem

You try to login to your graphical environmentunder linux, but the screen remains black and nothing more happens.

Solution

It does not matter if you have a vanilla (brand new) account (without any profile folders) or an account with an old KDE/Plasma profile in it. In Debian Stretch there is a bug which prevents the proper first start of Plasma. To circumvent this problem you have to stop the current session and then login again.

  • Press CTRL-ALT-F1 to switch to the console.

  • Login with your credentials
  • use loginctl list-sessions to check the running sessions. If you have just login through Plasma and have opened a console you should see two sessions. The session under tty1 is the console one, the other one is the Plasma Session:

    $ loginctl list-sessions
       SESSION        UID USER             SEAT             TTY             
             3      16320 username         seat0                            
            49      16320 username         seat0            /dev/tty1       
    
    2 sessions listed.
  • Now you can kill the hanging session (in the above example the first one with SESSION ID 3) with loginctl terminate-session 3

  • After the Login Manager has restored, login again.


CategoryLXCL

FAQ/KDEStretchBlackOn1Login (last edited 2020-09-02 07:33:01 by maegger)