Hi.
Brad Rogers - 23.12.24, 09:29:46 MEZ:
Looks like it started working after full session restart, so not sure
what exactly was wrong.
I've found that things can sometimes behave weirdly when upgrading from plasma 5-6 or Qt 5-6 (1) when only partial upgrades happen. As you've
found, a session restart will often sort things out.
(1) It's not just Plasma/Qt it happens with all sorts of things.
Actually upstream does not recommend to upgrade within a Plasma session at
all as far as I am aware. That is why they have a setting in "Software
updates" or "Updating Software" or something like that in Systemsettings
(in German here currently, so I do not know the exact English wording). In there you can set that updates triggered by Discover will be applied after system restart like in Windows :).
Reason for that is: Files that running processes of a Plasma session can
refer to are upgraded, replaced, renamed, deleted. For files they already loaded it should be no issue, but should a process need to load in some
files and there are not the right version or have been renamed or whatever
then you may get all kinds of funny effects. (On Windows there is an
additional reason for that: AFAIK they do not allow to replace opened
files. The Linux kernel has no issue with that.)
I still ignore that recommendation and upgrade with apt within a session. Yesterday I did it even with a Plasma 5 => 6 upgrade on a pure unstable
machine that has not been updated in a while. But if its something bigger
where I think it could affect the session, then I restart the session afterwards. Also I still do not use Discover cause whenever I tried it it
had some crazy bugs. Also it is usually just slower than just using apt on command line.
Best,
--
Martin - please no carbon copy to me
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)