Summary: | Save session doesn't work under Wayland | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | Patrick O'Callaghan <pocallaghan> |
Component: | Session Management | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | agurenko, alex765, andihartmann, anssi.hannula, anton.schenker, auxsvr, bednarczyk.pawel, bernie, bruno, butirsky, cdennett, cengique, chris, christian.rohmann, coque.couto, cribari, cruzki123, dennis, desw, dev+kde, dkxls23, drew.m.fisher, edtoml, endymion+kde, equeim, etaash.mathamsetty, eugene.shalygin+bugzilla.kde, feus73, freisim93, funtoos, hoehnp, hoperidesalone, imaginator, JanNowak94, jbuchert+kdebugs, jhs, jlp, jmtornetta, johannes.hirte, john.ettedgui, julien.dlq, kairo, kde, kishore96, L.Bonnaud, linux, mail, majzoube, matt, mauromol, miranda, mmtsales, msdobrescu, mwc85.23yp, nate, nerumo, nico.kruber, niklas, nkwkelvin, nl6720, nortexoid, ol+kde, omosnacek, pfeiffer, piotr.mierzwinski, plasma-bugs, postix, rdieter, roman, s2, sam, sandysareon, shtetldik, silver.salonen, smit17xp, tbondvagyok, ticonzero2010, tombrown9501, tuppa+kde, victualsquid, wdmlist, whyhow3.141, xqgrhiovxf6bw12h |
Priority: | HI | Keywords: | wayland |
Version: | 5.24.4 | ||
Target Milestone: | 1.0 | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
URL: | https://invent.kde.org/plasma/kwin/-/issues/113#note_500909 | ||
See Also: | https://bugs.kde.org/show_bug.cgi?id=476831 | ||
Latest Commit: | https://invent.kde.org/plasma/plasma-workspace/-/commit/804976c5ecec1fbf5f6e7e09970a8269bdf748d2 | Version Fixed In: | 6.1 |
Attachments: |
attachment-25640-0.html
attachment-30227-0.html attachment-30617-0.html attachment-13297-0.html attachment-19101-0.html attachment-23823-0.html attachment-2084366-0.html |
Description
Patrick O'Callaghan
2021-04-28 16:11:50 UTC
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. *** Bug 460567 has been marked as a duplicate of this bug. *** Same problem here with leap 15.4. Would be really nice to get it fixed ... . Hi all, same problem here does anyone know if the bug has been fixed? thanks Andrea (In reply to ticonzero from comment #28) > Hi all, > > same problem here does anyone know if the bug has been fixed? > If it had been fixed, the status would have changed. With the "Importance" downgraded to "normal", I don't expect it to be fixed before Plasma 6. ok, thanks for the clarification, I will be moving back to Xubuntu 20.04 LTS, since I make big use of this feature (In reply to ticonzero from comment #30) > ok, thanks for the clarification, I will be moving back to Xubuntu 20.04 > LTS, since I make big use of this feature I'd say that 99 % of the users make use of this feature. The rest either don't know that it exists or never log out because they are incurably addicted to Plasma-Wayland. ;) I don't think there are so many Wayland users out there because Wayland has so many restrictions and bugs so far (and I don't see any solution). Created attachment 154513 [details] attachment-25640-0.html Andreas, I would respectfully disagree. I switched to wayland once multi monitor support started working and have not looked back. Here, at least, the color is more vivid using wayland (eg X looks washed out). Aside from a few irritating bugs like this one, it works well. On Fri, Dec 9, 2022 at 12:56 PM Andreas Hartmann <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=436318 > > --- Comment #32 from Andreas Hartmann <andihartmann@freenet.de> --- > I don't think there are so many Wayland users out there because Wayland > has so > many restrictions and bugs so far (and I don't see any solution). > > -- > You are receiving this mail because: > You are on the CC list for the bug. (In reply to Andreas Hartmann from comment #32) > I don't think there are so many Wayland users out there because Wayland has > so many restrictions and bugs so far (and I don't see any solution). Just as a reference point, Wayland session usage is shown gradually growing here: https://www.gamingonlinux.com/index.php?module=statistics&view=trends#SessionType-top Created attachment 154515 [details] attachment-30227-0.html Well I do like it, in fact I'm sticking with it, but I do miss being able to restore the old session, for me it means not having to reopen dozen of pdfs in different okular instances on different desktops On Sun, 11 Dec 2022, 20:54 Ed Tomlinson, <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=436318 > > --- Comment #33 from Ed Tomlinson <edtoml@gmail.com> --- > Andreas, I would respectfully disagree. I switched to wayland once multi > monitor support started working and have not looked back. Here, at least, > the color is more vivid using wayland (eg X looks washed out). Aside from > a few irritating bugs like this one, it works well. > > On Fri, Dec 9, 2022 at 12:56 PM Andreas Hartmann <bugzilla_noreply@kde.org > > > wrote: > > > https://bugs.kde.org/show_bug.cgi?id=436318 > > > > --- Comment #32 from Andreas Hartmann <andihartmann@freenet.de> --- > > I don't think there are so many Wayland users out there because Wayland > > has so > > many restrictions and bugs so far (and I don't see any solution). > > > > -- > > You are receiving this mail because: > > You are on the CC list for the bug. > > -- > You are receiving this mail because: > You are on the CC list for the bug. Created attachment 154516 [details] attachment-30617-0.html You were not replying to me I guess ... On Sun, 11 Dec 2022, 21:19 ti conzero, <ticonzero2010@gmail.com> wrote: > Well I do like it, in fact I'm sticking with it, but I do miss being able > to restore the old session, for me it means not having to reopen dozen of > pdfs in different okular instances on different desktops > > On Sun, 11 Dec 2022, 20:54 Ed Tomlinson, <bugzilla_noreply@kde.org> wrote: > >> https://bugs.kde.org/show_bug.cgi?id=436318 >> >> --- Comment #33 from Ed Tomlinson <edtoml@gmail.com> --- >> Andreas, I would respectfully disagree. I switched to wayland once multi >> monitor support started working and have not looked back. Here, at least, >> the color is more vivid using wayland (eg X looks washed out). Aside from >> a few irritating bugs like this one, it works well. >> >> On Fri, Dec 9, 2022 at 12:56 PM Andreas Hartmann < >> bugzilla_noreply@kde.org> >> wrote: >> >> > https://bugs.kde.org/show_bug.cgi?id=436318 >> > >> > --- Comment #32 from Andreas Hartmann <andihartmann@freenet.de> --- >> > I don't think there are so many Wayland users out there because Wayland >> > has so >> > many restrictions and bugs so far (and I don't see any solution). >> > >> > -- >> > You are receiving this mail because: >> > You are on the CC list for the bug. >> >> -- >> You are receiving this mail because: >> You are on the CC list for the bug. > > (In reply to ticonzero from comment #35) > Well I do like it, in fact I'm sticking with it, but I do miss being able > to restore the old session, for me it means not having to reopen dozen of > pdfs in different okular instances on different desktops Same here. This bug is the only reason why I am not running Wayland. I usually have about a dozen PDF (okular) and over twenty text (kate) files open. It is too much work to open each of these files again every time I restart the computer. (In reply to Francisco Cribari from comment #37) > It is too much work to open each of these files again every time I > restart the computer. Ever heard about sleep and hibernation? ;-) (In reply to Mauro Molinari from comment #38) > Ever heard about sleep and hibernation? ;-) Sure. I use them daily. I'm on Arch Linux which is not shy in updates. Several updates (kernel (zen), etc.) require a reboot. (In reply to Francisco Cribari from comment #37) > (In reply to ticonzero from comment #35) > > > Well I do like it, in fact I'm sticking with it, but I do miss being able > > to restore the old session, for me it means not having to reopen dozen of > > pdfs in different okular instances on different desktops > > Same here. This bug is the only reason why I am not running Wayland. I > usually have about a dozen PDF (okular) and over twenty text (kate) files > open. It is too much work to open each of these files again every time I > restart the computer. If your windows don't change too much you can find a workaround on my dup: https://bugs.kde.org/show_bug.cgi?id=455900 Created attachment 154521 [details] attachment-13297-0.html It wouldn't work for me, I need to switch between different OSs and need to restart On Sun, 11 Dec 2022, 22:21 Mauro Molinari, <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=436318 > > --- Comment #38 from Mauro Molinari <mauromol@tiscali.it> --- > (In reply to Francisco Cribari from comment #37) > > It is too much work to open each of these files again every time I > > restart the computer. > > Ever heard about sleep and hibernation? ;-) > > -- > You are receiving this mail because: > You are on the CC list for the bug. (In reply to John E from comment #40) > (In reply to Francisco Cribari from comment #37) > > (In reply to ticonzero from comment #35) > > > > > Well I do like it, in fact I'm sticking with it, but I do miss being able > > > to restore the old session, for me it means not having to reopen dozen of > > > pdfs in different okular instances on different desktops > > > > Same here. This bug is the only reason why I am not running Wayland. I > > usually have about a dozen PDF (okular) and over twenty text (kate) files > > open. It is too much work to open each of these files again every time I > > restart the computer. > > If your windows don't change too much you can find a workaround on my dup: > https://bugs.kde.org/show_bug.cgi?id=455900 In my view, the most obvious and promising "workaround" for an ordinary user is to continue enjoying Plasma-X11 until all major issues in Plasma-Wayland are fixed and it's ready for productive use. ;) Created attachment 154527 [details] attachment-19101-0.html I installed kubuntu 22.04LTS, that came with Wayland, how can I get back to X11-Plasma, without returning to 18.04LTS ? On Mon, 12 Dec 2022, 10:10 , <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=436318 > > --- Comment #42 from imaginator@mailbox.org --- > (In reply to John E from comment #40) > > (In reply to Francisco Cribari from comment #37) > > > (In reply to ticonzero from comment #35) > > > > > > > Well I do like it, in fact I'm sticking with it, but I do miss being > able > > > > to restore the old session, for me it means not having to reopen > dozen of > > > > pdfs in different okular instances on different desktops > > > > > > Same here. This bug is the only reason why I am not running Wayland. I > > > usually have about a dozen PDF (okular) and over twenty text (kate) > files > > > open. It is too much work to open each of these files again every time > I > > > restart the computer. > > > > If your windows don't change too much you can find a workaround on my > dup: > > https://bugs.kde.org/show_bug.cgi?id=455900 > > In my view, the most obvious and promising "workaround" for an ordinary > user is > to continue enjoying Plasma-X11 until all major issues in Plasma-Wayland > are > fixed and it's ready for productive use. ;) > > -- > You are receiving this mail because: > You are on the CC list for the bug. (In reply to ticonzero from comment #43) > Created attachment 154527 [details] > attachment-19101-0.html > > I installed kubuntu 22.04LTS, that came with Wayland, how can I get back to > X11-Plasma, without returning to 18.04LTS ? I think that's a question for the kbuntu support forum / mailing list. Created attachment 154528 [details] attachment-23823-0.html Thanks! On Mon, 12 Dec 2022, 10:41 , <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=436318 > > --- Comment #44 from imaginator@mailbox.org --- > (In reply to ticonzero from comment #43) > > Created attachment 154527 [details] > > attachment-19101-0.html > > > > I installed kubuntu 22.04LTS, that came with Wayland, how can I get back > to > > X11-Plasma, without returning to 18.04LTS ? > I think that's a question for the kbuntu support forum / mailing list. > > -- > You are receiving this mail because: > You are on the CC list for the bug. (In reply to imaginator from comment #42) > (In reply to John E from comment #40) > > (In reply to Francisco Cribari from comment #37) > > > (In reply to ticonzero from comment #35) > > > > > > > Well I do like it, in fact I'm sticking with it, but I do miss being able > > > > to restore the old session, for me it means not having to reopen dozen of > > > > pdfs in different okular instances on different desktops > > > > > > Same here. This bug is the only reason why I am not running Wayland. I > > > usually have about a dozen PDF (okular) and over twenty text (kate) files > > > open. It is too much work to open each of these files again every time I > > > restart the computer. > > > > If your windows don't change too much you can find a workaround on my dup: > > https://bugs.kde.org/show_bug.cgi?id=455900 > > In my view, the most obvious and promising "workaround" for an ordinary user > is to continue enjoying Plasma-X11 until all major issues in Plasma-Wayland > are fixed and it's ready for productive use. ;) That's what I do as well, but it's not really what I would call a workaround. Exactly same problem can be seen even if KDE is run in wayland mode ... . Please ignore my last entry - wrong ticket :-). I've been "forced" to move now to wayland to get the per screen scale factor as it will never be implemented on X11. But loosing restore session is a pain. It seems we miss a global review on plasma development, with clear objectives for each release, to make all users (and developers) happy. (In reply to Bruno Friedmann from comment #49) > I've been "forced" to move now to wayland to get the per screen scale factor > as it will never be implemented on X11. But loosing restore session is a > pain. > It seems we miss a global review on plasma development, with clear > objectives for each release, to make all users (and developers) happy. I'm sure it holds the top position on their priority list for Plasma 6. But: who knows? ;) (In reply to Bernie Innocenti from comment #21) > I would like to know what's making this difficult. X11 had a session > management protocol; does Wayland define something equivalent? Let me loosely quote the wiki [1] > Session restoring does not include Wayland native windows (...). > Our sessions management recover engine is based on the X Session Management Protocol > and there is apparently currently no generic concept to do it on Wayland. > But on Qt it's plugin-able and GNOME has had their own implementation for some time. [2] Regarding opened discussions, there's an issue in the kwin repo, see "Goal 2: Session restore" [3] [1] https://community.kde.org/Plasma/Wayland_Showstoppers [2] https://wiki.gnome.org/Projects/SessionManagement/GnomeSession [3] https://invent.kde.org/plasma/kwin/-/issues/113#note_500909 See also the MR linked in the issue above: "Draft: wayland: Add support for xdg-session-v1" [1] [1] https://invent.kde.org/plasma/kwin/-/merge_requests/3024 Looks like some work was started 3 months ago and then, it stopped. I tried to use wayland again to see if the experience is any better and went back to x11 after an hour of frustration. I have 4 different desktops for various projects and just restoring all my konsole windows (about 9 of them) and their tabs, and placing them in their respective places on each boot is a big pain. Let's not even talk about putting other apps where I am used to seeing them. How does a serious dev use wayland at all? I am just curious. (In reply to devsk from comment #53) > Looks like some work was started 3 months ago and then, it stopped. > > I tried to use wayland again to see if the experience is any better and went > back to x11 after an hour of frustration. I have 4 different desktops for > various projects and just restoring all my konsole windows (about 9 of them) > and their tabs, and placing them in their respective places on each boot is > a big pain. Let's not even talk about putting other apps where I am used to > seeing them. > > How does a serious dev use wayland at all? I am just curious. My thoughts exactly. I've no doubt that serious devs *do* use Wayland, but I've no idea what their workflow is like. For me, session restore is an absolute requirement, so I keep feeling I must be missing something. (In reply to Patrick O'Callaghan from comment #54) > (In reply to devsk from comment #53) > > Looks like some work was started 3 months ago and then, it stopped. > > > > I tried to use wayland again to see if the experience is any better and went > > back to x11 after an hour of frustration. I have 4 different desktops for > > various projects and just restoring all my konsole windows (about 9 of them) > > and their tabs, and placing them in their respective places on each boot is > > a big pain. Let's not even talk about putting other apps where I am used to > > seeing them. > > > > How does a serious dev use wayland at all? I am just curious. > > My thoughts exactly. I've no doubt that serious devs *do* use Wayland, but > I've no idea what their workflow is like. For me, session restore is an > absolute requirement, so I keep feeling I must be missing something. Session restore is such a basic feature nowadays that it seems crazy to even have to waste one thought on it. It *has* to be there. Like wheels on a car. If not, something went seriously wrong somewhere. My way to deal with that - IMO disappointing - Wayland-show is that I simply don't care any more. To me it doesn't offer any benefit. And as long as there's a Plasma-X11 I'm happy. Are there any reasonable workarounds? Say a script that reads all window positions, sizes, etc., and saves the information, and then another script that can read this info and open and arrange the windows? For a while I used a script based on: https://github.com/zepalmer/script-vdr but it's for Python-2 and X11 and I haven't tried to bring it up to date. It's based around wmctrl, which AFAIK is not supported on Wayland, but there might be something useful there. Note that it's designed to save/restore the windows belonging to one process, e.g. your browser, not the full user session. Still an issue on Kubuntu 22.04, going to switch back to X until it is fixed. According to the plasma/wayland showstoppers page, session restore is a priority: https://community.kde.org/Plasma/Wayland_Showstoppers However, on the plasma 6 development page there is no mention of session restore: https://community.kde.org/Plasma/Plasma_6 Does anyone know if session restore is supposed to be in plasma 6? > Does anyone know if session restore is supposed to be in plasma 6? The plan is to solve all Wayland Showstoppers - including session restore - until Plasma 6.0 is released [1] [1] https://pointieststick.com/2023/09/06/september-plasma-6-update/#comment-37811 from my understanding the issue was downgraded to a non-showstopper anymore. At least this is shown now in the wiki page (https://community.kde.org/Plasma/Wayland_Showstoppers). I hope that Qt-pluginable option will still be provided on plasma 6. Is there any update about when it will be integrated? The plan right now is as follows: - For Plasma 6.0, implement a sort of fake session restore that on login, simply re-opens apps that were open on last logout, and count on apps that have state worth saving doing the saving themselves (and many apps already do; for example Firefox, Discord, Dolphin, Kate, Kile, Elisa...). - For a later Plasma 6 version, implement real session restore that's governed by a new Wayland protocol (one is in progress) and make KDE apps opt into it. - After that, keep the fake session restore and use it for apps that don't opt into the real session restore. This should ultimately produce a better UX than on X11, where many apps never opted into session restore and so it was semi-random as to which apps got launched on login. Will what is planned for KDE 6 take into account multiple monitors and multiple virtual desktops so that apps start in the desired monitor/virtual desktop? That is crucial! On 11/11/23 17:38, Charles Dennett wrote: > https://bugs.kde.org/show_bug.cgi?id=436318 > > --- Comment #63 from Charles Dennett <cdennett@gmail.com> --- > Will what is planned for KDE 6 take into account multiple monitors and multiple > virtual desktops so that apps start in the desired monitor/virtual desktop? > For the fake session restore, I can't make any promises about that. I've talked to the fellow doing the work and he wants to take those into consideration, but it becomes more technically challenging, so the first version might not. But I do expect those to *eventually* work in the fake session restore. (In reply to Charles Dennett from comment #63) > Will what is planned for KDE 6 take into account multiple monitors and > multiple virtual desktops so that apps start in the desired monitor/virtual > desktop? And please don't forget about activities! I'm tired of moving Firefox windows to different activities manually each time after login even on KDE 5 X11 session. (In reply to Nate Graham from comment #62) > - For Plasma 6.0, implement a sort of fake session restore that on login, > simply re-opens apps that were open on last logout, […] Wow, that sounds great! I mean, real session restore would be a fantastic feature to have, but the “fake” option is already a great improvement to what we have at the moment (i.e. nothing). I got already worried this was dropped entirely when I saw the change in the showstopper bug list. This is after all by far the biggest pain point I have with KDE Wayland. (In reply to Nate Graham from comment #62) > The plan right now is as follows: > - For Plasma 6.0, implement a sort of fake session restore that on login, > simply re-opens apps that were open on last logout, and count on apps that > have state worth saving doing the saving themselves (and many apps already > do; for example Firefox, Discord, Dolphin, Kate, Kile, Elisa...). Aside from the virtual desktop issue already mentioned by several people, it's worth noting that Dolphin does not currently restore its state correctly even under X11. Briefly, if you have more than one Dolphin window, some with the Terminal open and some not, the restored Dolphin will have all windows showing the Terminal in the same state, either open or closed, apparently at random. I reported this over a year ago (see https://bugs.kde.org/show_bug.cgi?id=455324) but never saw a reply. Indeed, Dolphin lost a lot of its session features, like restoring at the original position. For me, being an Nvidia user (didn't know the drawbacks at the time and Plasma looked to work good enough with x11 and Nvidia), has become more and more unlikely I would move to the next Plasma at all. This combination that makes any input unusable, the mouse pointer or the keyboard signals being sent to Plasma after 30 secs or so, but also lacking session, are unacceptable. I understand some features are ~ maybe ~ difficult to implement, but basic features like these are a must. I can't expect from a user to rather change a laptop just because he would use a DE, sorry. (In reply to Nate Graham from comment #62) > The plan right now is as follows: > - For Plasma 6.0, implement a sort of fake session restore that on login, > simply re-opens apps that were open on last logout, and count on apps that > have state worth saving doing the saving themselves (and many apps already > do; for example Firefox, Discord, Dolphin, Kate, Kile, Elisa...). > - For a later Plasma 6 version, implement real session restore that's > governed by a new Wayland protocol (one is in progress) and make KDE apps > opt into it. > - After that, keep the fake session restore and use it for apps that don't > opt into the real session restore. > > This should ultimately produce a better UX than on X11, where many apps > never opted into session restore and so it was semi-random as to which apps > got launched on login. Does Konsole save session (the windows and tabs and the current directory of each tab) by itself? My experience is that it does not, but given that things like Kate does, why can't Konsole, which is also a KDE app, do that? Am I missing something? > Does Konsole save session (the windows and tabs and the current directory of each tab) by itself? My experience is that it does not, but given that things like Kate does, why can't Konsole, which is also a KDE app, do that?
> Am I missing something?
Yes my experience proove it, I usually have 10 tabs opened in konsole, most of them are dedicated to a relative work, and as such the directory in which the last session was run, and is restored on the right desktop.
That IS the most reason I don't use (yet) Wayland.
(In reply to Bruno Friedmann from comment #71) > > Does Konsole save session (the windows and tabs and the current directory of each tab) by itself? My experience is that it does not, but given that things like Kate does, why can't Konsole, which is also a KDE app, do that? > > Am I missing something? > > Yes my experience proove it, I usually have 10 tabs opened in konsole, most > of them are dedicated to a relative work, and as such the directory in which > the last session was run, and is restored on the right desktop. > That IS the most reason I don't use (yet) Wayland. One workaround for Konsole exists on Stack-Exchange: https://unix.stackexchange.com/a/593779 It also works on Wayland. However, I believe this should be possible with built-in functionality. the same here. On 02/12/23 09:36, Bruno Friedmann wrote: > https://bugs.kde.org/show_bug.cgi?id=436318 > > --- Comment #71 from Bruno Friedmann <bruno@ioda-net.ch> --- >> Does Konsole save session (the windows and tabs and the current directory of each tab) by itself? My experience is that it does not, but given that things like Kate does, why can't Konsole, which is also a KDE app, do that? >> Am I missing something? > Yes my experience proove it, I usually have 10 tabs opened in konsole, most of > them are dedicated to a relative work, and as such the directory in which the > last session was run, and is restored on the right desktop. > That IS the most reason I don't use (yet) Wayland. > (In reply to Nate Graham from comment #62) > The plan right now is as follows: > - For Plasma 6.0, implement a sort of fake session restore that on login, > simply re-opens apps that were open on last logout, and count on apps that > have state worth saving doing the saving themselves (and many apps already > do; for example Firefox, Discord, Dolphin, Kate, Kile, Elisa...). > - For a later Plasma 6 version, implement real session restore that's > governed by a new Wayland protocol (one is in progress) and make KDE apps > opt into it. > - After that, keep the fake session restore and use it for apps that don't > opt into the real session restore. > > This should ultimately produce a better UX than on X11, where many apps > never opted into session restore and so it was semi-random as to which apps > got launched on login. Does that plan also apply to Plasma-6-X11 or will session restore there just keep working like in Plasma-5-X11? Thanks. I have made two scripts (heavily modified from scripts that I found somewhere else) to help session restore semi-automatically: https://github.com/Kelvin-Ng/konsole-session-restore: This script saves and reopens the Konsole windows with original tabs and directories. https://github.com/Kelvin-Ng/kde-window-status-restore: This script saves and restores the statuses of the windows, currently only activity and desktop. Note that it does not reopen the windows. The windows will have to be first reopened before running the restore script. Hope these scripts are helpful. (In reply to Nate Graham from comment #62) > The plan right now is as follows: > - For Plasma 6.0, implement a sort of fake session restore that on login, > simply re-opens apps that were open on last logout, and count on apps that > have state worth saving doing the saving themselves (and many apps already > do; for example Firefox, Discord, Dolphin, Kate, Kile, Elisa...). > - For a later Plasma 6 version, implement real session restore that's > governed by a new Wayland protocol (one is in progress) and make KDE apps > opt into it. > - After that, keep the fake session restore and use it for apps that don't > opt into the real session restore. > > This should ultimately produce a better UX than on X11, where many apps > never opted into session restore and so it was semi-random as to which apps > got launched on login. Alright, maybe my question was a bit too difficult to understand. So I rephrase it a bit: will session restore in Plasma-6-X11 work _right from the start_ as it does in Plasma-5-X11 or not? Some people don't give a damn about Wayland but do care about reliable and complete session restore. Created attachment 164287 [details] attachment-2084366-0.html Count me among those who need reliable session restore, I'm stuck with xubuntu 20.4 and will stay there until session restore will work properly On Tue, 19 Dec 2023, 10:07 , <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=436318 > > --- Comment #76 from imaginator@mailbox.org --- > (In reply to Nate Graham from comment #62) > > The plan right now is as follows: > > - For Plasma 6.0, implement a sort of fake session restore that on login, > > simply re-opens apps that were open on last logout, and count on apps > that > > have state worth saving doing the saving themselves (and many apps > already > > do; for example Firefox, Discord, Dolphin, Kate, Kile, Elisa...). > > - For a later Plasma 6 version, implement real session restore that's > > governed by a new Wayland protocol (one is in progress) and make KDE apps > > opt into it. > > - After that, keep the fake session restore and use it for apps that > don't > > opt into the real session restore. > > > > This should ultimately produce a better UX than on X11, where many apps > > never opted into session restore and so it was semi-random as to which > apps > > got launched on login. > > Alright, maybe my question was a bit too difficult to understand. So I > rephrase it a bit: will session restore in Plasma-6-X11 work _right from > the > start_ as it does in Plasma-5-X11 or not? Some people don't give a damn > about > Wayland but do care about reliable and complete session restore. > > -- > You are receiving this mail because: > You are on the CC list for the bug. (In reply to imaginator from comment #76) > Alright, maybe my question was a bit too difficult to understand. So I > rephrase it a bit: will session restore in Plasma-6-X11 work _right from the > start_ as it does in Plasma-5-X11 or not? Some people don't give a damn > about Wayland but do care about reliable and complete session restore. On X11? No changes have been made to session restore on X11 there so I would expect so. However I can't personally guarantee no regressions, as I'm not personally using X11 anymore and therefore not testing for regressions there. Someone else will need to step in for that. (In reply to Nate Graham from comment #78) > (In reply to imaginator from comment #76) > > Alright, maybe my question was a bit too difficult to understand. So I > > rephrase it a bit: will session restore in Plasma-6-X11 work _right from the > > start_ as it does in Plasma-5-X11 or not? Some people don't give a damn > > about Wayland but do care about reliable and complete session restore. > > On X11? No changes have been made to session restore on X11 there so I would > expect so. However I can't personally guarantee no regressions, as I'm not > personally using X11 anymore and therefore not testing for regressions > there. Someone else will need to step in for that. Thanks for clarifying this. *** Bug 476831 has been marked as a duplicate of this bug. *** *** Bug 481745 has been marked as a duplicate of this bug. *** Promoting this to be a 15-minute bug since it's Wayland-only and the Wayland-session is the default in Plasma 6 now. *** Bug 479886 has been marked as a duplicate of this bug. *** We've introduced a fallback. plasma-fallback-session-save which provides something. It's not perfect. It just sees which apps were open and then reopens them. The application has no mechanism to save any state. There's definitely room for improvement, but that involves upstream and updating all applications(!) which isn't worth us tracking in our bug tracker. Git commit 804976c5ecec1fbf5f6e7e09970a8269bdf748d2 by David Edmundson. Committed on 08/03/2024 at 09:17. Pushed by davidedmundson into branch 'master'. Migrate manual session saving to plasma-shutdown This allows the wayland fallback session saving to run too and removes more ksmserver logic from our library code. session-restore is patched to also run when the configuration file is set to restore the manually saved session. M +0 -3 libkworkspace/CMakeLists.txt M +2 -3 libkworkspace/sessionmanagement.cpp M +1 -0 startkde/plasma-shutdown/org.kde.Shutdown.xml M +24 -2 startkde/plasma-shutdown/shutdown.cpp M +1 -0 startkde/plasma-shutdown/shutdown.h M +1 -1 startkde/session-restore/restore.cpp https://invent.kde.org/plasma/plasma-workspace/-/commit/804976c5ecec1fbf5f6e7e09970a8269bdf748d2 > We've introduced a fallback. plasma-fallback-session-save which provides something. Thanks! > It's not perfect. It just sees which apps were open and then reopens them. The application has no mechanism to save any state. Let's take Konsole as an example. Does this mean that Konsole will not save its current directory? Correct. Because real session restore is not implemented on Wayland yet, at the moment this manual session restore hooks into the "real fake session restore" mechanism that will be used until we get real session restore. (In reply to Nate Graham from comment #87) > Correct. Because real session restore is not implemented on Wayland yet, at > the moment this manual session restore hooks into the "real fake session > restore" mechanism that will be used until we get real session restore. Any idea on when real session-restore might be coming? Once the proposed Wayland protocol gets approved and merged, support in Plasma will likely arrive quickly. I don't know if it's helpful to speculate as to when the protocol might get approved. It could be tomorrow and it could be in two years. Obviously we all would prefer the former over the latter. :) How about using this piece of software? https://github.com/Vladimir-csp/uwsm Session is restored in strange way. Firstly starts applications, so we have black screen and starting apps. and at end starts plasmashell. Second thing is that session in konsole is not restored, but in IceWm its working well. (In reply to Piotr Mierzwinski from comment #91) > Session is restored in strange way. Firstly starts applications, so we have > black screen and starting apps. and at end starts plasmashell. > Second thing is that session in konsole is not restored, but in IceWm its > working well. Applications also start in front of a black screen for me as well in 5.27 on X (and have in 5.24 as well). >How about using this piece of software?
That's not what's missing, that's a replacement for what we call "startkde"
|