Summary: | System Settings > Session > Desktop Session > Session Restore (Does not restore last session) | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | darrenllr |
Component: | Session Management | Assignee: | Plasma Bugs List <plasma-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | bdk, eugene.savitsky, kde, kdedev, natalie_clarius, peter.snauwaert, pm |
Priority: | NOR | ||
Version First Reported In: | 6.0.2 | ||
Target Milestone: | 1.0 | ||
Platform: | Neon | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
darrenllr
2024-03-22 06:12:28 UTC
At the time I might be using e.g. Obsidian MD Zotero Brave browser (multiple windows / tabs) Settings I see similar problems on openSUSE Tumbleweed with Plasma 6.0.3. I think it's the "save" part that is broken: when I first started after upgrading from Plasma 5 3 of my activities 4 were active, and most of the programs were started (Chromium has never been restarted, so that was no surprise), and IIRC even some of the activity/virtual desktop settings were right. I would count that as a successful update. After logging out and in again basically nothing was started. When I started the remaining activity (it was intentionally disabled in back in Plasma 5 for unrelated reasons) things in that activity were also more or less correctly set up. But after the next restart things are gone as well. On Wayland it was broken. In KDE 6.1 it is sort of restored. Fedora 41. Problem persists. Applications restored but to wrong desktop. maybe related to bug 496063 I have been experiencing this on Opensuse Tumbleweed also for quite some time now. Plasma version is 6.2.5. (It becomes quite annoying after some time when you have a sort of arrangement to help your work. Would really want to see this fixed.) Updating metadata(In reply to Brian Kaye from comment #5) > Applications restored but to wrong desktop. This is a different issue. It's covered by bug 436318 This seems like the same behavior as in bug 491130 which was supposed to be fixed in 6.2.5 Also seems related to bug 488520 which is fixed for some people but not others. I'm going to make this a duplicate of that report. Please follow that report for updates. Thanks! *** This bug has been marked as a duplicate of bug 488520 *** |