Bug 486012 - SDDM Themes brake my login screen
Summary: SDDM Themes brake my login screen
Status: RESOLVED DOWNSTREAM
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_sddm (other bugs)
Version First Reported In: 6.0.4
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-04-23 11:00 UTC by Mike
Modified: 2025-08-01 19:14 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mike 2024-04-23 11:00:28 UTC
Every time I use any SDDM theme I get a black screen with a cursor and can't login or anything else. I then have to boot into a live usb like fedora or POP go into the /user/share/sddm/themes and delete whatever theme I tried to use so that it goes back to the default theme. this happens regardless of the theme I use. The themes that come with the KDE plasma 6 install. it happens on my laptop and my desktop computers both running Arch. 


STEPS TO REPRODUCE
1. add any theme
2. 
3. 

OBSERVED RESULT
everything works fine until the next boot and I just get a black screen with a _ in the top right corner and the cursor and it just stays stuck like that.

I am using an HP Pavilion Desktop TP01-2xxx,  
Kernel: 6.8.7-arch1-1 
 DE: Plasma 6.0.4 
 Theme: Breeze-Dark [GTK2], Breeze [GTK3] 
 Icons: Gruvbox [GTK2/3] 
CPU: AMD Ryzen 5 5600G with Radeon Graphics (12) @ 3.900GHz 
GPU: AMD ATI Radeon Vega Series / Radeon Vega Mobile Series 
Memory: 4859MiB / 11292MiB 
 
The laptop is a Lenovo Thinkpad T560 with an NVIDIA GPU and the hardened kernel everything else is the same
Comment 1 Rustring 2025-03-02 08:24:51 UTC
Try to install the plasma-framework5 package
Comment 2 TraceyC 2025-08-01 19:14:16 UTC
Thanks for the bug report. I was not able to reproduce this on 6.3.4 or git-master. 

If this is still happening on your system with Plasma 6.3.4, your system may be missing a dependency, as mentioned in the last reply. Your best bet is to reach out to Arch user support.

Thanks!