I moved to Fedora KDE, added multimedia support and a few apps, and updated the system in stages. After a game ran normally, System Settings stopped opening and panel edits froze. A reboot left me with a black screen, though I could still reach a text console. Reinstalling KDE-related packages got the desktop working again but reset my settings. The log showed KWin failing with an undefined symbol in a KDE library. What would you check to avoid this happening again?
Any idea what broke KDE after I switched from Bazzite to Fedora?
Asked by
!Quoin+4
Answers
The undefined-symbol error points more toward mismatched KDE components than a bootloader problem. Since updates and extra packages were installed in stages, check whether the system had a partially updated set of KDE packages or packages from different repositories.
Next time, finish a complete system update in one go, let it complete, then reboot before adding more software. If the issue returns, inspect the package transaction history and the detailed KWin service log. Those may show which packages changed just before the failure.
Reply to this answer
That error is the useful clue. KWin tried to load a KDE library but could not find a symbol it expected, which can happen when related packages are out of sync. It does not identify the exact cause by itself, so I would not assume a particular app or driver caused it.
For diagnosis, collect the full service log and package versions for KWin and the library named in the error. Also check which repositories supplied them. A shortened or garbled log line makes it hard to tell whether this was a failed upgrade, a packaging mismatch, or something else.
Reply to this answer
Good call using the text console. If the graphical session fails again, check the display-manager and KWin service status there, and save the logs before reinstalling anything. Reinstalling can restore a working desktop, but it may also erase clues about what went wrong.
For your KDE layout and shortcuts, use the desktop’s export or backup options where available, and keep a copy of relevant configuration files separately. A backup is safer than relying on a repair to preserve settings.
Reply to this answer
Try to keep the software setup boring: update the base system fully, reboot, then install extra packages from the intended repositories. Avoid interrupting package operations or mixing package sources unless you know why a package needs to come from somewhere else.
If the same symptom happens again, note the exact update and install commands and capture the complete logs. Without those details, it is possible to narrow down the type of failure, but not name the package that caused it.
Reply to this answer
Add your answer
Answers are reviewed before publication.
42!Tapered:
I did update between installs, rather than doing the whole setup first and updating once. I no longer have the affected install to check its package history.