Not OP, but I use sunshine and moonlight for streaming my pc to various devices. Wayland forces me to use kms and I can't turn the monitors off while I'm doing it. Someone was working on a pipewire backend, so hopefully that goes somewhere.
GreenWithEnvy is also a nuisance on Wayland while Nvidia Settings Panel doesn't even work. I have a custom script just to control my fans on Wayland, but I'm eventually switching from Nvidia anyways, so it won't matter for much longer.
I read the words hybrid cpu 5 times and still thought this was something about hybrid graphics.
Maybe you should have considered the stuff he wanted to do before convincing him to use linux. I could have told you he'd have problems with that stuff. If he said he mainly plays steam games then sure, but not literally the most finicky, cumbersome games to get going in existence. Also out of curiosity because I haven't even thought about Roblox in like 8 years. I thought that was a browser game?
I'm already beta testing it. A solid improvement. Fixes a lot of long standing issues and makes quite a few existing features easier to use.
I'm beta testing 6.1 on Arch and can confirm that the feature is present and working great.
I feel like that may be true nowadays, but I remember back when I used to use ubuntu that the upgrade from 16.04 to 18.04 was pretty bad. Fedora has always worked great for me, but these days I only use rolling release distros in which case there aren't any major version updates in the first place, so the problem largely doesn't exist in the same context.
Yes, but that isn't really relevant to the current state of things. I still think Gnome's wayland implementation is ahead in some ways, but why would that matter when various game related stuff doesn't work on Gnome. We are talking about a gaming company here.
For the KDE part, something I haven't heard most people mention is the wayland support and how fast they are to pioneer and implement new protocols. DRM leasing is the reason why Gnome can't do VR games and I forget why they wouldn't implement it, but the why doesn't really matter for a company focused on gaming. There are quite a number of protocols that have followed this same story with Gnome.
Me and a buddy just set up syncthing and use that when we need to do this and don't want in third parties involved. Turn it off when you are done.
I'm still struggling with remote desktop software and other alternatives such as sunshine. KDE connect input sharing is inconsistent on wayland, but they will probably fix that eventually. xwaylandvideobridge is great when it works, but currently has an issue with eating input invisibly. Also, some things just seem to be kinda wonky. For example screen sharing portal when sharing my screen in a browser seems to open twice. Same with obs. Still no good virtual keyboard. If onboard worked on wayland that would be perfect.
I'm pretty sure it was an nvidia employee who was working on this for the last year.
Been using it since plasma 6
Cool, so jq but using sql instead of custom syntax. I wonder if it can output to plain text. That is what I usually use jq for.
Interesting, seems like quite a bit of work is needed to do this in rust, but hopefully that will benefit others who need to do the same. I do wonder if all of the efforts to do it in rust will be worth it though.
Funny thing about this. I had always though that creating new resolutions didn't work because I would always encounter an error no matter what guide I followed. It wasn't until a month ago that I discovered that the new resolution thing with xrandr doesn't work on nvidia.
There is an open bug report for it. Seems like it might be brought back from what I have read on there. https://bugs.kde.org/show_bug.cgi?id=481069. Someone has commented having already re-implemented the feature, but they seem to be stuck on something. If you can perhaps consider helping them out.
Honestly, I don't like any of the wayland keyboards, I wish onboard still worked, but sighhh.
It has been a while since I used fedora. I believe the last time was fedora 31 and heard murmurings of a dnf rewritten in c++ to be faster. Glad they actually pulled it off.
Thanks, that works.
The primary maintainer stepped down, but there has still been work done by other contributors. The primary problem is that the underlying library is reliant on x11. This is the same reason why nvidia-settings doesn't have all of its features on wayland. Basically if nvidia's on tool doesn't work then there is no way that green with envy can either. There is an open merge request attempting to switch to a different library that Nvidia says they plan to move to eventually, but it is slow going.