“Zero excuse” is a bit of a stretch, I aggree, but most things work really well now in my, and a lot others experience, at least recently. I also do my work full time on Linux, it’s mostly devops/sysadm work so a lot of what I use is terminal, web browser and well… Teams and Slack (the first one work well with an unofficial client, the latter got fixed recently), so it’s really not that hard to switch to Wayland. On my private machine I do mostly gaming, consuming content, some basic audio production and editing and there I rely a lot on X11 programs some running through Wine. They all work fine on Xwayland, recently even including HiDPI support (at least with simple one screen scenario). It’s really hard to find completely broken use case unless it’s something like automation scripts that move windows around, emit click or capture keyboard input globally and were designed strictly for X11. Oh, and apps that have multiple windows and request certain positioning - that is currently still missing and WIP.

On the other hand, the topic was originally about VR. While still kinda early, gimmicky and niche, it’s pretty cool modern tech. Good luck with that on X. Even more common cases like high refresh rates with multi screen setups, VRR, all suck on X11 while working nicely on Wayland for some time now, at least with good drivers.

Absolutely no kids ever even if I wasn’t gay or had ability to adopt. I don’t remember my childhood positively at all, I think my parents should’ve never decided to have kids, and despite me trying hard to not be like them, I found myself making similar mistakes. I don’t understand people being so obsessed about having kids and saying stuff like “wait until you got ur own”, I’m like bitch it’s not happening ever unless it’s a nightmare I wake up all wet after with relief that it’s not real

That something being probably Microsoft Teams piece of crap app or similar bullshit like Discord, all of which FOSS devs can’t do anything about even if they could. Or simply your system incompatibility like NVIDIA proprietary drivers.

If you expect everything to just work as if it was consumer OS that is fully supported by 3rd parties, Linux might not be the best choice for you in general.

Yes, but YouTube is kind of shit these days with how it works for creators and quite often getting more views is a matter of setting clickbait title and thumbnail. He actually is one of the biggest Linux creators on yt

The title of the video is actually “Plasma 6.1: the BEST LINUX DESKTOP (in my opinion)” and the video is not about argument what’s the best. It’s just regular coverage of the release. Just a little clickbait

Depends on what is most desired. Plasma is the most complete and feature rich desktop experience on Linux at the moment. The most polished one? Certainly not.

Like a SteamDeck vent exhaust?

Syncthing, KDE Connect

Fucking magnets. How do they work?

Honestly I didn’t think about the wording when I forst saw it and only was like “oh I see” when I saw all the downvotes. It would believe it’s possible not to notice when writing it or using some template to make release notes for each release

Gaming laptops are clunky, ugly, not practical (yeah, technically portable, but not very convenient), loud, hot, drink a lot of juice and always need to be connected to a giant power brick. The worst kind of computer

Who cares about what you need. The cat spotted a bed with heating feature

The problem with HDR is that it’s very difficult to get working on X11, to the point that those who tried (NVIDIA, 8 years ago) gave up long time ago and moved on. X11/Xorg is legacy solution that is still there mostly because it always was and things still depend on it.

Wayland can get HDR and it gradually does, but it wasn’t priority for quite a long time as there was much more basic stuff missing, to the point many users wouldn’t switch until recently, and because X was still the preferred display system for most users for such a long time, it wasn’t priority to fill missing gaps on Wayland side and it wasn’t moving forward too fast.

Now that things are coming together, over half of the user base (probably) already switched to Wayland, there are more desktop/WM options on the Wayland side, with fewer showstoppers every year, finally NVIDIA drivers start working on Wayland, color management is also getting closer to be part of the official spec. It’s already possible to play games in HDR, but with some solvable caveats: if a game runs on X11 (which for Wine/Proton the Wayland driver is still experimental) they use swap-chain hack to that’s only available in the gamescope compositor, so either in full blown Steak Deck session or wrapped in nested gamescope instance. This will be more out-of-box when:

1. the stable color management protocol is actually in place, more compositors implement it (currently only gamescope and kwin_wayland have HDR)
2. winewayland.drv stabilizes and implements HDR
3. Wine and Proton run on Wayland natively by default

Ugh, no offence to someone who worked on it but sddm is such a failure of display manager. It was only introduced around 10 years ago replacing kdm. It was meant to be simple (duh, thus the name). It has all sorts of issues and is constantly being fixed, just for something super basic like login screen

More non-binary than female lmao

The HDMI/DP was my wild guess. For now the problem should also go away if you just change in-game resolution for whatever is your screen. Maybe the problem isn’t being addressed because it was reported to Mesa user-space driver, but maybe the problem is in kernel module. It’s also not 100% always reproducible.

Actually it looks surprisingly tidy. Would autohide it (when windows touch it) though

I know this issue. It’s reproducible when

• Using AMD on Wayland
• Only on certain screens or only on HDMI (I never reproduced that when using DP)
• The game is running in non-native resolution, meaning the compositor is doing upscaling
• The game window is full screen and focused - the black blocks go away if you show some desktop menu or focus other window on top - so basically looks like only happens when the direct scanout protocol is doing its thing
• not only in Steam games, in most games in general

The problem has long been reported in Mesa project, but nothing was done to help. My bet is that the bug sits in amdgpu kernel driver and not user space.

https://gitlab.freedesktop.org/mesa/mesa/-/issues/8705

EDIT: maybe it’s worth to report in kernel bugzilla or wherever amdgpu kernel driver bugs would go. I don’t reproduce this on my end anymore, because I changed my screen and it uses DP

EDIT2: I could only reproduce it on RDNA2 and yours is RDNA3. I had Polaris (RX 570) for quite some time and it was running on Wayland. Maybe it only happens on newer cards, maybe it’s regression added along the way

Probably not yet

The problem will only get solved if there will be reliable methods for detecting cheats that don’t require direct ingeration in a client operating system directly.