After today's upgrade (Tumbleweed), I can no longer log in via the wayland session

After today’s upgrade (Tumbleweed), I suddenly can no longer log in via the wayland session.
When I switch to X11 it works.
Are there any other incidents of this kind?
Is there already a bug report on this?

Operating System: openSUSE Tumbleweed 20241122
KDE Plasma Version: 6.2.3
KDE Frameworks Version: 6.8.0
Qt Version: 6.8.0
Kernel Version: 6.11.8-1-default (64-bit)
Graphics Platform: X11
Graphics Processor: llvmpipe (<==== what means this now? i have amdgpu (radeon)

1 Like

For additional information. As always, I did the upgrade with Zypper. went through perfectly without any error messages

Did you use “zypper dup”? What does “I can no longer login” mean? There is no password prompt?

I always use zypper dup.
Yes the login screen shows a password prompt

Here are some journal entrys filtering sddm:

Starting Wayland user session: “/usr/share/sddm/scripts/wayland-session” “/usr/libexec/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland”

Failed to write utmpx: Datei oder Verzeichnis nicht gefunden

pam_systemd(sddm:session): New sd-bus connection (system-bus-pam-systemd-25392) opened.

pam_unix(sddm:session): session closed for user Max

After the login with wayland failed i switch to X11 and the login works.

Here are some journal entries filtering wayland:
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vkkhrdisplay, vnc, xcb, wayland-egl, wayland.

Process 25680 (xwaylandvideobr) of user 1000 dumped core.

Stack trace of thread 25680:
#0 0x00007f992ec9a25c __pthread_kill_implementation (libc.so.6 + 0x9a25c)
#1 0x00007f992ec414b6 raise (libc.so.6 + 0x414b6)
#2 0x00007f992ec2891a abort (libc.so.6 + 0x2891a)
#3 0x00007f992f4f31d2 n/a (libQt6Core.so.6 + 0xf31d2)
#4 0x00007f992f4f40e8 _ZNK14QMessageLogger5fatalEPKcz (libQt6Core.so.6 + 0xf40e8)
#5 0x00007f992fd73dc1 n/a (libQt6Gui.so.6 + 0x173dc1)
#6 0x00007f992fe10538 _ZN22QGuiApplicationPrivate21createEventDispatcherEv (libQt6Gui.so.6 + 0x210538)
#7 0x00007f992f5b01fd _ZN23QCoreApplicationPrivate4initEv (libQt6Core.so.6 + 0x1b01fd)
#8 0x00007f992fe105be _ZN22QGuiApplicationPrivate4initEv (libQt6Gui.so.6 + 0x2105be)
#9 0x00007f99307dae7d _ZN19QApplicationPrivate4initEv (libQt6Widgets.so.6 + 0x1dae7d)
#10 0x0000564cf0d8d40f n/a (xwaylandvideobridge + 0xa40f)
#11 0x00007f992ec2a2ae __libc_start_call_main (libc.so.6 + 0x2a2ae)
#12 0x00007f992ec2a379 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a379)
#13 0x0000564cf0d8d8f5 n/a (xwaylandvideobridge + 0xa8f5)

Stack trace of thread 25731:
#0 0x00007f992ed0f186 ppoll (libc.so.6 + 0x10f186)
#1 0x00007f992e102d9f n/a (libglib-2.0.so.0 + 0x60d9f)
#2 0x00007f992e1034bc g_main_context_iteration (libglib-2.0.so.0 + 0x614bc)
#3 0x00007f992f7fe043 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x3fe043)
#4 0x00007f992f5b6602 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x1b6602)
#5 0x00007f992f6a2a8c _ZN7QThread4execEv (libQt6Core.so.6 + 0x2a2a8c)
#6 0x00007f992fb7722e n/a (libQt6DBus.so.6 + 0x3c22e)
#7 0x00007f992f71ccf9 n/a (libQt6Core.so.6 + 0x31ccf9)
#8 0x00007f992ec983b2 start_thread (libc.so.6 + 0x983b2)
#9 0x00007f992ed1d5fc __clone3 (libc.so.6 + 0x11d5fc)
ELF object binary architecture: AMD x86-64

app-org.kde.xwaylandvideobridge@autostart.service: Main process exited, code=dumped, status=6/ABRT

app-org.kde.xwaylandvideobridge@autostart.service: Failed with result ‘core-dump’.

HAve this issue too, it is related to the mesa conflicts.

Yes indeed!
Journal entries filtering ‘mesa’ are full:
MESA-LOADER: failed to open dri: /usr/lib64/gbm/dri_gbm.so: Kann die Shared-Object-Datei nicht öffnen: Datei oder Verzeichnis nicht gefunden (search paths /usr/lib64/gbm, suffix _gbm)

Damn, what a ■■■■■■ upgrade.
Has anyone found a bug port yet?

https://bugzilla.opensuse.org/show_bug.cgi?id=1233596

TW20241122 with KDE and AMD Ryzen 7 works fine here. Are your Mesa packages from Packman? Move back to openSUSE.

My standard login runs via wayland. I enter my password on the login screen. It takes about 1-2 seconds and I end up on the login screen again (loop).

I then switch to X11 and can log in normally

Thanks for the hint. I will have a look

I have checked. Mesa comes completely from the main repository openSUSE

My Mesa comes from the main repository openSUSE

OK, could you please show the output of the following commands:

$ inxi -G
$ lspci -nnk | grep -iA2 VGA
$ dmesg | grep drm

How exactly do we allow one way vendor change?

inxi -G
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Ellesmere [Radeon RX
470/480/570/570X/580/580X/590] driver: amdgpu v: kernel
Device-2: Logitech HD Pro Webcam C920 driver: snd-usb-audio,uvcvideo
type: USB
Display: x11 server: X.Org v: 21.1.14 with: Xwayland v: 24.1.4 driver: X:
loaded: modesetting unloaded: vesa gpu: amdgpu resolution: 1: 1920x1200~60Hz
2: 1920x1200~60Hz
API: EGL v: 1.5 drivers: radeonsi,swrast platforms: x11,surfaceless,device
API: OpenGL v: 4.6 compat-v: 4.5 vendor: mesa v: 24.2.7 renderer: llvmpipe
(LLVM 19.1.3 256 bits)
API: Vulkan v: 1.3.296 drivers: N/A surfaces: N/A

lspci -nnk | grep -iA2 VGA
0b:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev e7)
Subsystem: Micro-Star International Co., Ltd. [MSI] Radeon RX 580 ARMOR 8G OC [1462:3418]
Kernel driver in use: amdgpu

