

What doesn’t at this point? All repos on github contaminated at this point. In couple of years border between code created by humans and code created by llm’s will be basically non existent.
The end is near. git clone until it’s too late!


What doesn’t at this point? All repos on github contaminated at this point. In couple of years border between code created by humans and code created by llm’s will be basically non existent.
The end is near. git clone until it’s too late!


Nothing is stable in this world nowadays.

For some reason when I use sddm shutdown sometimes just doesn’t work. Using GDM makes display doesn’t work (weird hdmi quirk with bitdepth). So instead I login via TTY and start my session manually. At least then I can shutdown my system. Usually.


I’ve been told that using linux similar to abusive relationships.
I wouldn’t know — I never had relationships.


Actually, I think dualshock works, it’s dualsence that have issues. Also, it works okay (I tested) in CachyOS, so whatever settings they made to udev rules or whatever — fixed it. Or they may just used old version of bluez, which is also a workaround, but you need to install insecure and 2 years old version at this point.
Also-also, it works fine via USB.


Oh, we doing “what doesn’t work for you” comment section? Count me in!
My LG TV consistently broken on multiple amd devices on linux. Something to do with how LG implemented HDMI protocol and how AMDGPU driver percepts it. I think it have something to do with color bit depth, cause all DEs allow to set 16 bit color (which is insane, not supported by any software nor my hardware and shouldn’t be a allowed as option without some special flags in my opinion) but like, there no protection and some DE/WM even defaults to max available bit depth, which in turn straight up doesn’t work and result in black screen.
Windows or nvidia — those work fine.
Another pain in the ass for me — connecting dualsense controller via bluetooth. It connects, then just disconnects. There a workaround that includes fetching it’s ID via terminal, then using commands to connect and entrust that device. After that it connects fine. Until you need to reconnect it, that is, cause it stops being recognized. Apparently that was fixed like, a year ago. Yeah, right.
Another pain for me would be steam client on wayland, but Valve finally started working in that direction so I will hold my complains for now.


You probably joking, but that actually a thing in China and was a thing in USSR
After watching recent ram cartel investigation from gamernexus: fuck them. They got what they fucking deserve.