Upgrade to KDE6 - black screen with cursor only

Laserpithium · 2024-03-08 08:17:51

Good morning,

Like many of us recently, I just upgraded my system (pacman -Syu) and thus moved to KDE6. Everything went well with no error message.

At reboot, I however ends-up with a black screen with a cursor (that I can move), nothing more.

I suspected an issue with SDDM and run through the wiki page, but to me it looks properly configured:

cat /etc/sddm.conf.d/10-wayland.conf
[General]
GreeterEnvironment=QT_WAYLAND_SHELL_INTEGRATION=layer-shell
Numlock=on
[Wayland]
CompositorCommand=kwin-wayland --drm --no-lockscreen --no-global-shortcuts --locale1

I try to restart the sddm service, no effect.

I then deleted the whole .config/ folder (or rather moved it to some .config.old/) and rebooted => no improvement

I am not using the NVidia drivers.

And here I am stucked...

seth · 2024-03-08 08:45:08

For a shotgun approach, please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

and the output of "printenv".
See whether there're crashes in https://wiki.archlinux.org/title/Core_d … _core_dump

KDE6 on X11 works as expected?

Laserpithium · 2024-03-08 09:14:19

SHELL=/usr/bin/bash
LESS=-R
CREDENTIALS_DIRECTORY=/run/credentials/getty@tty2.service
MEMORY_PRESSURE_WRITE=c29tZSAyMDAwMDAgMjAwMDAwMAA=
FSCK=fsck -p 
GPG_TTY=/dev/tty2
EDITOR=nano
XDG_SEAT=seat0
PWD=/home/gilgamesh
LOGNAME=gilgamesh
XDG_SESSION_TYPE=tty
SYSTEMD_EXEC_PID=712
MOTD_SHOWN=pam
HOME=/home/gilgamesh
_PMT_DEBUG_LEVEL=0
LANG=fr_FR.UTF-8
MEMORY_PRESSURE_WATCH=/sys/fs/cgroup/system.slice/system-getty.slice/getty@tty2.service/memory.pressure
INVOCATION_ID=fea80188f9884bd388ba26996d4b3ab5
XDG_SESSION_CLASS=user
TERM=linux
USER=gilgamesh
SHLVL=1
XDG_VTNR=2
XDG_SESSION_ID=2
XDG_RUNTIME_DIR=/run/user/1000
DEBUGINFOD_URLS=https://debuginfod.archlinux.org 
PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
MAIL=/var/spool/mail/gilgamesh
_=/usr/bin/printenv

sudo journalctl -b | curl -F 'file=@-' 0x0.st
https://0x0.st/Hhzl.txt

seth · 2024-03-08 09:33:39

The issue seems rather w/ sddm than w/ a plasma session?

