All from 6.10.0 to 6.10.1. After 5 minutes of inactivity the following message showed after a screen lock started:
The screen locker is broken and unlocking is not possible anymore. In order to unlock switch to a virtual terminal (e.g. Ctrl+Alt+F1), log in and execute the command:
loginctl unlock-session
Then log out of the virtual session by pressing Ctrl+D, and switch back to the running session (Ctrl+Alt+F2).
Then the system hanged. Moving to different tty and executing command did nothing. When I went back to the first tty, it was still stuck. On reboot, plasma wouldnât start, but I was able to get to a different tty. I tried the following command to try to start plasma on tty2.
Got an error message about a missing symbol. Something like âQt6 crash: undefined symbol: version Qt_6_PRIVATE_APIâ There was more to the message but I canât find it anymore.
Downgrading aforementioned packages allowed the same command to load into a plasma-session from tty2 without a reboot. After that I was able to reboot to plasma normally but packages left unupgraded.
Same here, couldnât even start SDDM after rebootâŚInstalled downgrade and downgraded qt6-base to 6.10.0. So at least SDDM is running again.Further downgrades may be required as the Konsole (with fish) also doesnât start with similar symbol undefined errors.
So I gonna downgrade all of them but python-pyqt6 to 6.10.0* âŚ
Done. Konsole also working again.
Until further notice I wonât upgrade anything out of QT6.
Yeah right now there are plasma and kwin etc. along many QT6 upgrades.
Iâm cautious now and wait for further reports. Donât wanna downgrade a lot more packages if it doesnât work again.
Yeah may be broken by incomplete rolling release. Can happen. @cscs so you have no issues with SDDM startup or Konsole?
I just re-ranked my mirrors just in case and re-ran the update. No issues now. Probably didinât need to redo the mirrors but that has fixed the odd issue for me before. All packages were updated as normal.
Not likely, normally, packages follow a strict order, like package A needs package B, so install B first, then A, etc. In this case Pacman was aware of the the cycle, installed (correct) seq. of packages, and completed the update with no errors.
Itâs a known quirk in the Qt 6.10.x ecosystem. The ffmpeg plugin for Qt multimedia had a refactoring, and temporarily created this circular dependency. Itâs not a bug in Cachy, but a upstream Qt issue that the maintainers chose to accept (rather than split/patch the packages), at least, this is what I could find.
The actual issue was something else in that update, likely graphics driver incompatibility or a Wayland/SDDM rendering issue, not this dependency cycle.
Best to keep the updates at bay for a few days as a patch will follow.
That âdependency cycleâ really was simply one package being installed before the other though it expects the other way around. Both get installed. It is only a notice.
As per the thread issue - You just managed to hit a partial upgrade scenario.
As shown by myself and other commenters above .. an extra 30 minutes was apparently the difference here. You upgraded parts of QT but not the parts of Plasma (etc) that rely on it.
Try again with all of them and I am 99.99% it will be fine.
This is my current pending updates, and before checking to take this screenshot, the plama-integration & plasma-workspace were not present. Could this have happened to many of us ? That the plasma updates were late compared to the QT6 ones ?
