I also have a 3080 and have been considering switching to AMD, but with the problems you describe. Maybe, I’ll give Intel’s offerings a shot assuming the graphics cards don’t suffer the same way their cpu’s are right now.

Weird, I haven’t had any issues since I bought it on steam whenever the official release was.

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.

Sounds like a case where machine learning would actually be useful.

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.

I bought 64 gigs of ram and still refuse to use it.

Endeavor and Arch both default to whatever upstream defaults to, so if you update Endeavor to plasma 6 then it will be wayland by default.

The latest driver should be 550 series. If VS Code is running under xwayland then you are probably going to be waiting a few more months for explicit sync to be finished in xwayland and various other pieces of the graphics stack https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/967. Since vs code is electron you can try running it with the wayland command line arguments --ozone-platform=wayland. There might be some other arguments you need to pass depending on the version of electron.

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.

kstart5 on plasma6? Try making a new user and seeing if the issue still happens.

Same, this is also the first time that I am able to use wayland on my nvidia card. There are still issues, but there are being worked out. 6.0.2 solved the issue with plasmashell just quitting whenever I turned one of my monitors off.

I’m using endeavourOS too, I didn’t even know there was an update script. We don’t all just use pacman?

The only thing I want to add is that installing arch the right way doesn’t matter if you have installed any linux distro manually. You could install debian the arch way if you wanted to and still come out with the same skill set.

Is this available over rss? I was trying to add it, but wasn’t able to find a feed link.