• 0 Posts
  • 9 Comments
Joined 6 months ago
cake
Cake day: January 6th, 2025

help-circle
  • Onihikage@piefed.socialtoLinux@lemmy.mlDistro choice
    link
    fedilink
    English
    arrow-up
    3
    ·
    3 days ago

    Thanks for bringing up the display managers and Wayland support, I don’t know enough to weigh in on those.

    And understand that its not a choice just between those two DEs.

    If OP sticks with Mint, that would be the case, but Bazzite only has two DEs right now (KDE and Gnome, with Budgie “coming soon”). OP doesn’t sound like they want to tinker much, they just want something that works with a modern GPU and will keep working. Bazzite certainly fits that use-case, at least in my experience.


  • Onihikage@piefed.socialtoLinux@lemmy.mlDistro choice
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    1
    ·
    3 days ago

    They’re mostly equivalent, but I think KDE has the edge when it comes to customization, included utilities, and advanced features. The Apple/Windows comparison is not limited to their look and feel, it also applies to the philosophical differences between the Gnome and KDE teams. If you plan to use SteamVR, KDE is supposedly better for that specific use case, but I can’t personally verify that.

    The feature sets and quality of both DEs are constantly improving, so a comparison from 6 months or a year ago could already be outdated. I haven’t used Gnome in quite a few years, so I’m basing this entirely on what others have said about it.


  • Onihikage@piefed.socialtoLinux@lemmy.mlDistro choice
    link
    fedilink
    English
    arrow-up
    7
    arrow-down
    3
    ·
    edit-2
    3 days ago

    If you want to use newer hardware, and would rather not tinker with the system to get it working (and then have to maintain that tinkering yourself if something breaks later), Bazzite is probably the better option. It’s based on Fedora Atomic which is almost identical to rolling-release like Arch. I switched from Windows to Bazzite more than a year ago and have personally had no major issues, never had to mess with drivers or kernel updates due to the image-based system, and pretty much everything I might need for some workaround or another is included in the image. The community is very active on both the Discord and the web forum, and the documentation on the website is good as well, so there’s no shortage of help and available resources if you run into an issue or don’t know how to do something.

    The main thing you need to be aware of going in is to be sure of which Desktop Environment you want (KDE or Gnome), because their user-space configs (which are not part of the image) interfere with each other so you can’t really switch between them without breaking a lot of things. Coming from Windows, I picked KDE and have been very happy with it.



  • I don’t know what it is but it feels like i went from crashing like maybe once a week, to multiple times a day as time has gone on.

    Make sure to disable all autosaves, disable quicksaves, and never save over an existing save. Something about Bethesda’s save system has never quite worked properly when overwriting existing saves (which is how autosave and quicksave function), you have to force it to create new saves and manually delete the old ones yourself later.

    After the remaster came out, I started replaying the original with a small modlist, and saw similar degradation in stability until I remembered to do that. Currently it’ll crash if I’ve had the game open more than a couple of hours, so I just manually save often and restart the game any time I feel like it’s been open for a while. It doesn’t seem to be getting worse anymore so I think I’m in the clear.


  • This tends to happen when there’s some kind of DNS configuration issue, most likely DNS over HTTPS. If that’s explicitly disabled in Firefox and the problem still occurs, then there are some troubleshooting steps to consider:

    • Is Firefox up to date?
    • Is the system up to date?
    • Have you tried reinstalling the extension?
    • Have you tried a clean Firefox profile with only the extension installed?
    • Has the system been restarted since the problem began occurring?

  • An in-browser VPN extension is innately contained to the browser it’s installed to, which has several benefits:

    • high-bandwidth activities outside of the browser, such as software updates and game downloads, which many people don’t consider part of their privacy profile, won’t be limited by the speed of the VPN
      • this is also possible with split-tunneling, but that requires more configuration, and not all VPNs support split tunneling on all OS environments
      • the bandwidth savings are a big reason why most VPNs create browser extensions and encourage their use, as bandwidth use from web browsing is always going to be smaller than full system bandwidth
    • different browsers or browser profiles can be configured to use different VPN endpoints, while most system-level VPNs can only select one endpoint for the entire system
    • setup and configuration will be more OS-agnostic; setting up a system-level VPN properly on Linux can be more difficult than Windows or MacOS depending on the distro and system config
    • running the VPN at the browser level usually takes less resources than at the system level, so on very old or very weak systems, it may be the best option

    Of course, if you’re downloading actual Linux ISOs and want to avoid a nasty letter from your brain-dead ISP that thinks all torrenting is illegal, or if you just don’t want your ISP to spy on you and sell what it learns to data brokers, installing the VPN at the system level is a great option. Remember to bind any torrent software to the VPN to prevent leaks ;)


  • EarlyOOM is great for keeping systems responsive. I can’t understand why the default memory management on many distros still seems to be “do everything possible to avoid automatic termination of processes even if that means the system becomes borderline unusable.” It makes for a terrible user experience, and most users are just going to restart the machine when it happens rather than try to struggle through a slide show to manually kill whatever’s causing the problem.