I’ve wanted this for a while; when I’m done with my computer, I don’t mind it staying on a bit longer to do this, rather than when I next turn it on when I (presumably) want to do something. Great add!
I’ve wanted this for a while; when I’m done with my computer, I don’t mind it staying on a bit longer to do this, rather than when I next turn it on when I (presumably) want to do something. Great add!
my favorite thng about this image is how the mandatory hamburger acknowledgement is interrupting a scene where a man is getting shot in the face, emphasizing that the target audience is Americans
In defense of this warning, when I first put my application on Flathub, I had it because of how file i/o worked (didn’t support XDG portals, so needed home folder access to save properly). It did actually motivate me to get things working with portals to not request the extra permissions and get the green “safe” marker.
A lot of apps will always be “unsafe” because they do things that requires hardware access, though, so I could see them wanting something more nuanced.
In my case I had another WM installed (iceWM, I think it was there by default?) and did the upgrade from there. Unfortunately it does seem that if you try to upgrade from within KDE it will crash part-way (I used zypper dup and it failed).
On my PC at home I’m running KDE Plasma on OpenSUSE Tumbleweed with two monitors: 1440p 240 Hz, 4k 60 Hz. Both are connected via displayport to an RTX2080. It works perfectly fine for me.
A while back, I used Linux Mint on the same system and it was a headache, where it would sometimes boot to a blank screen and I would have to restart a random number of times before it would work. I never did figure out the underlying cause, it just went away when I changed distros for other reasons…
Did I understand it right that you installed the driver manually? It’s generally better to use the Fedora Nvidia driver package (sudo dnf install akmod-nvidia), than to download from Nvidia’s website. I’m on Fedora 40 too, and currently using the 560.35.03 version of the driver on a 2080, which upgraded from 555 recently - I wonder if that’s what broke compatibility with your version of the driver. It may be that you need to update. Only thing I’m not sure of is how this will interact with manually-installed drivers…