https://bugs.kde.org/show_bug.cgi?id=502502
Nate Graham <n...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REPORTED |RESOLVED
Resolution|--- |DOWNSTREAM
--- Comment #13 from Nate Graham <n...@kde.org> ---
OK, then I'm a little bit less sure than I'd like to be, but I'm still fairly
sure of what happened: you've been a victim of in-place upgrades.
Basically right after you updated your system, for anything currently running
(like Plasma), the files on disk no longer matched the versions of those files
in memory. If anything running needed to reach out to load something from the
disk that wasn't already in memory, it would get a version that wasn't
*necessarily* compatible with other files in memory.
When this happens, it manifests as extremely strange transient issues that go
away after rebooting — exactly as happened here.
If there was a Plasma upgrade, then probably what happened was that the upgrade
provided new versions of some of the notification files; there were several
changes in Plasma 6.3 point releases. If, as mentioned earlier, you don't
regularly see notifications with buttons, then it's quite possible that the
file with the buttons in it never got loaded into memory. So then when Plasma
tried to show you one such notification, it loaded the file, but got the one
that was newly installed by the system update, and it was subtly incompatible
with the in-memory files and broke, producing this issue.
If there was no Plasma upgrade then probably the above happened with a
different file, something deeper in the system that caused Plasma's session
restore system to believe it didn't need to ask the notification for any
buttons.
Preventing horrible issues like this is one of the reasons why KDE recommends
offline updates. I'm not sure whether Manjaro or Arch support offline updates
now, but if they do, I would strongly recommend using them. If not, and
switching distros isn't an option, it's always a good idea to reboot
immediately after an upgrade. In this case, restarting plasmashell first is
probably a good idea too, to prevent being bitten by this issue when you do try
to reboot!
--
You are receiving this mail because:
You are watching all bug changes.
