ASUS X550 laptop
Unable to type or click on KDE login screen. Cannot log in to desktop.
Can move mouse pointer around screen but cannot click anything.
Machine still responds to SSH logins. Updating through zypper did not solve the problem.
Happened something similar to me using Plasma5 and Wayland: I could log in, but if went to tty1 and returned to tty7 it showed login screen with (almost) the behaviour you describe (password box showed asterisks). I had my “desktop” session avaliable at tty2.
Had a similar problem. After running zypper dup, the login screen froze upon next reboot.
I tried to figure out which update caused the issue.
Apparently, updating either libgbm1 23.3.6-369.1 → 24.0.3-372.1 or Mesa 23.3.6-369.1 → 24.0.3-372.1 (and dependencies) results in frozen login screen or looping back to the login screen after entering the password.
Therefore, an SDDM issue …
From a VT, what is the output of the following?
# systemctl status display-manager.service
Check the systemd Journal for any issues around about the time that the Display Manager (SDDM) started.
Hi,
sorry for delay. Just did the update of both libgbm1 and Mesa (and its dependencies) again. Updating both in one run leads to freeze of the login screen instead of looping back after the password was entered.
The systemctl status output is (difference to before the update marked in bold):
display-manager.service - X Display Manager
Loaded: loaded (/usr/lib/systemd/system/display-manager.service; enabled; preset: enabled)
Active: active (running) since Tue 2024-04-16 22:45:39 CEST; 2min 16s ago
Process: 1219 ExecStart=/usr/lib/X11/display-manager start (code=exited, status=0/SUCCESS)
Main PID: 1254 (sddm)
Tasks: 16 (limit: 4915)
CPU: 614ms
CGroup: /system.slice/display-manager.service
├─1254 /usr/bin/sddm
└─1274 /usr/bin/Xorg.bin -nolisten tcp -background none -seat seat0 vt2 -auth /run/sddm/xauth_FcBOKz -noreset -displayfd 16
Apr 16 22:45:40 daka sddm-helper[1327]: [PAM] returning.
Apr 16 22:45:40 daka sddm-helper[1327]: pam_unix(sddm-greeter:session): session opened for user sddm(uid=461) by sddm(uid=0)
Apr 16 22:45:40 daka sddm-helper[1327]: pam_kwallet5(sddm-greeter:session): pam_kwallet5: pam_sm_open_session
Apr 16 22:45:40 daka sddm-helper[1327]: pam_kwallet5(sddm-greeter:session): pam_kwallet5: open_session called without kwallet5_key
Apr 16 22:45:40 daka sddm-helper[1327]: Writing cookie to "/tmp/xauth_IdbLVs"
Apr 16 22:45:40 daka sddm-helper[1327]: Starting X11 session: "" "/usr/bin/sddm-greeter-qt6 --socket /tmp/sddm-:0-frwbow --theme /usr/share/sddm/themes/breeze-openSUSE"
Apr 16 22:45:40 daka sddm[1254]: Greeter session started successfully
Apr 16 22:45:41 daka sddm[1254]: Message received from greeter: Connect
**Apr 16 22:45:44 daka sddm[1254]: Auth: sddm-helper exited with 11**
**Apr 16 22:45:44 daka sddm[1254]: Greeter stopped. SDDM::Auth::HelperExitStatus(11)**
Information from systemd journal follows soon…
After the update, the systemd journal of the next boot has a line kernel: sddm-greet:gl0[1473]: segfault [...] in radeonsi_dri.so [...] followed by a core dump.
I guess it’s no use posting all of that here. But of course I’m happy to support anyone who can make more sense of that core dump than I do. 
“radeonsi_dri.so” is located in →
/usr/lib64/dri/radeonsi_dri.so
/usr/lib/dri/radeonsi_dri.so
At least on this Leap 15.5 system –
> rpm --query --whatprovides /usr/lib64/dri/radeonsi_dri.so
Mesa-dri-22.3.5-150500.75.2.x86_64
> rpm --query --whatprovides /usr/lib/dri/radeonsi_dri.so
Mesa-dri-32bit-22.3.5-150500.75.2.x86_64
>
Therefore, please check the validity of the “Mesa-dri” packages installed on your system.
It’s a little bit strange that, AMD graphics devices are causing a Mesa issue –
- Can you please indicate which AMD hardware is installed on your system?
If, you have an AMD GPU and/or CPU, are the following packages installed on your system?
- “kernel-firmware-amdgpu”
- “libdrm_amdgpu1” + “libdrm_amdgpu1-32bit”
- “ucode-amd”
Hardware:
Intel i3-4130 CPU
Asus H87-Pro Mainboard with Intel H87 chipset
Radeon HD 7750 GPU
OS: Tumbleweed 20240416
> rpm --query --whatprovides /usr/lib64/dri/radeonsi_dri.so
Mesa-dri-23.3.6-369.1.x86_64
How does one check the “validity” of packages?
Packages kernel-firmware-amdgpu and libdrm_amdgpu1 are installed, the others not:
> sudo zypper se --details kernel-firmware-amdgpu libdrm_amdgpu1 libdrm_amdgpu-32bit ucode-amd
S | Name | Type | Version | Arch | Repository
---+------------------------+-------+--------------+--------+-----------------------
i+ | kernel-firmware-amdgpu | Paket | 20240322-2.1 | noarch | Haupt-Repository (OSS)
i+ | libdrm_amdgpu1 | Paket | 2.4.120-1.3 | x86_64 | Haupt-Repository (OSS)
| libdrm_amdgpu1-32bit | Paket | 2.4.120-1.3 | x86_64 | Haupt-Repository (OSS)
| ucode-amd | Paket | 20240322-2.1 | noarch | Haupt-Repository (OSS)
@dkage Hi you have a Southern Island card (Cape Verde) which is the same as the Oland in this thread https://forums.opensuse.org/t/after-tw-update-i-cant-enter-anything-at-login-screen/173701/16 add kernel boot options etc and see how it goes.