Linux

13447 readers

4 users here now

A community for everything relating to the GNU/Linux operating system (except the memes!)

Also, check out:

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 2 years ago

MODERATORS

Ategon@programming.dev

anzo@programming.dev

dwraf_of_ignorance@programming.dev

222

After 6 Years, One of Wayland’s Most Annoying Problems is Finally Getting Fixed (itsfoss.com)

submitted 1 month ago by cm0002@europe.pub to c/linux@programming.dev

34 comments fedilink hide all child comments

There is a new merge on the Wayland GitLab repo. This new merge (of an old pull request) adds xdg-session-management protocol to Wayland. This is a big development and certainly a feature Linux users will enjoy.

As per the brief message in merge request:

For a variety of cases it's desirable to have a method for negotiating the restoration of previously-used states for a client's windows. This helps for e.g., a compositor/client crashing (definitely not due to bugs) or a backgrounded client deciding to temporarily destroy its surfaces in order to conserve resources.

This protocol adds a method for managing such negotiation and is loosely based on the Enlightenment "session recovery" protocol which has been implemented and functional for roughly two years.

In simpler words, session recovery is finally coming to Wayland.

you are viewing a single comment's thread
view the rest of the comments

[–] Tempy@programming.dev 1 points 4 weeks ago (1 children)

I mean many Wayland compositors is kinda like old browsers at the moment. They all implement a common spec and then implement a bunch of their own extensions to get features the spec doesn't allow for. And apps have to be aware of these custom extensions to make use of them. So in the KDE case, I imagine a lot of their apps are aware of KDEs own extensions to Wayland. But it doesn't mean all of them are.

[–] FishFace@piefed.social 1 points 4 weeks ago (1 children)

Surely it'd be absurd for each individual app to need to implement this spec - that defeats the whole point. I can believe it'd be down to Qt or some other library, but as I said, I'm sure that'd apply to those two apps.

[–] Tempy@programming.dev 1 points 4 weeks ago

Yeah, I imagine there's some QT bits for implementing a lot of it, if it detects them being available. Not being massively familiar with QT or how those two apps make use of it, I can't assume they'd be making use of the components that'd implement KDEs custom extensions. So you know shrugs