SUMMARY After configuring session-restore on login, then saving the session, many items are missing after starting a new session. STEPS TO REPRODUCE 1. Enable "Manually saved session" 2. Set up some apps including Firefox, Konsole, Dolphin 3. Save the session using the Leave button OBSERVED RESULT On logging in again, neither Dolphin nor Konsole windows are restored. Firefox is restored. EXPECTED RESULT All saved windows should be restored. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 34 (available in About System) KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION
Already noted on https://community.kde.org/Plasma/Wayland_Showstoppers. We can use this as the bug report to track it.
*** Bug 442192 has been marked as a duplicate of this bug. ***
*** Bug 442283 has been marked as a duplicate of this bug. ***
@Nate: is this going to be taken up any time soon? This is one of the biggest roadblocks to adopting plasma wayland for me. For example, its painful to rearrange firefox windows into different desktops after I start it. I have gone back to X11 solely because of this.
I don't know, sorry.
*** Bug 453849 has been marked as a duplicate of this bug. ***
unfortuantely still an issue on plasma 5.24.90
*** Bug 455105 has been marked as a duplicate of this bug. ***
*** Bug 455900 has been marked as a duplicate of this bug. ***
So something like this will eventually be able to help it? https://www.youtube.com/watch?v=fRdnRwPBFBk
Will this bug get fixed soon? It is the sole reason why I'm not on Wayland. Can someone let us know what time frame can be realistic expected for this to be sorted out? Thank you.
It's listed on https://community.kde.org/Plasma/Wayland_Showstoppers, so it will eventually get fixed/implemented.
This annoying issue is still present on Fedora 36 using KDE 5.97.0 with Wayland. Is somebody looking into this, or is there a timeline for when this will be fixed?
To be honest it stops me before using/testing Plasma session with Wayland. IMO. This is one from the biggest advantage in KDE (recently even Windows 10 got it, at least for me. I don't understand why this is so low on the priority list (issue reported over 1 year ago).
Would you like to contribute technical work towards fixing this issue? That's what there's not enough of right now.
(In reply to Nate Graham from comment #15) > Would you like to contribute technical work towards fixing this issue? > That's what there's not enough of right now. I'm not sure if this is the question to me, because you didn't quote my statement only answered just after me. Assuming you asked me, I can reply only that maybe I would like, but technically this would be not feasible due to few free time (private reasons). Only from time to time I can report some issue and this is enough what I can do, sorry. Recently I use Neon unstable, so I think, I'm up to date with what's new in Plasma so in this way I test. Sorry for my previous complains.
Hopefully this has contributed to answering your question: everyone with the technical ability to work on this issue is busy with other things that they have prioritized higher. :)
(In reply to Nate Graham from comment #17) > Hopefully this has contributed to answering your question: everyone with the > technical ability to work on this issue is busy with other things that they > have prioritized higher. :) NOP for me. I work with X11, because here more things works better, or just work. Only, IMHO, KDE/Plasma a bit suffer because has less testers, because of this. And please don't understand me wrong, I would not like to set development priorities of KDE/Plasma.
In general, Plasma has enough testers and QA people. What it lacks is enough developers to fix all the issues those people find.
(In reply to Nate Graham from comment #19) > In general, Plasma has enough testers and QA people. What it lacks is enough > developers to fix all the issues those people find. Or the devs you already have are interested only in next shiny thing than to fix bugs in their code...:-) Sure, we can't force devs to stick around forever and fix bugs in their code but sometimes, its good to stop new development and just fix the bugs. You will have more adoption and participation, and that can potentially get you more devs.
(In reply to devsk from comment #20) > Or the devs you already have are interested only in next shiny thing than to > fix bugs in their code...:-) Sure, we can't force devs to stick around > forever and fix bugs in their code but sometimes, its good to stop new > development and just fix the bugs. You will have more adoption and > participation, and that can potentially get you more devs. As a user, I also wish session restore to worked on Wayland, but inflammatory comments won't help expedite it. I would like to know what's making this difficult. X11 had a session management protocol; does Wayland define something equivalent? If not, could Plasma do something limited to KDE apps? Where is the current session save/restore code? Any documentation we could link in this bug to support someone who wants to give a shot at it?
(In reply to Bernie Innocenti from comment #21) > (In reply to devsk from comment #20) > > Or the devs you already have are interested only in next shiny thing than to > > fix bugs in their code...:-) Sure, we can't force devs to stick around > > forever and fix bugs in their code but sometimes, its good to stop new > > development and just fix the bugs. You will have more adoption and > > participation, and that can potentially get you more devs. > > As a user, I also wish session restore to worked on Wayland, but > inflammatory comments won't help expedite it. I swear inflammation was not the intention. But truth can be hard sometimes and it lands wrongly in written communications. My apologies if it sounded like that. It is true that devs like to move onto newer things. I see it everyday at work. And good teams and leaders have to bring them back to the table. We have burnt sprints doing just bug fixes solely because of this. And it works! The overall quality of the code improves and customers are happier and they spread the good word!
For me, with x11 applications running under x11 ad Wayland, it just seems to be a app startup mechanism. xcalc for example doesn't remain state after logging out. The observed result has been found because Firefox has a option to reopen the pages that were closed during the shutdown of Firefox. Therefore i think changing restore to reopen would be more accurate and a more concrete path to a solution. after the user ends session by logging out, rebooting, etc. Before closing the applications, the paths of the open applications should be saved to a (session) file from where these can be opened. I would be interested to know how the x11 application reopen is done in Wayland as hopefully some of the solution can be reused or be expanded on to include Wayland applications. Im not completely confident in my c++ skills yet as im studying it, so maybe some would like to help me tackle by introducing me to the project structure and the working parts making up KDE.
(In reply to devsk from comment #22) > (In reply to Bernie Innocenti from comment #21) > > (In reply to devsk from comment #20) > > > Or the devs you already have are interested only in next shiny thing than to > > > fix bugs in their code...:-) Sure, we can't force devs to stick around > > > forever and fix bugs in their code but sometimes, its good to stop new > > > development and just fix the bugs. You will have more adoption and > > > participation, and that can potentially get you more devs. > > > > As a user, I also wish session restore to worked on Wayland, but > > inflammatory comments won't help expedite it. > > I swear inflammation was not the intention. But truth can be hard sometimes > and it lands wrongly in written communications. My apologies if it sounded > like that. Your comment was not inflammatory at all. It was your opinion expressed in a friendly and factual manner. IMO. But it seems to me that esp. in the FOSS community quite a few people simply can't stand critigue, however constructive or well intentioned or politely formulated it may be. They seem to experience critigue as an aggression and not as a chance for improvement. And I consider that a major weakness and an obstacle to success.
This "bug" or missing key feature, as I see it, is obviously really bad and at this point of time quite shocking. Two days ago I was about switching to Plasma-Wayland because I had such a favorable impression of it. Until I discovered this thing. I don't know whether this situation is due to a lack of provision in the Wayland-design or an inability of developers to focus on what really matters. But if the Plasma devs could solve this on their own, I'd strongly suggest they drop any other Wayland related work *NOW* and start working like hell on resolving this issue. Because this is so detrimental to Plasma's and KDE's reputation that they may not recover from it. IMO.