https://bugs.kde.org/show_bug.cgi?id=524375
Nicolas Fella <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Latest Commit| |https://invent.kde.org/plas | |ma/plasma-workspace/-/commi | |t/fa4eb6a002e1f5f72f634aa10 | |6bf295adb18201f Resolution|--- |FIXED Status|ASSIGNED |RESOLVED --- Comment #2 from Nicolas Fella <[email protected]> --- Git commit fa4eb6a002e1f5f72f634aa106bf295adb18201f by Nicolas Fella. Committed on 22/08/2026 at 16:11. Pushed by nicolasfella into branch 'master'. Save/restore windows consistently by storageId The documentation for the AppId role contradicts itself. It says it's the service's storageId, but without the .desktop extension, which doesn't make sense. 0ea430ac969eb9a8e17c45e0645311e35eb2e8f1 fixed it to actually be the appId. However plasma-fallback-session-save uses the AppId when saving. plasma-fallback-session-restore then uses KServie::serviceByMenuId() to restore it, which is wrong (but works okay most of the time). To address all of this consistently use the storageId, which is suitable for this kind of thing. M +2 -0 libtaskmanager/abstracttasksmodel.cpp M +2 -1 libtaskmanager/abstracttasksmodel.h M +6 -0 libtaskmanager/launchertasksmodel.cpp M +6 -0 libtaskmanager/waylandtasksmodel.cpp M +1 -1 startkde/session-restore/restore.cpp M +1 -1 startkde/session-restore/save.cpp https://invent.kde.org/plasma/plasma-workspace/-/commit/fa4eb6a002e1f5f72f634aa106bf295adb18201f -- You are receiving this mail because: You are watching all bug changes.
