Nice

I saw this problem for the first time yesterday. Run dmesg to look for errors from the kernel, for me I had amdgpu 0000:03:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data. I took this to mean that my system couldn’t communicate with the monitor to change brightness anymore. When my system is idle, it first dims the monitor before turning it off, so when I wake it back up it’s stuck on low brightness like this. Simply turning my monitor off and back on seemed to fix it.

Yes, most people aren’t aware of it as they’ve seen inside Program Files and assumed that was all the program’s data.

Bro you’re messing with wine prefixes? You already know more than most and clearly have the motivation and ability to do what you want. You’ll go far, just google what you need when you need it like the rest of us :)

It’s the price of bleeding edge :) Hope you find what you’re looking for in Nobara, my dude.

I’ve had the same issues with Endeavour, sometimes you get buggy software and need to roll back. I do a full system backup once a week and update once or twice a day (I like updating frequently as it makes it obvious which package broke your system). When I get a bad package I just restore from backup but exclude /home. Then from there I install packages one at a time until I find that bad one and then just ignore it for a while. It really hasn’t been too bad. I don’t think you’ll find anything like the AUR if you start distrohopping. Debian is the king of set it and forget it, but it might be a shock to go back older packages of everything.