KDE Plasma with Wayland black screen issue

antisocial · 2018-02-04 02:17:34

Hi all,

I'm having an issue getting SDDM to log me into KDE with Wayland. The SDDM login page appears fine but if I login with my user when Plasma (Wayland) is selected, I get a black screen with a mouse cursor. I can get a desktop without issue if I login without Wayland.

journalctl -b --unit=sddm.service

-- Logs begin at Sat 2018-02-03 19:11:26 CST, end at Sat 2018-02-03 20:13:50 CST. --
Feb 03 20:13:24 arch systemd[1]: Started Simple Desktop Display Manager.
Feb 03 20:13:24 arch sddm[360]: Initializing...
Feb 03 20:13:24 arch sddm[360]: Logind interface found
Feb 03 20:13:24 arch sddm[360]: Starting...
Feb 03 20:13:24 arch sddm[360]: Adding new display on vt 1 ...
Feb 03 20:13:24 arch sddm[360]: Loading theme configuration from ""
Feb 03 20:13:24 arch sddm[360]: Display server starting...
Feb 03 20:13:24 arch sddm[360]: Running: /usr/bin/X -nolisten tcp -auth /var/run/sddm/{317dec31-5c6e-4825-97d2-6e8d46bd54dd} -background none -noreset -displayfd 17 -seat seat0 vt1
Feb 03 20:13:25 arch sddm[360]: Setting default cursor
Feb 03 20:13:25 arch sddm[360]: Running display setup script  "/usr/share/sddm/scripts/Xsetup"
Feb 03 20:13:25 arch sddm[360]: Display server started.
Feb 03 20:13:25 arch sddm[360]: Socket server starting...
Feb 03 20:13:25 arch sddm[360]: Socket server started.
Feb 03 20:13:25 arch sddm[360]: Loading theme configuration from ""
Feb 03 20:13:25 arch sddm[360]: Greeter starting...
Feb 03 20:13:25 arch sddm[360]: Adding cookie to "/var/run/sddm/{317dec31-5c6e-4825-97d2-6e8d46bd54dd}"
Feb 03 20:13:25 arch sddm-helper[368]: [PAM] Starting...
Feb 03 20:13:25 arch sddm-helper[368]: [PAM] Authenticating...
Feb 03 20:13:25 arch sddm-helper[368]: [PAM] returning.
Feb 03 20:13:25 arch sddm-helper[368]: pam_unix(sddm-greeter:session): session opened for user sddm by (uid=0)
Feb 03 20:13:25 arch sddm[360]: Greeter session started successfully
Feb 03 20:13:25 arch sddm[360]: Message received from greeter: Connect
Feb 03 20:13:31 arch sddm[360]: Message received from greeter: Login
Feb 03 20:13:31 arch sddm[360]: Reading from "/usr/share/wayland-sessions/plasmawayland.desktop"
Feb 03 20:13:31 arch sddm[360]: Reading from "/usr/share/wayland-sessions/plasmawayland.desktop"
Feb 03 20:13:31 arch sddm[360]: Session "/usr/share/wayland-sessions/plasmawayland.desktop" selected, command: "dbus-launch --exit-with-session /usr/bin/startplasmacompositor"
Feb 03 20:13:31 arch sddm-helper[381]: [PAM] Starting...
Feb 03 20:13:31 arch sddm-helper[381]: [PAM] Authenticating...
Feb 03 20:13:31 arch sddm-helper[381]: [PAM] Preparing to converse...
Feb 03 20:13:31 arch sddm-helper[381]: [PAM] Conversation with 1 messages
Feb 03 20:13:31 arch sddm-helper[381]: pam_kwallet5(sddm:auth): (null): pam_sm_authenticate
Feb 03 20:13:31 arch sddm-helper[381]: [PAM] returning.
Feb 03 20:13:31 arch sddm[360]: Authenticated successfully
Feb 03 20:13:31 arch sddm[360]: Jumping to VT 2
Feb 03 20:13:31 arch sddm[360]: VT mode didn't need to be fixed
Feb 03 20:13:31 arch sddm-helper[381]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred
Feb 03 20:13:31 arch sddm-helper[381]: pam_unix(sddm:session): session opened for user zac by (uid=0)
Feb 03 20:13:31 arch sddm[360]: Auth: sddm-helper exited successfully
Feb 03 20:13:31 arch sddm[360]: Greeter stopped.
Feb 03 20:13:31 arch sddm-helper[381]: pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_open_session
Feb 03 20:13:31 arch sddm-helper[381]: pam_kwallet5(sddm:session): pam_kwallet5: final socket path: /run/user/1000/kwallet5.socket
Feb 03 20:13:31 arch sddm-helper[381]: Starting: "/usr/share/sddm/scripts/wayland-session dbus-launch --exit-with-session /usr/bin/startplasmacompositor"
Feb 03 20:13:31 arch sddm[360]: Session started
Feb 03 20:13:33 arch sddm[360]: Auth: sddm-helper exited successfully
Feb 03 20:13:33 arch sddm[360]: Socket server stopping...
Feb 03 20:13:33 arch sddm[360]: Socket server stopped.
Feb 03 20:13:33 arch sddm[360]: Display server stopping...
Feb 03 20:13:38 arch sddm[360]: Removing display ":0" ...
Feb 03 20:13:38 arch sddm[360]: Adding new display on vt 1 ...
Feb 03 20:13:38 arch sddm[360]: Loading theme configuration from ""
Feb 03 20:13:38 arch sddm[360]: Display server starting...
Feb 03 20:13:38 arch sddm[360]: Running: /usr/bin/X -nolisten tcp -auth /var/run/sddm/{71bf78fa-b26d-41f7-9aa3-cb70f0abeefd} -background none -noreset -displayfd 18 -seat seat0 vt1

