Tumbleweed with KDE desktop; after months with very few issues using Plasma Wayland I am suddenly lost as my last update has left me with a black screen. I tried reverting to the previous snapshot but still didn’t get my desktop screen back. Changing to Plasma X11 has given me a screen but I can hardly recognise the screen and cannot find anything any more as the desktop has no icons or bars anywhere.
Please could somebody help me get back to my working Wayland desktop.
Further to this post there are several references to this problem as a feature of Tumbleweed with KDE desktop and Wayland going back weeks. Unfortunately possible fixes are not clear to me and much well beyond my know how. My temporary solution is to use IceWM but I really do not understand why the issue has not been fixed.
Is there anybody on this forum who can help me please?
Hi Budgie
Please start by sharing the results from
inxi -Gaz
zypper se -si Mesa | grep -E "Mesa|Repository"
Sometimes a mix of Mesa packages from different repos (OSS and Packman) can break Wayland sessions. Let’s verify that before going further.
I have the same issue. I tried to move to Xorg by putting the line WaylandEnable=false in /etc/gdm/custom.conf but it is still stuck on the black screen with Tumbleweed logo. Can’t get a shell with Ctrl+Alt+F1.
Fortunately I have sshd running.
I tried to force the reinstall of Mesa and gdm but it doesn’t solved the issue.
What I have on my side:
$ zypper se -si Mesa | grep -E "Mesa|Repository"
S | Name | Type | Version | Arch | Repository
i+ | Mesa | paquet | 25.2.4-1.1 | x86_64 | Dépôt principal (OSS)
i | Mesa-32bit | paquet | 25.2.4-1.1 | x86_64 | Dépôt principal (OSS)
i | Mesa-demo-egl | paquet | 9.0.0-6.1 | x86_64 | Dépôt principal (OSS)
i | Mesa-demo-x | paquet | 9.0.0-6.1 | x86_64 | Dépôt principal (OSS)
i | Mesa-dri | paquet | 25.2.4-1.1 | x86_64 | Dépôt principal (OSS)
i | Mesa-dri-32bit | paquet | 25.2.4-1.1 | x86_64 | Dépôt principal (OSS)
i | Mesa-KHR-devel | paquet | 25.2.4-1.1 | x86_64 | Dépôt principal (OSS)
i | Mesa-libEGL-devel | paquet | 25.2.4-1.1 | x86_64 | Dépôt principal (OSS)
i+ | Mesa-libEGL1 | paquet | 25.2.4-1.1 | x86_64 | Dépôt principal (OSS)
i | Mesa-libGL-devel | paquet | 25.2.4-1.1 | x86_64 | Dépôt principal (OSS)
i | Mesa-libGL1 | paquet | 25.2.4-1.1 | x86_64 | Dépôt principal (OSS)
i | Mesa-libGL1-32bit | paquet | 25.2.4-1.1 | x86_64 | Dépôt principal (OSS)
i | Mesa-libva | paquet | 25.2.4-1.1 | x86_64 | Dépôt principal (OSS)
i+ | Mesa-vulkan-device-select | paquet | 25.2.4-1.1 | x86_64 | Dépôt principal (OSS)
i+ | Mesa-vulkan-device-select-32bit | paquet | 25.2.4-1.1 | x86_64 | Dépôt principal (OSS)
$ sudo inxi -Gaz
Graphics:
Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics vendor: ASUSTeK
driver: i915 v: kernel arch: Gen-6 code: Sandybridge process: Intel 32nm built: 2011 ports:
active: HDMI-A-1 empty: DP-1, DP-2, HDMI-A-2, VGA-1 bus-ID: 00:02.0 chip-ID: 8086:0102
class-ID: 0300
Display: unspecified server: X.org v: 1.21.1.15 with: Xwayland v: 24.1.8 driver: X:
loaded: modesetting unloaded: vesa alternate: fbdev,intel dri: crocus gpu: i915 tty: 237x58
Monitor-1: HDMI-A-1 model: Idek Iiyama PL2790 serial: <filter> built: 2014 res: 1920x1080
dpi: 82 gamma: 1.2 size: 598x336mm (23.54x13.23") diag: 686mm (27") ratio: 16:9 modes:
max: 1920x1080 min: 720x400
API: EGL v: 1.5 hw: drv: intel crocus platforms: device: 0 drv: crocus device: 1 drv: swrast
gbm: drv: crocus surfaceless: drv: crocus inactive: wayland,x11
API: OpenGL v: 4.5 compat-v: 3.3 vendor: mesa v: 25.2.4 note: console (EGL sourced)
renderer: Mesa Intel HD Graphics 2000 (SNB GT1), llvmpipe (LLVM 21.1.2 256 bits)
API: Vulkan v: 1.4.321 layers: 1 device: 0 type: cpu name: llvmpipe (LLVM 21.1.2 256 bits)
driver: mesa llvmpipe v: 25.2.4 (LLVM 21.1.2) device-ID: 10005:0000 surfaces: N/A
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo de: kscreen-console,kscreen-doctor
wl: wayland-info x11: xdpyinfo, xprop, xrandr
Do you use gdm?
/usr/sbin/update-alternatives --display default-displaymanager
Yes I’m using gdm. I asked Gemini for help. It spotted that I had several login manager, gave me some commands to remove ssdm. I did that, forced reinstall of mesa and gdm, did not solved anything.
systemctl unit showed graphical.target was dead but I had no entries in journalctl gdm.
Finally I did a snapper rollback to oct 7th and I got my gdm back.
Here is the output of your command it it may help:
default-displaymanager - auto mode
link best version is /usr/lib/X11/displaymanagers/gdm
link currently points to /usr/lib/X11/displaymanagers/gdm
link default-displaymanager is /usr/lib/X11/displaymanagers/default-displaymanager
/usr/lib/X11/displaymanagers/console - priority 5
/usr/lib/X11/displaymanagers/gdm - priority 25
/usr/lib/X11/displaymanagers/lightdm - priority 15
/usr/lib/X11/displaymanagers/xdm - priority 10
Could you show the output of inxi -Gaz and the results from the zypper command I gave since doing this please?
Sure, output after rollback:
Graphics:
Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics vendor: ASUSTeK
driver: i915 v: kernel arch: Gen-6 code: Sandybridge process: Intel 32nm built: 2011 ports:
active: HDMI-A-1 empty: DP-1, DP-2, HDMI-A-2, VGA-1 bus-ID: 00:02.0 chip-ID: 8086:0102
class-ID: 0300
Display: unspecified server: X.org v: 1.21.1.15 with: Xwayland v: 24.1.8 driver: X:
loaded: modesetting unloaded: vesa alternate: fbdev,intel dri: crocus gpu: i915 tty: 237x58
Monitor-1: HDMI-A-1 model: Idek Iiyama PL2790 serial: <filter> built: 2014 res: 1920x1080
dpi: 82 gamma: 1.2 size: 598x336mm (23.54x13.23") diag: 686mm (27") ratio: 16:9 modes:
max: 1920x1080 min: 720x400
API: EGL v: 1.5 hw: drv: intel crocus platforms: device: 0 drv: crocus device: 1 drv: swrast
gbm: drv: crocus surfaceless: drv: crocus inactive: wayland,x11
API: OpenGL v: 4.5 compat-v: 3.3 vendor: mesa v: 25.2.2 note: console (EGL sourced)
renderer: Mesa Intel HD Graphics 2000 (SNB GT1), llvmpipe (LLVM 21.1.0 256 bits)
API: Vulkan v: 1.4.321 layers: 1 device: 0 type: cpu name: llvmpipe (LLVM 21.1.0 256 bits)
driver: mesa llvmpipe v: 25.2.2 (LLVM 21.1.0) device-ID: 10005:0000 surfaces: N/A
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo de: kscreen-console,kscreen-doctor
wl: wayland-info x11: xdpyinfo, xprop, xrandr
S | Name | Type | Version | Arch | Repository
i+ | Mesa | paquet | 25.2.2-424.1 | x86_64 | (Paquets système)
i | Mesa-32bit | paquet | 25.2.2-424.1 | x86_64 | (Paquets système)
i | Mesa-demo-egl | paquet | 9.0.0-5.1 | x86_64 | (Paquets système)
i | Mesa-demo-x | paquet | 9.0.0-5.1 | x86_64 | (Paquets système)
i | Mesa-dri | paquet | 25.2.2-424.1 | x86_64 | (Paquets système)
i | Mesa-dri-32bit | paquet | 25.2.2-424.1 | x86_64 | (Paquets système)
i | Mesa-KHR-devel | paquet | 25.2.2-424.1 | x86_64 | (Paquets système)
i | Mesa-libEGL-devel | paquet | 25.2.2-424.1 | x86_64 | (Paquets système)
i+ | Mesa-libEGL1 | paquet | 25.2.2-424.1 | x86_64 | (Paquets système)
i | Mesa-libGL-devel | paquet | 25.2.2-424.1 | x86_64 | (Paquets système)
i | Mesa-libGL1 | paquet | 25.2.2-424.1 | x86_64 | (Paquets système)
i | Mesa-libGL1-32bit | paquet | 25.2.2-424.1 | x86_64 | (Paquets système)
i | Mesa-libva | paquet | 25.2.2-424.1 | x86_64 | (Paquets système)
i+ | Mesa-vulkan-device-select | paquet | 25.2.2-424.1 | x86_64 | (Paquets système)
i+ | Mesa-vulkan-device-select-32bit | paquet | 25.2.2-424.1 | x86_64 | (Paquets système)
Indicative of a Mesa regression. A bug report needed.
Hi Dean,
Many thanks for the reply. I see that I am not the only one but I have been slower to try and solve myself. In the end I rolled back and stopped my timer for updater until I really understand or try to understand the problem. Will post my data tomorrow.
Have you read this one:
https://bugzilla.suse.com/show_bug.cgi?id=1250513
This is the solution:
https://bugzilla.suse.com/show_bug.cgi?id=1250513#c2
I’m not sure that is applicable here? In any case Budgie is using Plasma Wayland until hit by this regression.
Hi Dean,
Apologies for not getting back to you sooner. It is not that I had ignored your reply but I lost work time trying to restore my machine and I have no idea what the issue was or the fix. I rolled back to get working again but my system is btrfs and no separate home partition so I had to restore all my added system components and local system stuff too.
This evening and for no reason that I can identify my system stalled and in the end I had to reboot and now I am back to black screen except that this time I have a mouse. For now I have given and am using laptop and office machine which is on Leap15.6. Will look at reverting to Leap on problem machine tomorrow and sorry I cannot add anything useful.
After sleeping on it I have the following:-
alastair@HP-Z640-1:~> inxi -Gaz
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Ellesmere [Radeon Pro WX 7100]
vendor: Dell driver: amdgpu v: kernel arch: GCN-4 code: Arctic Islands
process: GF 14nm built: 2016-20 pcie: gen: 3 speed: 8 GT/s lanes: 16
ports: active: DP-4 empty: DP-1,DP-2,DP-3 bus-ID: 02:00.0
chip-ID: 1002:67c4 class-ID: 0300 temp: 46.0 C
Display: wayland server: X.org v: 1.21.1.15 with: Xwayland v: 24.1.8
compositor: kwin_wayland driver: X: loaded: modesetting unloaded: vesa
alternate: fbdev dri: radeonsi gpu: amdgpu display-ID: 0
Monitor-1: DP-4 model: Asus PB258 serial: <filter> built: 2015 res:
mode: 2560x1440 hz: 60 scale: 100% (1) dpi: 118 gamma: 1.2
size: 553x311mm (21.77x12.24") diag: 634mm (25") ratio: 16:9 modes:
max: 2560x1440 min: 720x400
API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
device: 1 drv: swrast gbm: drv: kms_swrast surfaceless: drv: radeonsi
wayland: drv: radeonsi x11: drv: radeonsi
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 25.2.4 glx-v: 1.4
direct-render: yes renderer: AMD Radeon Pro WX 7100 Graphics (radeonsi
polaris10 ACO DRM 3.64 6.17.1-1-default) device-ID: 1002:67c4
memory: 7.81 GiB unified: no display-ID: :0.0
API: Vulkan v: 1.4.328 layers: 1 device: 0 type: discrete-gpu name: AMD
Radeon Pro WX 7100 Graphics (RADV POLARIS10) driver: mesa radv v: 25.2.4
device-ID: 1002:67c4 surfaces: N/A device: 1 type: cpu name: llvmpipe
(LLVM 21.1.3 256 bits) driver: mesa llvmpipe v: 25.2.4 (LLVM 21.1.3)
device-ID: 10005:0000 surfaces: N/A
Info: Tools: api: eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor wl: wayland-info
x11: xdpyinfo, xprop, xrandr
alastair@HP-Z640-1:~>
The symptoms from last night were black screen as before but with mouse working.
I also have:-
alastair@HP-Z640-1:/etc> cat nsswitch.conf
#
# /etc/nsswitch.conf
#
# An example Name Service Switch config file. This file should be
# sorted with the most-used services at the beginning.
#
# Valid databases are: aliases, ethers, group, gshadow, hosts,
# initgroups, netgroup, networks, passwd, protocols, publickey,
# rpc, services, and shadow.
#
# Valid service provider entries include (in alphabetical order):
#
# compat Use /etc files plus *_compat pseudo-db
# db Use the pre-processed /var/db files
# dns Use DNS (Domain Name Service)
# files Use the local files in /etc
# hesiod Use Hesiod (DNS) for user lookups
# nis Use NIS (NIS version 2), also called YP
# nisplus Use NIS+ (NIS version 3)
#
# See `info libc 'NSS Basics'` for more information.
#
# Commonly used alternative service providers (may need installation):
#
# ldap Use LDAP directory server
# myhostname Use systemd host names
# mymachines Use systemd machine names
# mdns*, mdns*_minimal Use Avahi mDNS/DNS-SD
# resolve Use systemd resolved resolver
# sss Use System Security Services Daemon (sssd)
# systemd Use systemd for dynamic user option
# winbind Use Samba winbind support
# wins Use Samba wins support
# wrapper Use wrapper module for testing
#
# Notes:
#
# 'sssd' performs its own 'files'-based caching, so it should generally
# come before 'files'.
#
# WARNING: Running nscd with a secondary caching service like sssd may
# lead to unexpected behaviour, especially with how long
# entries are cached.
#
# Installation instructions:
#
# To use 'db', install the appropriate package(s) (provide 'makedb' and
# libnss_db.so.*), and place the 'db' in front of 'files' for entries
# you want to be looked up first in the databases, like this:
#
# passwd: db files
# shadow: db files
# group: db files
passwd: compat systemd
group: compat [SUCCESS=merge] systemd
shadow: compat systemd
# Allow initgroups to default to the setting for group.
# initgroups: compat
hosts: files mdns_minimal [NOTFOUND=return] dns
networks: files dns
aliases: files usrfiles
ethers: files usrfiles
gshadow: files usrfiles
netgroup: files nis
protocols: files usrfiles
publickey: files
rpc: files usrfiles
services: files usrfiles
automount: files nis
bootparams: files
netmasks: files
alastair@HP-Z640-1:/etc>
which leaves me none the wiser but am still hoping I can identify the underlying issue.
Edit by Sauerland: Code-Tags
Please post output like the above as preformatted text (refer to the </> button in the forum editor).
More about that here:
Hi Dean,
Sorry about that, I have no idea why this happened. Going forward here is the output from your original zypper command:-
alastair@HP-Z640-1:~> zypper se -si Mesa | grep -E "Mesa|Repository"
S | Name | Type | Version | Arch | Repository
i | Mesa | package | 25.2.4-1699.2.pm.2 | x86_64 | (System Packages)
i | Mesa-demo-egl | package | 9.0.0-6.1 | x86_64 | Main Repository (OSS)
i | Mesa-demo-x | package | 9.0.0-6.1 | x86_64 | Main Repository (OSS)
i | Mesa-dri | package | 25.2.4-1699.2.pm.13 | x86_64 | (System Packages)
i | Mesa-libEGL1 | package | 25.2.4-1699.2.pm.2 | x86_64 | (System Packages)
i | Mesa-libGL1 | package | 25.2.4-1699.2.pm.2 | x86_64 | (System Packages)
i | Mesa-libva | package | 25.2.4-1699.2.pm.13 | x86_64 | (System Packages)
i | Mesa-vulkan-device-select | package | 25.2.4-1699.2.pm.13 | x86_64 | (System Packages)
There was also a question concerning gdm and this is what I have on this:-
alastair@HP-Z640-1:~> cat /etc/sysconfig/displaymanager | grep DISPLAYMANAGER=
alastair@HP-Z640-1:~> sudo cat /etc/sysconfig/displaymanager | grep DISPLAYMANAGER=
[sudo] password for root:
alastair@HP-Z640-1:~> ps -e | grep dm
687 ? 00:00:00 kworker/R-amdgpu_dm_hpd_rx_offload_wq
688 ? 00:00:00 kworker/R-amdgpu_dm_hpd_rx_offload_wq
689 ? 00:00:00 kworker/R-amdgpu_dm_hpd_rx_offload_wq
690 ? 00:00:00 kworker/R-amdgpu_dm_hpd_rx_offload_wq
691 ? 00:00:00 kworker/R-dm_vblank_control_workqueue
716 ? 00:00:00 kworker/R-sdma0
717 ? 00:00:00 kworker/R-sdma1
2270 ? 00:00:00 rpc.idmapd
2311 ? 00:00:00 gdm
4265 ? 00:00:00 gdm-session-wor
4998 tty2 00:00:00 gdm-wayland-ses
6763 ? 00:00:00 kworker/R-kdmflush/254:0
6766 ? 00:00:00 dmcrypt_write/254:0
6779 ? 00:00:00 jbd2/dm-0-8
15976 ? 00:00:00 kworker/u96:1-sdma0
alastair@HP-Z640-1:~> systemctl status display-manager.service
● display-manager-legacy.service - X Display Manager
Loaded: loaded (/usr/lib/systemd/system/display-manager-legacy.service; enabled; preset: enabled)
Active: active (running) since Thu 2025-10-23 08:43:35 BST; 1h 8min ago
Invocation: 437fa482c377435ba23dd5705d9cbea3
Process: 2295 ExecStart=/usr/lib/X11/display-manager start (code=exited, status=0/SUCCESS)
Main PID: 2311 (gdm)
Tasks: 5 (limit: 76927)
CPU: 371ms
CGroup: /system.slice/display-manager-legacy.service
└─2311 /usr/sbin/gdm
Edit by Sauerland: Code-Tags
You’ve done it again ^^
….and sauerland tidied up your previous post.
Looking through that output, the display manager is gdm. Try changing to sddm and test again.
This is an explanation from a thread using Code-Tags using the forum software:
Code-Tags
Please read it.
Once again apologies. In a rush between work. Will try hard not to do it again and thanks for the edit.
Turning now to Dean’s suggestion, before I do this it would be good to understand why I am not using sddm as I did not change intentionally. Also I thought this gdm issue had been fixed.