[-] [email protected] 16 points 1 week ago

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

[-] [email protected] 4 points 1 week ago

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.

[-] [email protected] 67 points 1 week ago

Like a SteamDeck vent exhaust?

[-] [email protected] 9 points 1 week ago

Syncthing, KDE Connect

[-] [email protected] 3 points 1 week ago

Fucking magnets. How do they work?

[-] [email protected] 11 points 2 weeks ago

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

[-] [email protected] 7 points 2 weeks ago

More non-binary than female lmao

[-] [email protected] 1 points 2 weeks ago

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.

[-] [email protected] 2 points 2 weeks ago* (last edited 2 weeks ago)

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

[-] [email protected] 2 points 2 weeks ago* (last edited 2 weeks ago)

Windows 98, Windows XP, Ubuntu 6.06, some other distros on and off, Arch Linux is the last OS I would ever need for desktop PC btw

[-] [email protected] 5 points 2 weeks ago* (last edited 2 weeks ago)

I like how you accidentally (edit: or maybe not) donated Wine devs by buying CrossOver license :D

[-] [email protected] 3 points 2 weeks ago

Long term NVIDIA might be going into either upstreaming their nvidia-gpu-open driver into Linux kernel, or they will help Nouveau+NVK development, which works relatively well with modern NVIDIA cards already (and NVIDIA just hired long time Nouveau maintainer)

view more: ‹ prev next ›

azvasKvklenko

joined 1 year ago