/etc/sddm.conf

[Autologin]
# Whether sddm should automatically log back into sessions when they exit
Relogin=false

# Name of session file for autologin session (if empty try last logged in)
Session=

# Username for autologin session
User=


[General]
# Halt command
HaltCommand=/usr/bin/systemctl poweroff

# Input method module
InputMethod=qtvirtualkeyboard

# Initial NumLock state. Can be on, off or none.
# If property is set to none, numlock won't be changed
# NOTE: Currently ignored if autologin is enabled.
Numlock=none

# Reboot command
RebootCommand=/usr/bin/systemctl reboot


[Theme]
# Current theme name
Current=

# Cursor theme used in the greeter
CursorTheme=

# Number of users to use as threshold
# above which avatars are disabled
# unless explicitly enabled with EnableAvatars
DisableAvatarsThreshold=7

# Enable display of custom user avatars
EnableAvatars=true

# Global directory for user avatars
# The files should be named <username>.face.icon
FacesDir=/usr/share/sddm/faces

# Theme directory path
ThemeDir=/usr/share/sddm/themes


[Users]
# Default $PATH for logged in users
DefaultPath=/usr/local/bin:/usr/bin:/bin

# Comma-separated list of shells.
# Users with these shells as their default won't be listed
HideShells=

# Comma-separated list of users that should not be listed
HideUsers=

# Maximum user id for displayed users
MaximumUid=60000

# Minimum user id for displayed users
MinimumUid=1000

# Remember the session of the last successfully logged in user
RememberLastSession=true

# Remember the last successfully logged in user
RememberLastUser=true

# When logging in as the same user twice, restore the original session, rather than create a new one
ReuseSession=false


[Wayland]
# Enable Qt's automatic high-DPI scaling
EnableHiDPI=false

# Path to a script to execute when starting the desktop session
SessionCommand=/usr/share/sddm/scripts/wayland-session

# Directory containing available Wayland sessions
SessionDir=/usr/share/wayland-sessions

# Path to the user session log file
SessionLogFile=.local/share/sddm/wayland-session.log


[X11]
# Path to a script to execute when starting the display server
DisplayCommand=/usr/share/sddm/scripts/Xsetup

# Path to a script to execute when stopping the display server
DisplayStopCommand=/usr/share/sddm/scripts/Xstop

# Enable Qt's automatic high-DPI scaling
EnableHiDPI=false

# The lowest virtual terminal number that will be used.
MinimumVT=1

# Arguments passed to the X server invocation
ServerArguments=-nolisten tcp

# Path to X server binary
ServerPath=/usr/bin/X

# Path to a script to execute when starting the desktop session
SessionCommand=/usr/share/sddm/scripts/Xsession

