Not able to log in to Plasma (wayland) after updating

English Install/Boot/Login
1

Following the latest updates, I wasn’t able to log in to Plasma (Wayland). When I type my password, the screen stays black for 1-2 seconds, and before I can log in, the SDDM login appears again instead of logging to KDE. Trying X11 worked… kinda. I was able to enter KDE, but the app windows can’t be minimized, closed, or moved (I can only resize them). I was able to roll back multiple times to the previous snapshot, but every time I update, it’s always the same problem. How can I know what’s causing this problem? Or should I ignore updates for now?


  Kernel: 6.9.7-1-default arch: x86_64 bits: 64 compiler: gcc v: 13.3.0
    clocksource: hpet avail: acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.9.7-1-default
    root=UUID=8314e85f-22f1-4ff1-bba1-63458b98332a splash=silent
    mitigations=auto quiet security=apparmor
  Desktop: KDE Plasma v: 6.1.2 tk: Qt v: N/A info: frameworks v: 6.3.0
    with: krunner tools: avail: xscreensaver vt: 2 dm: SDDM Distro: openSUSE
    Tumbleweed 20240430
Graphics:
  Device-1: NVIDIA TU117M [GeForce GTX 1650 Mobile / Max-Q]
    vendor: Hewlett-Packard driver: N/A alternate: nouveau non-free: 550.xx+
    status: current (as of 2024-04; EOL~2026-12-xx) arch: Turing code: TUxxx
    process: TSMC 12nm FF built: 2018-2022 pcie: gen: 3 speed: 8 GT/s lanes: 8
    link-max: lanes: 16 bus-ID: 01:00.0 chip-ID: 10de:1f99 class-ID: 0300
  Device-2: AMD Cezanne [Radeon Vega Series / Radeon Mobile Series]
    vendor: Hewlett-Packard driver: amdgpu v: kernel arch: GCN-5 code: Vega
    process: GF 14nm built: 2017-20 pcie: gen: 3 speed: 8 GT/s lanes: 16
    link-max: gen: 4 speed: 16 GT/s ports: active: eDP-1 empty: none
    bus-ID: 05:00.0 chip-ID: 1002:1638 class-ID: 0300 temp: 45.0 C
  Device-3: Quanta HP TrueVision HD Camera driver: uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-3:2 chip-ID: 0408:5365
    class-ID: 0e02
  Display: x11 server: X.Org v: 21.1.12 with: Xwayland v: 23.2.6 driver: X:
    loaded: modesetting unloaded: fbdev,vesa dri: radeonsi gpu: amdgpu
    display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 120 s-size: 406x228mm (15.98x8.98")
    s-diag: 466mm (18.33")
  Monitor-1: eDP-1 model: ChiMei InnoLux 0x153b built: 2020 res: 1920x1080
    hz: 60 dpi: 142 gamma: 1.2 size: 344x193mm (13.54x7.6") diag: 394mm (15.5")
    ratio: 16:9 modes: max: 1920x1080 min: 640x480
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
    device: 1 drv: swrast surfaceless: drv: radeonsi x11: drv: radeonsi
    inactive: gbm,wayland
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.0.5 glx-v: 1.4
    direct-render: yes renderer: AMD Radeon Graphics (radeonsi renoir LLVM
    18.1.4 DRM 3.57 6.9.7-1-default) device-ID: 1002:1638 memory: 500 MiB
    unified: no
  API: Vulkan v: 1.3.280 layers: 5 device: 0 type: integrated-gpu name: AMD
    Radeon Graphics (RADV RENOIR) driver: N/A device-ID: 1002:1638
    surfaces: xcb,xlib
2

@zeesuse Have you set the Nvidia GPU as primary (or used the likes of suse-prime). That looks like the Nvidia gpu is a 3D controller, so your display needs the AMD GPU as primary.

Perhaps the kernel and drivers for the Nvidia card are the issue as it’s N/A, or your using the open drivers?

3

no (as far as i know) so now i have to set my AMD gpu as primary ? how can i do it?.

i had the drivers from nvidia official site not the open ones

4

@zeesuse So if you reboot and at grub select advanced and boot from a previous kernel, does it work?

5

no, booting the previous karnel didnt solve it

6

@zeesuse OK, is the suse-prime package present? Can you show the output from /sbin/lspci -nnk | grep -EA3 "VGA|Display|3D" and also /sbin/modinfo nvidia | grep "filename:"

7

thanks for the help, i just solved the problem by running the update again, even tho i fully updated everything before but now new packages to update showed up again? … i also noticed all of nvidias drivers were deleted after the update so i had to reinstall them

8

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.