Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)PL
Posts
1
Comments
59
Joined
2 yr. ago

  • I recently bought a projector that I had to trick into not connecting to Wifi by telling it that it was connected to ethernet until it gave up. It will never know the wifi password. It gets an HDMI signal, it shows the HDMI signal, that is its purpose.

  • 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...

  • 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.

  • If you're on KDE using Discover for updates, the default on a lot of distros is to apply updates on reboot, but you can change this under the Software Update section of the System Settings app. I think it's not a bad idea; I'd rather have a bit of controlled downtime than risk borking my system.

  • 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....

  • I've had it since 2016, so it's close to 7 years now. I replaced the screen and battery on it, but it has been pretty solid. Actually, uptime is something that's an advantage for self-repairable stuff: when the screen needed to be replaced, it still worked enough to use, which I did until the replacement arrived. Takes a minute to swap the screen and then it's running again.

    I'm based in Germany so I only used it in the US when traveling. Maybe the 5 will be the one where they decide to cover the US officially? It seems like there's more attention to repairability than there was 7 years ago...