Bug 482536 - After updating to latest KDE packages via Discover on Mar 5th, login on splash screen must be done with on-screen keyboard, and a "missing resources" error appears every time I use the window switcher (ctrl + tab)
Summary: After updating to latest KDE packages via Discover on Mar 5th, login on splas...
Status: RESOLVED UPSTREAM
Alias: None
Product: neon
Classification: KDE Neon
Component: Packages User Edition (other bugs)
Version First Reported In: unspecified
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Neon Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-03-06 12:14 UTC by Andy
Modified: 2024-03-19 11:44 UTC (History)
5 users (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Andy 2024-03-06 12:14:15 UTC 
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. Boot the computer
2. Decrypt drive
3. KDE desktop login must be done via on-screen keyboard

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2024-03-06 19:25:32 UTC 
User edition, right? Can you attach a screenshot of the issues?
Comment 2 Andy 2024-03-07 12:30:11 UTC 
Yes, user edition. I've figured out what the issue was, though, I believe - the update to KDE 6 seems to have caused issues with desktop elements that were utilising custom themed versions. In my case, I had the Nord theme Login screen, and the MediumDarkRounded custom window switcher. When I went into settings and selected alternatives to these, correct function was restored.

Probably good for the team to be aware that KDE 6 may mess up people using custom-themed components at first, but this seems more like an upgrade hiccup rather than a true bug, so I'm going to mark this as "resolved." Feel free to change the status to whatever you think appropriate.
Comment 3 Carlos De Maine 2024-03-19 11:44:38 UTC 
3rd party qt5 sddm themes need to be updated by the upstream authors (or someone else) to be qt6 sddm compatible