Those who don’t have the time or appetite to tweak/modify/troubleshoot their computers: What is your setup for a reliable and low-maintenance system?

Context:

I switched to Linux a couple of years ago (Debian 11/12). It took me a little while to learn new software and get things set up how I wanted, which I did and was fine.

I’ve had to replace my laptop though and install a distro (Fedora 41) with a newer kernel to make it work but even so, have had to fix a number of issues. This has also coincided with me having a lot less free time and being less interested in crafting my system and more interested in using it efficiently for tasks and creativity. I believe Debian 13 will have a new enough kernel to support my hardware out of the box and although it will still be a hassle for me to reinstall my OS again, I like the idea of getting it over with, starting again with something thoroughly tested and then not having to really touch anything for a couple of years. I don’t need the latest software at all times.

I know there are others here who have similar priorities, whether due to time constraints, age etc.

Do you have any other recommendations?

    • JustEnoughDucks@feddit.nl
      link
      fedilink
      arrow-up
      8
      arrow-down
      1
      ·
      5 days ago

      Doesn’t ucore also have to restart to apply updates?

      Not super ideal for a server as far as maintenance and uptime to have unexpected, frequent restarts as opposed to in-place updates, unless one’s startup is completely automated and drives are on-device keyfile decrypted, but that probably fits some threat models for security.

      The desktop versions are great!

      • notfromhere@lemmy.one
        link
        fedilink
        arrow-up
        1
        arrow-down
        1
        ·
        5 days ago

        Run k3s on top and run your stateless services on a lightweight kubernetes, then you won’t care you have to reboot your hosts to apply updates?

      • Axum@lemmy.blahaj.zone
        link
        fedilink
        arrow-up
        15
        arrow-down
        4
        ·
        edit-2
        5 days ago

        Not super ideal for a server as far as maintenance and uptime to have unexpected, frequent restarts

        This is such a weird take given that 99.9% of people here are just running this on their home servers which aren’t dictated by a SLA, so it’s not like people need to worry about reboots. Just reboot once a month unless there’s some odd CVE you need to hit sooner than later.

        • dino@discuss.tchncs.de
          link
          fedilink
          English
          arrow-up
          2
          ·
          4 days ago

          So why would somebody run that on their homeserver compared to tried and true staples with tons of documentation? 🍿

          • asap@lemmy.world
            link
            fedilink
            English
            arrow-up
            2
            arrow-down
            1
            ·
            edit-2
            4 days ago

            It’s just Fedora CoreOS with some small quality-of-life packages added to the build.

            There’s tons of documentation for CoreOS and it’s been around for more than a decade.

            If you’re running a container workload, it can’t be beat in my opinion. All the security and configuration issues are handled for you, which is especially ideal for a home user who is generally not a security expert.

        • JustEnoughDucks@feddit.nl
          link
          fedilink
          arrow-up
          4
          ·
          5 days ago

          That is very fair!!

          But on the other hand, 99.9% of users don’t read all of the change notes for their packages and don’t have notifications for CVEs. In that case, in my opinion just doing updates as they come would be easier and safer.

      • asap@lemmy.world
        link
        fedilink
        English
        arrow-up
        7
        arrow-down
        1
        ·
        edit-2
        5 days ago

        They won’t apply unexpectedly, so you can reboot at a time that suits. Unless there’s a specific security risk there’s no need to apply them frequently. Total downtime is the length of a restart, which is also nice and easy.

        It won’t fit every use-case, but if you’re looking for a zero-maintenance containerized-workload option, it can’t be beat.

    • moontorchy@lemmy.world
      link
      fedilink
      arrow-up
      3
      ·
      4 days ago

      Yeah, sure. I was running Bluefin-DX. One day image maintainers decided to replace something and things break. UBlue is an amazing project. Team is trying hard but it’s definitely not zero mainainace. I fear they are chasing so many UBlue flavours, recently an LTS one based on CoreOS, spreading thin.

      • j0rge@lemmy.ml
        link
        fedilink
        arrow-up
        5
        arrow-down
        1
        ·
        edit-2
        4 days ago

        If you depend on third party modules you’ll end up with third party maintenance - we didn’t purposely decide to break this we don’t work at Nvidia.

        • moontorchy@lemmy.world
          link
          fedilink
          arrow-up
          2
          ·
          4 days ago

          Jorge, OP asked about “not having to really touch anything for a couple of years”. I am just sharing my experience. Big fan of containers and really appreciate your efforts of pulling containers tech into Linux desktop. Thank you!

          I don’t understand the answer though. Maybe I am missing something here. There’s an official Bluefin-DX-Nvidia iso. Nvidia-containers-toolkit was part of that iso.

          On a separate note, I liked the idea of GTS edition. Since few weeks ago iso became unavailable pending some fix. At the same time I see loads of new LTS edition buzz. It’s still in Alpha though. I feel confused.

          • j0rge@lemmy.ml
            link
            fedilink
            arrow-up
            4
            arrow-down
            1
            ·
            edit-2
            3 days ago

            I don’t understand the answer though.

            The answer is if you’re depending on software that is closed and out of your control (aka. you have an Nvidia card) then you should have support expectations around that hardware and linux.

            There are no GTS ISOs because we don’t have a reliable way to make ISOs (the ones we have now are workarounds) but that should be finished soon.

            • moontorchy@lemmy.world
              link
              fedilink
              arrow-up
              1
              ·
              3 days ago

              Thanks for clarifying, Jorge. I wish I lived in a perfect world where all hardware and software follow FOSS principles. Until then I will have to rely on the other distros that embrace an imperfect reality. I cannot reconcile how Bluefin targets developers and NVidia, unfortunately is not something many of those developers can afford to ignore. Good luck with your project!

              • j0rge@lemmy.ml
                link
                fedilink
                arrow-up
                1
                ·
                3 days ago

                I cannot reconcile

                It’s like a saving throw in a video game, most times you can make it, but every once in a while you don’t lol.

      • asap@lemmy.world
        link
        fedilink
        English
        arrow-up
        3
        arrow-down
        1
        ·
        edit-2
        4 days ago

        🤷 I’ve been running Aurora and uCore for over a year and have yet to do any maintenance.

        You can roll back to the previous working build by simply restarting, it’s pretty much the easiest fix ever and still zero maintenance (since you didn’t have to reconfigure or troubleshoot anything, just restart).

      • asap@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        arrow-down
        1
        ·
        edit-2
        4 days ago

        It’s just Fedora CoreOS with some QoL packages added at build time. Not niche at all. The very minor changes made are all transparent on GitHub.

        Choose CoreOS if you prefer, it’s equally zero maintenance.

    • trevor (he/they)@lemmy.blahaj.zone
      link
      fedilink
      English
      arrow-up
      16
      arrow-down
      1
      ·
      5 days ago

      This is the way. The uBlue derivatives benefit from the most shared knowledge and problem-solving skills being delivered directly to users.

      Between that, and using a decorative distrobox config, I get an actually reliable system with packages from any distro I want.

    • lka1988@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      6
      ·
      edit-2
      5 days ago

      As someone who just had to bandaid an unexplained battery draw on his wife’s MacBook - no, Mac OS no longer “just works”. Apple buries some of the most basic settings inside a command line-only tool called pmset, and even then those can be arbitrarily overridden by other processes.

      And even after a fresh reinstall and new battery, it still drains the battery faster in hibernation mode than my Thinkpad T14 G1 running LMDE does while sleeping. Yeah, that was a fun discovery.

      That Thinkpad is by far one of my most dependable machines.

      • mbirth@lemmy.ml
        link
        fedilink
        arrow-up
        2
        ·
        5 days ago

        If you have battery drain, make sure you’ve disabled the option to regularly wake up and do some background processing (check for emails, sync photos, etc.). Settings → Battery → Options… → Wake for network access. (Or search for “Power Nap” in the System Sertings dialog.)

        No need to use pmset for that.

        • lka1988@lemmy.dbzer0.com
          link
          fedilink
          English
          arrow-up
          2
          ·
          edit-2
          5 days ago

          So here’s the thing - if you can think of it, I’ve already tried it 😅 I spent a week and a half sifting through countless forum posts on Apple’s own support center, Macrumors, reddit, and a host of other forums.

          The “Wake for network access” setting was the first thing I disabled after I wiped and reinstalled the OS. Among a number of other settings, including “Power Nap”. Still got the fucking “EC.DarkPME (Maintenance)” process firing off every ~45 seconds, no matter what I did, causing excessive insomnia and draining the battery within 12 hours.

          What I ended up doing was using a little tool called “FluTooth” to automatically disable wifi/Bluetooth on sleep (the built-in OS settings did fuck-all), set hibernationmode to 25, and a few other tweaks with pmset that currently escape me (edit: disabled networkoversleep, womp, ttyskeepawake, powernap - which was still set to 1 even with the setting in System Settings was disabled 🤨), and a couple others I can’t remember as it’s not here in front of me).

          I put several full charge cycles on the brand new battery before it finally calmed the fuck down.

          • SL3wvmnas@discuss.tchncs.de
            link
            fedilink
            arrow-up
            1
            ·
            2 days ago

            I feel you. I still use an intel macbook with tweaks i cannot remember plus 3rd party utils like Turbo Boost switcher. That experience alone has kept me from upgrading to newer models.

            In retrospect my powerbook g4 (Ti) and os 9 was peak computing.

            • lka1988@lemmy.dbzer0.com
              link
              fedilink
              English
              arrow-up
              1
              ·
              edit-2
              2 days ago

              My Thinkpad T14 running Linux Mint (LMDE) gets better battery life on “Suspend” than that damn MBP does when hibernated. It’s the 2017 A1706, too - out of ALL the variants it had to be that one 😂

              • SL3wvmnas@discuss.tchncs.de
                link
                fedilink
                arrow-up
                1
                ·
                edit-2
                17 hours ago

                Oh no. Maybe some Incense to cleanse the demons? (⊙_⊙)

                Edit: I just remembered I had a similar problem, after changing the battery on my 2015. This thread at macrumors helped me tremendously especially the last entry (did it on three seperate days before it had an effect.) but I’m sure you already tried all of that. Just for the off chance.

                these Intel Macs were such a bad experience.

                • lka1988@lemmy.dbzer0.com
                  link
                  fedilink
                  English
                  arrow-up
                  1
                  ·
                  16 hours ago

                  That thread was a godsend. Turning off tcpkeepalive was the other one that I couldn’t remember, but that seemed to help out as well.

                  My wife has had multiple MacBooks over the years (I set up her old 2009-era A1278 with Linux Mint for the kids to do homework), and after I “fixed” it and talked about the longer wake-up process, she told me that’s what she was used to already and the “super fast wake up” was a very new thing for her when she bought it. So no complaints from her, and the battery performs better. Win/win.

  • merthyr1831@lemmy.ml
    link
    fedilink
    English
    arrow-up
    14
    ·
    4 days ago

    fedora has been this for myself. maybe tweaking every now and then to fix whatever edge cases I’ve run into but it’s the least painful distro I’ve used so far

  • Mactan@lemmy.ml
    link
    fedilink
    arrow-up
    1
    ·
    3 days ago

    every system is only as stable as the user. anybody can break Debian or any other “stable” distro of renown the second they go tinkering, adding PPAs or anything else

  • DigitalDilemma@lemmy.ml
    link
    fedilink
    English
    arrow-up
    6
    ·
    3 days ago

    Debian stable is as hassle-free as you’ll get.

    It sounds like your issue is more with having to migrate to a new laptop. Firstly - buy laptops that are more linux compatible and you’ll have fewer niggles like with sound, suspend and drivers.

    Secondly - use “dpkg --get-selections” and “–set-selections” to transfer your list of installed software across to your new laptop. Combined with transferring your /home directory, user migration can be speeded up.

    • Churbleyimyam@lemm.eeOP
      link
      fedilink
      arrow-up
      2
      ·
      3 days ago

      Firstly - buy laptops that are more linux compatible

      This is the thing: The laptop is from Starlabs, supposedly made for Linux…

    • ReversalHatchery@beehaw.org
      link
      fedilink
      English
      arrow-up
      3
      ·
      5 days ago

      in my app the post starts with this sentence:

      Those who don’t have the time or appetite to tweak/modify/troubleshoot their computers […]

      • Nora@lemmy.ml
        link
        fedilink
        arrow-up
        1
        ·
        5 days ago

        Yeah just use the default setup. Some minor tweaks at first, then it stays the same forever.

        • Bee_R@beehaw.org
          link
          fedilink
          arrow-up
          2
          ·
          5 days ago

          A minor tweak on another system, like an obscure driver, can be a huge headache on nix

    • Leaflet@lemmy.world
      link
      fedilink
      English
      arrow-up
      5
      ·
      5 days ago

      NixOS was troubleshoot central for me. Not all programs behaved as expected with Nix’s unique design.

  • mesa@piefed.social
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    1
    ·
    5 days ago

    PopOS is very stable as a desktop. It also keeps up to date with packages better than base Ubuntu in my opinion.

  • tasankovasara@sopuli.xyz
    link
    fedilink
    arrow-up
    5
    arrow-down
    1
    ·
    5 days ago

    You’re not going to believe this, but I’ve found Arch is it. My desktop install was in December 2018: Sway with Gnome apps. Save for Gnome rolling dice on every major update, it’s been perfectly boring and dependable.

    • navordar@lemmy.ml
      link
      fedilink
      arrow-up
      7
      ·
      5 days ago

      There are two camps of Arch users:

      1. Use it despite it breaking on every update, because of AUR and other benefits
      2. What? Arch breaks?
  • cerement@slrpnk.net
    link
    fedilink
    arrow-up
    31
    arrow-down
    1
    ·
    4 days ago
    • yet another vote for Debian Stable
    • second the comment on: if you need a newer kernel for hardware reasons, use backports
    • Xfce
    • stick to flatpaks when dealing with wanting to try out a new program (if you like it, then make the decision to use apt or not)
    • don’t confuse “hasn’t been updated” with “hasn’t needed to be updated”
    • d00phy@lemmy.world
      link
      fedilink
      English
      arrow-up
      21
      ·
      5 days ago

      This really is the answer. The more services you add, the more of your attention they will require. Granted, for most services already integrated into the distro’s repo, the added admin overhead will likely be minimal, but it can add up. That’s not to say the admin overhead can’t be addressed. That’s why scripting and crons, among some other utilities, exist!

      • umbrella@lemmy.ml
        link
        fedilink
        arrow-up
        2
        ·
        edit-2
        5 days ago

        i think its more about modifying the system behavior, esp on desktop oses. i have many local services running on my server, and if set up right, its pretty much no maintenance at all.

    • umbrella@lemmy.ml
      link
      fedilink
      arrow-up
      9
      ·
      5 days ago

      i want to try another distro than ubuntu, but the damn thing isnt giving me a single excuse to format my system. it doesnt break if you don’t fuck with it.

    • dino@discuss.tchncs.de
      link
      fedilink
      English
      arrow-up
      4
      arrow-down
      15
      ·
      4 days ago

      Such a bad comment, what does tinkering mean? Not use any software besides the default one? So only browsing and text apps? facepalm

      • Magiilaro@feddit.org
        link
        fedilink
        arrow-up
        11
        ·
        4 days ago

        Tinkering, in my personal definition, would mean installing third party repositories for the package manager (or something like the AUR on Arch) or performing configuration changes on the system level… Just keep away as most as possible from accessing the root user (including su/sudo) is a general a good advice I would say.

  • socphoenix@midwest.social
    link
    fedilink
    arrow-up
    3
    arrow-down
    1
    ·
    5 days ago

    For as much hate as it gets Ubuntu (or kubuntu for the kde version) will feel very familiar in usage and will have a newer kernel. It’s my default it just needs to work distro if regular Debian isn’t an issue due to drivers or something similar.

    • jBoi@szmer.info
      link
      fedilink
      arrow-up
      2
      ·
      5 days ago

      Eeh, idk. I’ve first installed kubuntu 20.04, then used it all the way up to 24.04, updating each version. I tinkered with it, added ppas, ect. and each update new random issues started piling up. I switched to fedora when the update to 24.04 completely broke my system, I don’t recommend kubuntu.

  • Magiilaro@feddit.org
    link
    fedilink
    arrow-up
    5
    ·
    4 days ago

    My Arch Linux setup on my desktop and my servers are low-maintenance. I do updates on my servers every month or so (unless some security issue was announced, that will be patched right away) and my desktop a few times a week.

    Nearly anything can be low-maintenance with the proper care and consideration.

    For your constraints I would use just use Debian, Alma Linux or Linux Mint and stick with the official packages, flathub and default configuration on the system level. Those are low-maintenance out of the box in general.

  • JustARegularNerd@aussie.zone
    link
    fedilink
    English
    arrow-up
    9
    ·
    3 days ago

    Linux Mint Debian Edition (LMDE) is my pick.

    I’ve got two study laptops and apart from Tailscale giving me some grief very recently with DNS resolution, I literally haven’t had any problems with either machine. Both have been going for 1.5 years.

    I like the LMDE route for the DE already having pretty decent defaults and not requiring much tweaking from the get-go. Xfce (as it ships by default in Debian) absolutely works, but I end up spending an hour theming it and adding panel applets and rearranging everything so that it… ends up looking similar to Cinnamon anyway, because default Xfce looks horrible in my opinion