mars 08 10:00:26 uruk sddm-greeter[645]: Loading theme configuration from "/usr/share/sddm/themes/Uzuri-forAll-Themes/theme.conf"
mars 08 10:00:26 uruk sddm-greeter[645]: Connected to the daemon.
mars 08 10:00:26 uruk sddm[575]: Message received from greeter: Connect
mars 08 10:00:26 uruk sddm-greeter[645]: Loading file:///usr/share/sddm/themes/Uzuri-forAll-Themes/Main.qml...
mars 08 10:00:26 uruk kernel: [UFW BLOCK] IN=wlan0 OUT= MAC= SRC=fe80:0000:0000:0000:9e29:76ff:fec5:2a88 DST=ff02:0000:0000:0000:0000:0000:0001:0003 LEN=70 TC=0 HOPLIMIT=255 FLOWLBL=387394 PROTO=UDP SPT=5355 DPT=5355 LEN=30 
mars 08 10:00:26 uruk sddm-greeter[645]: QObject: Cannot create children for a parent that is in a different thread.
                                         (Parent is QGuiApplication(0x7fff17f3da30), parent's thread is QThread(0x63aa0cad6e80), current thread is QThread(0x63aa0cbfa680)
mars 08 10:00:26 uruk sddm-greeter[645]: QObject: Cannot create children for a parent that is in a different thread.
                                         (Parent is QGuiApplication(0x7fff17f3da30), parent's thread is QThread(0x63aa0cad6e80), current thread is QThread(0x63aa0cbfa680)
mars 08 10:00:26 uruk sddm-greeter[645]: QObject: Cannot create children for a parent that is in a different thread.
                                         (Parent is QGuiApplication(0x7fff17f3da30), parent's thread is QThread(0x63aa0cad6e80), current thread is QThread(0x63aa0cbfa680)
mars 08 10:00:26 uruk sddm-greeter[645]: QObject::installEventFilter(): Cannot filter events for objects in a different thread.
mars 08 10:00:26 uruk kernel: [UFW BLOCK] IN=wlan0 OUT= MAC= SRC=fe80:0000:0000:0000:9e29:76ff:fec5:2a88 DST=ff02:0000:0000:0000:0000:0000:0001:0003 LEN=70 TC=0 HOPLIMIT=255 FLOWLBL=387394 PROTO=UDP SPT=5355 DPT=5355 LEN=30 
mars 08 10:00:26 uruk sddm-greeter[645]: file:///usr/share/sddm/themes/Uzuri-forAll-Themes/Main.qml:581:21: QML Image: Cannot open: file:///usr/share/sddm/themes/Uzuri-forAll-Themes/images/capslock.svg
mars 08 10:00:26 uruk sddm-greeter[645]: file:///usr/share/sddm/themes/Uzuri-forAll-Themes/Main.qml:387:21: QML Image: Cannot open: file:///var/lib/AccountsService/icons/gilgamesh
mars 08 10:00:26 uruk sddm-greeter[645]: file:///usr/share/sddm/themes/Uzuri-forAll-Themes/Main.qml:344:13: QML Grid: Cannot specify anchors for items inside Grid. Grid will not function.
mars 08 10:00:26 uruk sddm-greeter[645]: file:///usr/share/sddm/themes/Uzuri-forAll-Themes/Main.qml:223:8: QML Rectangle: Detected anchors on an item that is managed by a layout. This is undefined behavior; use Layout.alignment instead.
mars 08 10:00:26 uruk sddm-greeter[645]: file:///usr/share/sddm/themes/Uzuri-forAll-Themes/Main.qml:238:9: QML Rectangle: Detected anchors on an item that is managed by a layout. This is undefined behavior; use Layout.alignment instead.
mars 08 10:00:26 uruk kernel: [UFW BLOCK] IN=wlan0 OUT= MAC= SRC=fe80:0000:0000:0000:9e29:76ff:fec5:2a88 DST=ff02:0000:0000:0000:0000:0000:0001:0003 LEN=70 TC=0 HOPLIMIT=255 FLOWLBL=387394 PROTO=UDP SPT=5355 DPT=5355 LEN=30 
mars 08 10:00:26 uruk sddm-greeter[645]: file:///usr/share/sddm/themes/Uzuri-forAll-Themes/Main.qml:31:5: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
mars 08 10:00:26 uruk sddm-greeter[645]: file:///usr/share/sddm/themes/Uzuri-forAll-Themes/components/VirtualKeyboard.qml:20:1: module "QtQuick.VirtualKeyboard" is not installed
mars 08 10:00:26 uruk sddm-greeter[645]: file:///usr/share/sddm/themes/Uzuri-forAll-Themes/Main.qml:75: ReferenceError: panel is not defined
mars 08 10:00:26 uruk sddm-greeter[645]: file:///usr/share/sddm/themes/Uzuri-forAll-Themes/Main.qml:81: ReferenceError: panel is not defined
mars 08 10:00:26 uruk sddm-greeter[645]: file:///usr/share/sddm/themes/Uzuri-forAll-Themes/Main.qml:203: ReferenceError: menuitems is not defined
mars 08 10:00:26 uruk sddm-greeter[645]: file:///usr/share/sddm/themes/Uzuri-forAll-Themes/Main.qml:153:21: Unable to assign [undefined] to int
mars 08 10:00:26 uruk sddm-greeter[645]: file:///usr/share/sddm/themes/Uzuri-forAll-Themes/Main.qml:304: ReferenceError: menuitems is not defined
mars 08 10:00:26 uruk sddm-greeter[645]: file:///usr/share/sddm/themes/Uzuri-forAll-Themes/Main.qml:430:25: Unable to assign QQuickImage_QML_22 to QUrl
mars 08 10:00:26 uruk sddm-greeter[645]: Adding view for "HDMI-A-1" QRect(0,0 1920x1080)
mars 08 10:00:26 uruk sddm-greeter[645]: No shell integration named "layer-shell" found
mars 08 10:00:26 uruk sddm-greeter[645]: Loading shell integration failed.
mars 08 10:00:26 uruk sddm-greeter[645]: Attempted to load the following shells ("layer-shell")
mars 08 10:00:26 uruk sddm-greeter[645]: Wayland does not support QWindow::requestActivate()
mars 08 10:00:26 uruk sddm-greeter[645]: Wayland does not support QWindow::requestActivate()
mars 08 10:00:27 uruk sddm-greeter[645]: Message received from daemon: Capabilities
mars 08 10:00:27 uruk sddm-greeter[645]: Message received from daemon: HostName
mars 08 10:00:28 uruk systemd[1]: systemd-rfkill.service: Deactivated successfully.
mars 08 10:00:31 uruk sddm-helper-start-wayland[635]: "kwin_wayland_drm: Presentation failed! Permission non accord\xC3\xA9""e\n"

Try to use the default SDDM theme.

mars 08 10:00:31 uruk sddm-helper-start-wayland[635]: "kwin_wayland_drm: Presentation failed! Permission non accord\xC3\xA9""e\n"
mars 08 10:00:31 uruk systemd[1]: Started Getty on tty2.

is probably only because of the VT switch.

Laserpithium · 2024-03-08 10:56:11

Deleting the whole /usr/share/sddm/themes/Uzuri-forAll-Themes/ solved the issue.

Thank you for your guidance!

seth · 2024-03-08 14:09:32

\o/
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

foobat · 2024-03-09 03:47:38

I encountered a simliar problem, but it's with the lockscreen. The lockscreen becomes a black screen with a cusor that can move. And if I blindly type my password, it can be unlocked. How can I reset the settings of the plasma lockscreen?

seth · 2024-03-09 08:06:07

Does KDE Systemsettings have a lockscreen configuration?

kt167 · 2024-03-11 17:46:49

I'm facing the same problem after upgrading to kde6. If I run on X11 all is fine. If I choose Wayland (chosen by default now), I get a black screen with a cursor. I can still launch applications (Win+W shortcut) but the resolution is very poor (issue with display drivers?). I have an nVidia GPU and have installed nvidia, nvidia-lts, nvidia-utils.

@Seth, I tried the dumping the journal as you suggested above. I found the following kwin_wayland related messages/issues. Do you know what is going on? Thanks!

kwin_wayland[1278]: No backend specified, automatically choosing drm
kwin_wayland_wrapper[1278]: MESA-LOADER: failed to open simpledrm: /usr/lib/dri/simpledrm_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/dri, suffix _dri)

kwin_wayland[1278]: OpenGL vendor string:                   Mesa
kwin_wayland[1278]: OpenGL renderer string:                 llvmpipe (LLVM 17.0.6, 256 bits)
kwin_wayland[1278]: OpenGL version string:                  4.5 (Core Profile) Mesa 24.0.2-arch1.2
kwin_wayland[1278]: OpenGL shading language version string: 4.50
kwin_wayland[1278]: Driver:                                 LLVMpipe
kwin_wayland[1278]: GPU class:                              Unknown
kwin_wayland[1278]: OpenGL version:                         4.5
kwin_wayland[1278]: GLSL version:                           4.50
kwin_wayland[1278]: Mesa version:                           24.0.2
kwin_wayland[1278]: Requires strict binding:                no
kwin_wayland[1278]: Virtual Machine:                        no
kwin_wayland[1278]: Timer query support:                    yes
kwin_wayland[1278]: kwin_scene_opengl: No render nodes have been found, falling back to primary node

kwin_wayland[1278]: kwin_wayland_drm: Failed to create framebuffer: Invalid argument
kwin_wayland[1278]: qt.qml.typeresolution.cycle: Cyclic dependency detected between "qrc:/qt/qml/org/kde/desktop/private/TextFieldContextMenu.qml" and "qrc:/qt/qml/org/kde/desktop/MenuItem.qml"

kwin_wayland_wrapper[1414]: Refusing to try glamor on llvmpipe
kwin_wayland_wrapper[1414]: EGL setup failed, disabling glamor
kwin_wayland_wrapper[1414]: Failed to initialize glamor, falling back to sw

kwin_wayland_wrapper[1480]: The XKEYBOARD keymap compiler (xkbcomp) reports:
kwin_wayland_wrapper[1480]: > Warning:          Could not resolve keysym XF86CameraAccessEnable
kwin_wayland_wrapper[1480]: > Warning:          Could not resolve keysym XF86CameraAccessDisable
kwin_wayland_wrapper[1480]: > Warning:          Could not resolve keysym XF86CameraAccessToggle
kwin_wayland_wrapper[1480]: > Warning:          Could not resolve keysym XF86NextElement
kwin_wayland_wrapper[1480]: > Warning:          Could not resolve keysym XF86PreviousElement
kwin_wayland_wrapper[1480]: > Warning:          Could not resolve keysym XF86AutopilotEngageToggle
kwin_wayland_wrapper[1480]: > Warning:          Could not resolve keysym XF86MarkWaypoint
kwin_wayland_wrapper[1480]: > Warning:          Could not resolve keysym XF86Sos
kwin_wayland_wrapper[1480]: > Warning:          Could not resolve keysym XF86NavChart
kwin_wayland_wrapper[1480]: > Warning:          Could not resolve keysym XF86FishingChart
kwin_wayland_wrapper[1480]: > Warning:          Could not resolve keysym XF86SingleRangeRadar
kwin_wayland_wrapper[1480]: > Warning:          Could not resolve keysym XF86DualRangeRadar
kwin_wayland_wrapper[1480]: > Warning:          Could not resolve keysym XF86RadarOverlay
kwin_wayland_wrapper[1480]: > Warning:          Could not resolve keysym XF86TraditionalSonar
kwin_wayland_wrapper[1480]: > Warning:          Could not resolve keysym XF86ClearvuSonar
kwin_wayland_wrapper[1480]: > Warning:          Could not resolve keysym XF86SidevuSonar
kwin_wayland_wrapper[1480]: > Warning:          Could not resolve keysym XF86NavInfo
kwin_wayland_wrapper[1480]: Errors from xkbcomp are not fatal to the X server
kwin_wayland[1278]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11

kwin_wayland_wrapper[1485]: The XKEYBOARD keymap compiler (xkbcomp) reports:
kwin_wayland_wrapper[1485]: > Warning:          Unsupported maximum keycode 708, clipping.
kwin_wayland_wrapper[1485]: >                   X11 cannot support keycodes above 255.

kwin_wayland[1278]: kf.config.core: "\"fsrestore1\" - conversion of \"0,0,0,0\" to QRect failed"
kwin_wayland[1278]: kf.config.core: "\"fsrestore2\" - conversion of \"0,0,0,0\" to QRect failed"
kwin_wayland[1278]: kf.config.core: "\"fsrestore3\" - conversion of \"0,0,0,0\" to QRect failed"

kwin_wayland[1278]: kwin_wayland_drm: Failed to create framebuffer: Invalid argument

seth · 2024-03-11 17:53:12

You don't have a proper drm device and try to run on the simpledrm device.
Why the is is impossble to say from that snippet, you might lack https://wiki.archlinux.org/title/NVIDIA … de_setting - use the "nvidia_drm.modeset=1" kernel parameter (modprobe.conf won't do for killing the simpledrm device)

kt167 · 2024-03-13 00:10:51

Thanks @Seth. I managed to set the "nvidia_drm.modeset=1" kernel parameter by editing grub. When I login using Wayland I can actually see the desktop, and windows are now opening. Progress!

Next issue is that on some windows I see flickering, Trilium is particularly bad. Would you have any advice on this?

Also, I have 2 display-port monitors connected. Resolution on one is fine but not ideal on the other. Because of another issue, I had gotten rid of kscreen a couple of years ago. I have since been using xrandr to position the displays (resolution was fine before). Could this be an xrandr setting or is something else going on that I do not understand?

V1del · 2024-03-13 00:23:42

If you're on Wayland you need to be using kscreen. As for flickering xwayland clients you could try https://aur.archlinux.org/packages/xorg … t-sync-git

... or forego both of these and just switch back to the xorg session in SDDM

kt167 · 2024-03-14 19:17:19

Hello @V1del, thanks for your suggestions. This is just an update. I installed kscreen and xorg-xwayland-explicit-sync-git 23.2.4.r159.g2ef0f1116-1. While kscreen was helpful is setting the resolution, and seemingly didn't give me the black screen issue it did in the past (when waking from power save mode), the flickering issue hasn't gone away. It is quite bad on several applications including VS Code, Trilium and MS Edge. I looked on other threads as well and seems the consensus is to fall back to X11, until nVidia release an implicit sync.

Last edited by kt167 (2024-03-14 19:17:59)

V1del · 2024-03-14 23:15:45

All three of those should be configurable to use native wayland rather than xwayland: https://wiki.archlinux.org/title/Wayland#Electron https://wiki.archlinux.org/title/Chromi … nd_support

kt167 · 2024-03-17 12:03:52

Just an update. I tried configuring chromium and electron to make apps work under Wayland. This was through creating .conf files in the home .config directory. I checked which electron version the apps were using, and then created corresponding .conf files (e.g. electron25-flags.conf, electron27-flags.conf). While VS Code seemed to be working normally, other applications including MS Edge, Zoom and Trilium still had significant issue with flickering. I have decided to stick to X11 for now. When I update my hardware, I'll give Wayland another try. For now, it is really affecting productivity.

Arch Linux

#1 2024-03-08 08:17:51

Upgrade to KDE6 - black screen with cursor only

#2 2024-03-08 08:45:08

Re: Upgrade to KDE6 - black screen with cursor only

#3 2024-03-08 09:14:19

Re: Upgrade to KDE6 - black screen with cursor only

#4 2024-03-08 09:33:39

Re: Upgrade to KDE6 - black screen with cursor only

#5 2024-03-08 10:56:11

Re: Upgrade to KDE6 - black screen with cursor only

#6 2024-03-08 14:09:32

Re: Upgrade to KDE6 - black screen with cursor only

#7 2024-03-09 03:47:38

Re: Upgrade to KDE6 - black screen with cursor only

#8 2024-03-09 08:06:07

Re: Upgrade to KDE6 - black screen with cursor only

#9 2024-03-11 17:46:49

Re: Upgrade to KDE6 - black screen with cursor only

#10 2024-03-11 17:53:12

Re: Upgrade to KDE6 - black screen with cursor only

#11 2024-03-13 00:10:51

Re: Upgrade to KDE6 - black screen with cursor only

#12 2024-03-13 00:23:42

Re: Upgrade to KDE6 - black screen with cursor only

#13 2024-03-14 19:17:19

Re: Upgrade to KDE6 - black screen with cursor only

#14 2024-03-14 23:15:45

Re: Upgrade to KDE6 - black screen with cursor only

#15 2024-03-17 12:03:52

Re: Upgrade to KDE6 - black screen with cursor only

Board footer