dmesg | grep drm
[ 0.634767] [ T1] ACPI: bus type drm_connector registered
[ 0.637020] [ T1] [drm] Initialized simpledrm 1.0.0 for simple-framebuffer.0 on minor 0
[ 0.640255] [ T1] simple-framebuffer simple-framebuffer.0: [drm] fb0: simpledrmdrmfb frame buffer device
[ 4.869354] [ T497] [drm] amdgpu kernel modesetting enabled.
[ 4.869746] [ T497] [drm] initializing kernel modesetting (POLARIS10 0x1002:0x67DF 0x1462:0x3418 0xE7).
[ 4.869759] [ T497] [drm] register mmio base: 0xFCE00000
[ 4.869761] [ T497] [drm] register mmio size: 262144
[ 4.869829] [ T497] [drm] add ip block number 0 <vi_common>
[ 4.869831] [ T497] [drm] add ip block number 1 <gmc_v8_0>
[ 4.869833] [ T497] [drm] add ip block number 2 <tonga_ih>
[ 4.869835] [ T497] [drm] add ip block number 3 <gfx_v8_0>
[ 4.869836] [ T497] [drm] add ip block number 4 <sdma_v3_0>
[ 4.869838] [ T497] [drm] add ip block number 5
[ 4.869840] [ T497] [drm] add ip block number 6
[ 4.869842] [ T497] [drm] add ip block number 7 <uvd_v6_0>
[ 4.869843] [ T497] [drm] add ip block number 8 <vce_v3_0>
[ 4.871739] [ T497] [drm] UVD is enabled in VM mode
[ 4.871741] [ T497] [drm] UVD ENC is enabled in VM mode
[ 4.871743] [ T497] [drm] VCE enabled in VM mode
[ 4.940370] [ T497] [drm] vm size is 128 GB, 2 levels, block size is 10-bit, fragment size is 9-bit
[ 4.941995] [ T497] [drm] Detected VRAM RAM=8192M, BAR=256M
[ 4.941997] [ T497] [drm] RAM width 256bits GDDR5
[ 4.942101] [ T497] [drm] amdgpu: 8192M of VRAM memory ready
[ 4.942104] [ T497] [drm] amdgpu: 16003M of GTT memory ready.
[ 4.942122] [ T497] [drm] GART: num cpu pages 65536, num gpu pages 65536
[ 4.943799] [ T497] [drm] PCIE GART of 256M enabled (table at 0x000000F400300000).
[ 4.946728] [ T497] [drm] Chained IB support enabled!
[ 4.972713] [ T497] [drm] Found UVD firmware Version: 1.130 Family ID: 16
[ 4.980760] [ T497] [drm] Found VCE firmware Version: 53.26 Binary ID: 3
[ 5.301388] [ T497] [drm] Display Core v3.2.291 initialized on DCE 11.2
[ 5.566405] [ T497] [drm] UVD and UVD ENC initialized successfully.
[ 5.667331] [ T497] [drm] VCE initialized successfully.
[ 5.672810] [ T497] [drm] Initialized amdgpu 3.59.0 for 0000:0b:00.0 on minor 1
[ 5.693087] [ T497] fbcon: amdgpudrmfb (fb0) is primary device
[ 5.693162] [ T497] amdgpu 0000:0b:00.0: [drm] fb0: amdgpudrmfb frame buffer device
[ 39.728286] [ T1] systemd[1]: Starting Load Kernel Module drm…
[ 39.746592] [ T1] systemd[1]: modprobe@drm.service: Deactivated successfully.
[ 39.746731] [ T1] systemd[1]: Finished Load Kernel Module drm.
[ 5648.298537] [ T17428] [drm] PCIE GART of 256M enabled (table at 0x000000F400300000).
[ 5648.634121] [ T17428] [drm] UVD and UVD ENC initialized successfully.
[ 5648.735092] [ T17428] [drm] VCE initialized successfully.

In Yast it is possible for example