Bug 1221524 - sddm failure after latest TW update re: theme / shared libs
Summary: sddm failure after latest TW update re: theme / shared libs
Status: RESOLVED DUPLICATE of bug 1221405
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: KDE Workspace (Plasma) (show other bugs)
Version: Current
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: E-Mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-03-17 22:57 UTC by Toby Breckon
Modified: 2024-03-18 08:09 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
bad phone screenshot of error at sddm prompt (2.95 MB, image/jpeg)
2024-03-17 22:57 UTC, Toby Breckon 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Toby Breckon 2024-03-17 22:57:48 UTC 
Created attachment 873584 [details]
bad phone screenshot of error at sddm prompt

With the latest update, I get a sddm failure and the following error message:

The current theme cannot be loaded due to the errors below, please select another theme.

file://usr/share/sddm/themes/breeze-openSUSE/Main.qml:111.9 Type WallpaperFader unavailable
file://usr/share/sddm/themes/breeze-openSUSE/components/WallpaperFader.qml:13.1 plugin cannot be loaded for module "org.kde.plasma.sessions". Cannot load library /usr/lib64/qt5qml/org/kde/plasma/sessions/libsessionsprivateplugin.so (libkworkspace5.so.5. cannot open shared object file: no such file or directory)

Login screen unable, login not possible with correct credentials.

[ Retyped from phone screenshot - attached ]

Temp solution = snapper rollback

T.
Comment 1 Fabian Vogt 2024-03-18 08:09:24 UTC 
Due to a bug, the upgrade is killed halfway. You need to rollback to the previous snapshot and either upgrade from a tty or wait until bug 1221405 is fixed.

*** This bug has been marked as a duplicate of bug 1221405 ***