@mammut @boo agreed, and that's what they rely on, though valve isn't by far the worst offender here

@kde@floss.social @kde@lemmy.kde.social is this the compositor handoff protocol? is that implemented by all major compositors already?

@woelkchen @Bilu47 I recommend that thing would be under the gpl, but to each their own

@Tersevs awesome, thanks for the explanation! I wanted something like this for a long while, especially since I usually game in weird places which are far from the computer. Also, I looked on flathub, and both apps are on there, even the server. Why would run the server as a flatpak, I don't know, but I know it's there, so yeah, gonna try this now.

@Tersevs can you detail the process a bit? where goes what component?

@popcar2 yes, the ntfs problem hit me as well, as I previously commented on other occasions. Also, I didn't think that intel mobile integrated gpu's wouldn't be recognised by opengl or vulkan, but that's how it goes apparently

@kde@floss.social @kde@lemmy.kde.social hmm, now that I try to join the matrix room, I see that I'm already in it. Wonderful! this means that the people there heard my rumblings regarding kde, mostly the software, not the desktop, being very inaccessible and unusable. For the desktop, the worst is the settings app

@kde@floss.social @kde@lemmy.kde.social ok, thanks! kde 5 is almost more accessible than gnome already, if it becomes better with kde 6, probably it's gonna be the default desktop for blind and visually impaired linux users, beginners and advanced alike. By advanced, I mean those who still use desktop environments, in stead of switching to a tiling window manager, like some I know do.

@kde@floss.social @kde@lemmy.kde.social lol, that's a pretty interesting mistake to make, I want to do it some time! Also, I'm reading stuff about the visual issues of plasma 6, especially under wayland. However, what about accessibility? would plasma 6 become more accessible? would the orca not reading windows under wayland thing be fixed? what about the issue where you have to click the desktop with the mouse first, before you can read it with screenreaders?

@theshatterstone54 @dvdnet90 yeah, those kinds of games are always reported to have issues for whatever reason

@falsem @Voytrekk because they always want to be remembered in history for something good, and they're desperately trying to make something that will eventually, through no try of their own, end up both *good* and ethical. Also, they want people to use their stuff more, so that they can eventually make it proprietary or something.

@BloodSlut @ShaunaTheDead hohoho, a good head start! I had to clear some environment variables from time to time as well, especially when it comes to wine stuff misinterpreting some vars I thought are only for some specific programs I use, so it's not the first time such happened to me. Glad it worked for you, also glad you worked out what env var to clear.

@ShaunaTheDead @BloodSlut of course it matters. Environment variables get passed to wine, after which other processes inherit them, simply because they are children of wine. Because wine makes them available to windows calls too, well, you get them in wine processes.

@ShaunaTheDead @BloodSlut what do you mean? you can use different wine prefixes for different applications, so I don't quite get it. Also, outside bottles, I'm not sure you can run wine in flatpak

@ShaunaTheDead @BloodSlut yeah, I don't think that the system wide dotnet will work under wine with the windows dependencies programs want, but yeah, if it does that'll be awesome

@JasSmith @miggs597 @F04118F @bionade24 lol, that's completely hilarious imo. Still though, that bug is definitely weird, I never got it my self on ubuntu or any of its derivatives. Is it only a pop OS issue then?

@bionade24 @miggs597 @F04118F @JasSmith I'm a bit out of the loop here, but what was the bug actually? Did he do this on livestream?

@setInner234 @deong yes, uninstall gtk-desktop-portal-gnome if you aren't using the gnome desktop, same for the kde variant if you aren't using kde. The gtk portal is most generic, it's supposed to be for any setup which doesn't have its own portals like many, or those who only have the minimum required, those which have something to do with compositor support, for example wlroots based setups. If your desktop has a portal backend, don't use the gtk one as you may be missing in functionality, arch devs should make more specific portal backend packages conflict with the generic gtk one, but o well.

yeah, wayland is awesome, unless you really need global shortcuts decided by the application, or a tun of other accessibility features. Still though, as you said, for most cases, wayland is good, and even the a11y features are getting ironed out, ever so slowly.

Personally, I wouldn't recommend immutable distros, as I think they limit our freedoms far too much, not that the way the general stack is going doesn't do that already. Not debating that here, since it's a hot and controversial topic currently, at least in the segment of the linux using population that cares about this stuff and which picked linux for that. Imo, if we do this, we'll basically make of the OS one block, from bootloader, to kernel, to initramfs, to display manager and finally desktop, especially since I'm hearing whispers of attempts at removing the tty kernel rendering being done, which will force us into using a specific compositor, desktop and so on, so we'll be exactly like windows or mac or android, so we lost everything, and then what's the point of linux?
If you want to use immutable distros anyway, I don't recommend silverblue for gaming, but I do recommend you give ublue linux a try, it has many drivers included, even some udev rules.