# Directory containing available X sessions
SessionDir=/usr/share/xsessions

# Path to the user session log file
SessionLogFile=.local/share/sddm/xorg-session.log

# Path to the Xauthority file
UserAuthFile=.Xauthority

# Path to xauth binary
XauthPath=/usr/bin/xauth

# Path to Xephyr binary
XephyrPath=/usr/bin/Xephyr

Has anyone else had this issue? What am I doing wrong?

Thank you!

c00ter · 2018-02-04 05:29:21

Hmm...I had not read anywhere that Plasma5 was ready for Wayland quite yet--or vice versa. Is it even now all that stable in GNOME? What are your SDDM login results under Xorg? Are they better? Worse? Perform as expected?

regards

antisocial · 2018-02-04 22:15:12

c00ter wrote:

Hmm...I had not read anywhere that Plasma5 was ready for Wayland quite yet--or vice versa. Is it even now all that stable in GNOME? What are your SDDM login results under Xorg? Are they better? Worse? Perform as expected?
regards

I'm running KDE Plasma 5.11.5 which was installed when installing the 'plasma' group via pacman. The wiki states, to enable wayland support, install the 'plasma-wayland-session' package:
https://wiki.archlinux.org/index.php/KDE

Therefore I'm assuming it's 'ready' or at least compatible.

As far as my results under Xorg, it seems to run fine, haven't ran across any bugs or anything but the problem remains that I'm unable to login via Wayland.
I'd really like to fix this just so I can say for one, that I've installed it and it works, but also to determine whether or not I'd like to continue using it over Xorg.

If anyone has any ideas, please let me know!

Thank you.

c00ter · 2018-02-05 17:16:13

antisocial wrote:

The wiki states, to enable wayland support, install the 'plasma-wayland-session' package:
https://wiki.archlinux.org/index.php/KDE
Therefore I'm assuming it's 'ready' or at least compatible.
If anyone has any ideas, please let me know!
Thank you.

The Wiki states quite alot about KDE & some about Wayland. Follow the link to the Errata. See all the outstanding bugs? https://community.kde.org/Plasma/5.11_Errata#Wayland

From that I think we can probably count on living with Xorg for a while longer. I don't mind it--why jump into something so far away from ready?

Last edited by c00ter (2018-02-05 17:17:42)

arojas · 2018-02-05 18:03:56

Which video card and driver?

antisocial · 2018-02-06 00:46:27

c00ter wrote:

antisocial wrote:
The wiki states, to enable wayland support, install the 'plasma-wayland-session' package:
https://wiki.archlinux.org/index.php/KDE
Therefore I'm assuming it's 'ready' or at least compatible.
If anyone has any ideas, please let me know!
Thank you.
The Wiki states quite alot about KDE & some about Wayland. Follow the link to the Errata. See all the outstanding bugs? https://community.kde.org/Plasma/5.11_Errata#Wayland
From that I think we can probably count on living with Xorg for a while longer. I don't mind it--why jump into something so far away from ready?

From the few posts I've seen about people using Wayland with Plasma, people are very close to using it as a daily driver as soon as a few bugs are fixed, of which none of those bugs I foresee being an issue for me as they're things I don't deal with - therefore I wanted to try it and see if it's right for me. I've read that it is a much "smoother" experience vs running it under Xorg (minus the bugs, ofc).

arojas wrote:

Which video card and driver?

Honestly, that may be my issue. This was a test run in which I was utilizing a Vultr VPS - the machine I would be running it on whenever I decide to try it for real has Intel® HD Graphics 620.

This laptop in particular: https://www.amazon.com/gp/product/B0716 … UTF8&psc=1

Regards.

Arch Linux

#1 2018-02-04 02:17:34

KDE Plasma with Wayland black screen issue

#2 2018-02-04 05:29:21

Re: KDE Plasma with Wayland black screen issue

#3 2018-02-04 22:15:12

Re: KDE Plasma with Wayland black screen issue

#4 2018-02-05 17:16:13

Re: KDE Plasma with Wayland black screen issue

#5 2018-02-05 18:03:56

Re: KDE Plasma with Wayland black screen issue

#6 2018-02-06 00:46:27

Re: KDE Plasma with Wayland black screen issue

Board footer