[ksmserver] [Bug 436318] Save session doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=436318 --- Comment #20 from devsk --- (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. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 436318] Save session doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=436318 --- Comment #22 from devsk --- (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! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436318] Save session doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=436318 --- Comment #122 from devsk --- > Switched back to "On last logout" and it is still working. Very pleased! > Thanks to everyone who put in the hard work to make this happen for Plasma 6. What you are saying is that switching away and the switching back to this option made the session restore work properly for you with 6.1. Can you please confirm what all works? Does it put all your console windows with their tabs in their respective desktops? How about firefox windows? What else did you try to restore? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436318] Save session doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=436318 --- Comment #130 from devsk --- Is there more work planned for plasma 6.2 to address the issues with session restore (via another bug)? or do we need to reopen this bug and address the remaining issues via this bug? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436318] Save session doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=436318 --- Comment #99 from devsk --- This is marked RESOLVED as FIXED for a while now. Do people have experience with the new session restore in Plasma 6? How good is it working with X11 and wayland? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436318] Save session doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=436318 --- Comment #119 from devsk --- So, after reading the comments, it looks like it is still the "same old same old". Sticking with plasma 5 then! -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 436318] Save session doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=436318 devsk changed: What|Removed |Added CC||funt...@yahoo.com --- Comment #4 from devsk --- @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. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436318] Save session doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=436318 --- Comment #53 from devsk --- 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. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436318] Save session doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=436318 --- Comment #141 from devsk --- Gentoo sort of forced me to update to latest plasma by deprecating some of the packages because of dependency hell. And now, the X11 session restore is broken:-( -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 387202] Copy and Paste stop working after 47 days
https://bugs.kde.org/show_bug.cgi?id=387202 devsk changed: What|Removed |Added CC||funt...@yahoo.com --- Comment #4 from devsk --- This is a serious problem. I have VNC sessions that are never restarted unless security issues force a restart, and I used to be able to run them for months on end (one had an uptime of >300 days). This issue started happening recently (in last one year or may be since I moved to KF5 like 1.5 yrs ago), it wasn't the case earlier. How can we debug and make progress on it? -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 142847] ksysgaurd picker applet should display composite real values in the topbar
https://bugs.kde.org/show_bug.cgi?id=142847 --- Comment #2 from devsk --- Wow! 17.5 years! KDE, my love, we go a long way! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436318] Implement real session save/restore on Wayland
https://bugs.kde.org/show_bug.cgi?id=436318 --- Comment #184 from devsk --- While hunting for any recent updates, I found this. Looks like gnome-48 will contain some form of session restore: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3825 https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/7682 https://www.phoronix.com/news/Mutter-XDG-Session-Management I can't really find any recent updates for KDE for similar effort. Is this ever going to be worked on by KDE? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436318] Implement real session save/restore on Wayland
https://bugs.kde.org/show_bug.cgi?id=436318 --- Comment #186 from devsk --- > Is this ever going to be worked on by KDE? In my mind, there are two answers to this question, and both are correct answers: 1. We have no plan to get this working on KDE anytime soon 2. We have a plan and here is the schedule (gnome guys took this approach) I haven't seen 2) for KDE anywhere on the interwebs. Can we at least create a plan? Its fine if its done in 6 months from now or 1 year. But let's have a plan and work toward it. 1) is also fine but then, let's state that clearly so that we can stop coming back to this bug (its almost 4 years old now) every few months. To me, it almost feels like, because this bug is open, someone is working on it in the background when, in reality, no one is, and there is no way of knowing if someone is or not. PS: I found the following for kwin but its 2 years old and open: https://invent.kde.org/plasma/kwin/-/merge_requests/3024 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436318] Implement real session save/restore on Wayland
https://bugs.kde.org/show_bug.cgi?id=436318 --- Comment #217 from devsk --- (In reply to David Edmundson from comment #216) > This is a bug tracker, not a forum. If you're not adding something, don't > post things. I posted something that gets me 95% of the way there. If KDE had gotten me there 1/2/3/4 years ago, I would have moved to wayland much earlier and never complained. > People are working on this. Why so secret about it if people are working on it? We rarely see any updates here or anywhere else I could find with google search. What I could find showed that the development stopped more than 2 years ago. > This is the part that's in progress in xdg-desktop-portals and why the > Wayland part is seemingly stuck. Can you please point to the discussion thread for this? I need read-only access and have no (or had any) intention of spamming anyone. The last thing I want to do is to annoy the people who are working voluntarily on this feature. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436318] Implement real session save/restore on Wayland
https://bugs.kde.org/show_bug.cgi?id=436318 --- Comment #227 from devsk --- > David Edmundson is it resolved? > What does a "Status: Closed Later" mean? Now that you guys have pissed off the main developer, whatever implementation was coming in the spring is now off the table. just kidding:-) Nothing was coming this spring. All David had to do was to remove himself from the CC list and he would be fine. But he had to use his developer hammer. The patience and the kindness comes difficult these days! In the meantime, I made a change to my code snippet to match the title with regex because I realized that if the title of the window had some information that was variable (e.g. a tab in firefox has yahoo mail and N unread messages, and next moment it is N+10), it won't restore it correctly. In case you want a poor man's session restore: https://gist.github.com/devsk/9eff2d08d6cd5772afd2b178930b66ae PS: This feature will require a fresh, young (think college grad) set of eyes and will come in due time, and when it comes, it will come fast! I am very hopeful. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436318] Implement real session save/restore on Wayland
https://bugs.kde.org/show_bug.cgi?id=436318 --- Comment #215 from devsk --- (In reply to Kevin Gilbert from comment #211) > Can someone please give a status update on Wayland's progress on the > protocol mentioned in Comment #89? That can only happen if someone was working on it. Nobody is. The presence of this bug gives that wrong impression. I gave up on this bug ever getting fixed. That's why I ended up writing the set of elaborate shell functions I wrote. They do most of the work for session restore for me and I have been super happy with that. It works better than both the x11 and wayland restore in KDE right now. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436318] Implement real session save/restore on Wayland
https://bugs.kde.org/show_bug.cgi?id=436318 --- Comment #230 from devsk --- (In reply to Patrick O'Callaghan from comment #229) > (In reply to Nate Graham from comment #228) > > With https://invent.kde.org/plasma/kwin/-/merge_requests/7475, preliminary > > support for session restore has been merged for Plasma 6.4! > > > > This implements the WIP wayland protocol at > > https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/18. > > Since the protocol itself is WIP, things could change, and support should be > > considered somewhat experimental at the moment. > > > > Also keep in mind that since it's a new protocol, toolkits and apps need to > > opt into it. So don't expect everything to immediately start working as soon > > as you upgrade to Plasma 6.4. Support from apps should start trickling in > > over time, likely with KDE apps leading the way. There's still an open > > question as to what we do with apps that haven't opted in yet. This is still > > being discussed. > > > > Regardless, things are moving! Thanks for your patience here, everyone. Soon > > our long national nightmare of no session restore on Wayland will be over. > > :) > > That's encouraging news. Does this mean that at least window placement on > desktops will start working, even if individual windows don't restore their > state? Properties like desktop number, window position and window size should all be independent of the apps opting in. kwin controls these. This is 95% of the way there. Its the internal state of the app, like how many tabs of konsole in a window on desktop 3 or which file in kate on desktop 1 was open last, that will take some work on the app side. Nate, is my understanding correct? PS: Thanks for this much needed update! And thanks to David for working on the PR. Appreciate your efforts! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436318] Implement real session save/restore on Wayland
https://bugs.kde.org/show_bug.cgi?id=436318 --- Comment #209 from devsk --- > All the apps I've used already remember their sizes on restarting, so I don't > bother with that. konsole doesn't do that for me. It opens a single window of a dimension from the profile. My script opens as many konsole windows as you had open before, moves to the right location in the right desktop and sizes them. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436318] Implement real session save/restore on Wayland
https://bugs.kde.org/show_bug.cgi?id=436318 --- Comment #207 from devsk --- (In reply to Patrick O'Callaghan from comment #205) > > So this patch has actually nothing to do with session restore. I'd suggest > posting it somewhere else to avoid confusion. Yes. I don't think anybody cares about flipping the gestures behavior. I will keep this patch around. > I've had a quick look at your scripts but haven't tried them. They seem > quite complicated, but maybe they do more than mine. I've taken note of how > you use 'kdotool windowmove' and have added this to my own scripts (don't > know why I hadn't noticed this before :-). I'll upload them shortly (still > not very familiar with Gist to be honest). Yes. My script does do way more..:-) It saves a lot more information in a format which is easily read in bash. Then, it starts all the apps and waits for the user to ack the restoration process which restores their desktop, position and size. I had to add a lot of code for robustness e.g. some random processes make their way into 'kdotool search' when they don't have a real window associated with them e.g. plasmashell. For example, restoring from X11 to wayland, the window class changes from konsole to org.kde.konsole. For example, the size and location on wayland are floating point numbers sometimes, which was not apparent until wayland locked up on creating a window with 0 size with infinite memory allocation loop and got killed by OOM. For example, if you saved session from a crontab periodically, kdotool just doesn't find any windows because crontab does not have access to the user environment to access the DBUS. Lots of accounting for quirks. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436318] Implement real session save/restore on Wayland
https://bugs.kde.org/show_bug.cgi?id=436318 --- Comment #204 from devsk --- (In reply to Patrick O'Callaghan from comment #203) > (In reply to devsk from comment #202) > > (In reply to Roke Julian Lockhart Beedell from comment #198) > > > (In reply to imaginator from comment #197) > > > On older systems, this wouldn't really work, since there's always > > > something > > > that randomly takes ages to launch. Is there a way to wait for a specific > > > process to be invoked? If so, perhaps wait for `plasmashell` to be > > > running, > > > then run the script, since it's usually one of the last things to run. > > > https://stackoverflow.com/a/9118509/9731176 might be of use. > > > > I simply went with the option of starting all the applications from the > > saved session and then giving user a dialog box to OK the moving of the > > windows to their respective desktops, positioning them at the saved location > > and resizing them as per the saved info. > > > > The user just waits for all the application windows to start in the current > > desktop and then, pressing OK does the work. There are tricks to center the > > dialog box, keep it above all windows and activating it. kdotool works > > really well to do the rest. > > > > Checkout the gist I posted. Most of code can be used as is. Only binary > > names need adjusting/addition/deletion. > > What does kwin-fix_crazy_gesture.patch do? Seems to be a patch to the kwin > source code. On all platforms where I have used the swipe gesture, it takes to the right desktop when you swipe left. With X11, it was like that (imagine years of motor tuning). With wayland, it drove me crazy because every time I wanted to go a desktop, it took me to the wrong desktop. This behavior would be typically changeable but everything I tried using touchegg, confused the desktop navigation more: touchegg would move it to next but kwin would move it back, meaning that it did not change the desktop. After some real desperation, I took the drastic step of finding and toggling the gesture in code. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436318] Implement real session save/restore on Wayland
https://bugs.kde.org/show_bug.cgi?id=436318 --- Comment #201 from devsk --- I finally moved to wayland with 6.3. I had to jump through some hoops though. Here is the code in case someone wants to try the save/restore scripts (make sure to read the comments on the gist before using this code): https://gist.github.com/devsk/9eff2d08d6cd5772afd2b178930b66ae -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436318] Implement real session save/restore on Wayland
https://bugs.kde.org/show_bug.cgi?id=436318 --- Comment #202 from devsk --- (In reply to Roke Julian Lockhart Beedell from comment #198) > (In reply to imaginator from comment #197) > On older systems, this wouldn't really work, since there's always something > that randomly takes ages to launch. Is there a way to wait for a specific > process to be invoked? If so, perhaps wait for `plasmashell` to be running, > then run the script, since it's usually one of the last things to run. > https://stackoverflow.com/a/9118509/9731176 might be of use. I simply went with the option of starting all the applications from the saved session and then giving user a dialog box to OK the moving of the windows to their respective desktops, positioning them at the saved location and resizing them as per the saved info. The user just waits for all the application windows to start in the current desktop and then, pressing OK does the work. There are tricks to center the dialog box, keep it above all windows and activating it. kdotool works really well to do the rest. Checkout the gist I posted. Most of code can be used as is. Only binary names need adjusting/addition/deletion. -- You are receiving this mail because: You are watching all bug changes.
