A contract they will try not to honor at every turn at that and if they do for the least amount possible.

I’m constantly surprised at this point how anyone fails at it. Not to mention there are a number of distros that provide them out of the box now and somehow people still say they couldn’t install it.

Finally time to bust this out again.

Too my knowledge the Snapdragon support hasn’t even been fully fleshed out in the kernel which is probably why you don’t have a stable experience.

You can configure the kde clipboard manager to never delete things or keep a higher amount of things. That is how I have mine setup.

I’ve recently gotten into using cockpit. I just wish it was as expansive as openSUSE’s yast.

Seems like a really big release. I’ve never used it, but I appreciate that they exist.

I was wondering this exact thing. Lots of stuff made it in, but not a peep from the linux gaming community when they had been talking about this for so long.

Even though we may bump heads on certain issues. I wish them the best of luck.

While I’m glad that there are people who do this work and certainly appreciate it. I also read his tweets and this person did seem to come off as a bit annoying. Like I get it. Security is important. However, things not moving as fast as you like is no reason to act like that.

Yeah, was gonna say the same. It works fine for me on native steam. But flatpak steam needs flatpak mangohud. This was actually one of the reasons that I stopped using flatpak steam though. Not a problem against flatpaks or even that it didn’t work. Hell it worked even during times when native steam didn’t work.

However, lots of small differences like this kinda make it harder to utilize existing software and information when the software and the communities around that software don’t have flatpak in mind.

Cool, while a lot of people are complaining. For those of us that still keep a chromium based browser around for the those few times where you need compatibility. These small improvements are very much welcome.

Cool. Always nice to see the whole document signing situation improving across all the different linux desktops.

Glad you brought up the software point. Back when I tried I had the same issue, but no one mentioned it when I was hearing about why I should try out a BSD system. Seems that even open source software often doesn’t have any of the BSD’s in mind and you end up needing to use that linux compat thing I remember seeing. If that even works for whatever you are trying to use.

I tried the flatpak for Zen, but it seem to crash quite a bit. How has your experience been?

No, not really. I believe it is because a lot of us linux users have more understanding of our systems, so we know why a certain outcome happened vs “it just works ^tm”.

Also I would like to point out something that I have been telling people for years whenever a post like this comes up. Windows and Mac users do the same thing. They constantly overlook bugs, bad design, artificial limitations, and just the overall lack of care when it comes to various details that more community oriented projects cater to. The reason is because of familiarity. Just like many of us will often not see issues with new comers struggles because we have already worked around all of the issues. These users do the same.

I found this in the forum that was linked on the planettwatt.com site. https://planetwatt.com/newforum/index.php?topic=1016.msg3100#msg3100

Didn’t find any source code though.

deleted by creator

I rarely see any comments on any Gnome posts here actually.

As someone who tries to look under the hood for a lot of the open source software I run, one thing that I have noticed is that there are a lot of cases where the general sentiment seems to be port to what. Wayland still doesn’t support a number of things that some applications require. A lot of developers that I have interacted with would rather have the app run through XWayland rather than have a wayland version of the app with less features or certain features grayed out.

In the case of one project in paticular, that being the Sunshine game streaming project. I have personally witnessed. Them implementing a solution for wlroots based compositor. Having that solution eventually break as wlroots based projects deprecate the protocol they were using in favor of a new one and now that protocol is looking like it too is old news and is going to be deprecated in favor of a newer and better protocol. What I am getting at here is that protocols not existing isn’t the only problem, but things are still very much in development. Even applications that implemented wayland support are being put in positions where they need yet another rewrite because things are far from finalized and still moving pretty fast.