Your changes can’t hurt me!

  • mlg@lemmy.world
    link
    fedilink
    English
    arrow-up
    20
    ·
    2 days ago

    The Debian 6.12 kernel trying to find modules for your fancy new hardware:

  • Wispy2891@lemmy.world
    link
    fedilink
    arrow-up
    10
    ·
    2 days ago

    Just last week I updated the kernel in my arch laptop and now the touchpad doesn’t work anymore

    Luckily the solution was just pacman -S linux-lts

  • palordrolap@fedia.io
    link
    fedilink
    arrow-up
    64
    ·
    3 days ago

    Using a Debian is like being able to stay in bed in the morning. Heck, someone might even come by and change the sheets while you’re in REM and you’ll hardly even notice.

    Everyone else is up and running about like headless chickens fighting dependency wars and system vulnerabilities and cutting themselves on that bleeding edge and you’re hugging xteddy in blissful slumber.

    Speaking of which, has he been ported to Wayland?

    • msage@programming.dev
      link
      fedilink
      arrow-up
      3
      ·
      2 days ago

      I have been using Gentoo for over three years and I feel exactly the same.

      Updating the system after half a year when I didn’t have time to do it? Absolutely painless, everything works.

      And I get to quickly remove parts of software due to USE flags.

      Also, no releases, I just update, no changing sources, no full-upgrade… just the same command every time.

      There are binay packages for folks who don’t want to compile locally.

      Gentoo is the way.

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

      I have to switch over to debian some time. I sadly followed the many positive recommendations of Fedora and now my laptop crashes every time I wake it up from sleep.

  • ohshit604@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    11
    ·
    edit-2
    2 days ago

    Going into the Trixie update blind with no backups, first reboot was already a failure, wish me luck.

    Success! Only real issue was the nvidia-persistenced.service not starting preventing boot, running sudo apt purge *nvidia* and reinstalling resolves the issue.

  • mazzilius_marsti@lemmy.world
    link
    fedilink
    arrow-up
    16
    ·
    3 days ago

    true but only if you dont use the latest hardware. IMO, if you already have a computer then Debian is 100% crash proof, minus user errors. Using the latest computer spec on Debian is just a nightmare.

    • DefederateLemmyMl@feddit.nl
      link
      fedilink
      arrow-up
      5
      ·
      edit-2
      2 days ago

      The correct way with a new computer with recent hardware is to install Debian Testing to get a recent kernel, firmware and mesa and stuff, but put the code name of the next release into your apt config instead of “testing”. So then when the next version is released, you can just stay on that, now stable, version.

      Trixie just got released today though, so for the time being you can probably get away with using that.

      • pmk@lemmy.sdf.org
        link
        fedilink
        arrow-up
        1
        ·
        2 days ago

        Wouldn’t it be better to use backports? Testing doesn’t always get security updates if a package is problematic and can’t migrate from sid for a while.

        • DefederateLemmyMl@feddit.nl
          link
          fedilink
          arrow-up
          1
          ·
          2 days ago

          That’s another option, but it’s a bit more cumbersome having to cherrypick which exact backports you need for your specific hardware. Also, if you then for some reason don’t upgrade to the next stable release when it comes out, backports get abandoned after 1 year instead of the customary 3 years for the rest of the oldstable release.

          From my experience, running trixie/testing the past year or so on a minipc with hardware that was a bit too recent for bookworm, I can say that the cadence of security patches has been about the same between bookworm and testing.

          And let’s be honest, on a desktop system your main attack surface is going to be the software you go online with, i.e. the browser. So if you make sure that is kept up to date (flatpak, vendor repo, …) that already goes a long way.

    • Wispy2891@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      2 days ago

      Or proprietary shit

      Debian is the only distro that if installed on my iMac 2013 shows a black screen after installation

  • pelya@lemmy.world
    link
    fedilink
    arrow-up
    20
    arrow-down
    1
    ·
    3 days ago

    Time to download new Plasma bugs! I just hope it will decrease crashing frequency to once per week with Wayland backend, with Bookworm it was once per day, which is not fun if you need to keep several windows open.

    • Barbarian@sh.itjust.works
      link
      fedilink
      arrow-up
      18
      ·
      3 days ago

      I’m on Fedora with Plasma & Wayland, everything just works… Honestly not sure if Fedora is doing something special or all this talk of Plasma being crashy is overblown.

      • Shareni@programming.dev
        link
        fedilink
        arrow-up
        20
        ·
        3 days ago

        Plasma has a cycle of releasing a bunch of new features and changes, and then squashing bugs every week when they discover them.

        Debian is on a 2+ year release schedule, and the packages are frozen long before the release. So plasma might be either working fine, or be broken for 2+ years.

        Fedora is semi-stable because it’s on a 4 month schedule, and AFAIK they don’t rush upgrading to new major plasma versions, so plasma works a lot better.

        Generally from my experience, plasma works best on rolling distros, while it’s crap on stable ones. Stable DEs like xfce are incomparably better suited to stable distros.

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

        I haven’t had plasma crash on debian, fedora, or opensuse using wayland on three completely different, albeit older setups. It was completely unusable briefly on opensuse with an Nvidia card, but zero crashes that I can recall.

      • Damage@feddit.it
        link
        fedilink
        arrow-up
        3
        ·
        3 days ago

        Same, went to Bazzite after a decade on Fedora, it’s been YEARS since I’ve had any issue with Plasma

    • turdas@suppo.fi
      link
      fedilink
      arrow-up
      22
      arrow-down
      2
      ·
      3 days ago

      Using Plasma Wayland on Debian sounds like you’re deliberately setting yourself up for a lot of pain.

      • CoyoteFacts@piefed.ca
        link
        fedilink
        English
        arrow-up
        6
        ·
        3 days ago

        I’ve been using Plasma Wayland on Bookworm since Bookworm came out. Never had any issues. I’m using AMD GPU though.

    • stuner@lemmy.worldOP
      link
      fedilink
      arrow-up
      5
      ·
      3 days ago

      Plasma 6 is a significant upgrade for sure, especially on Wayland! I’d rate the crash frequency (on Fedora) at between once per week and once per month ;-)

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

      My work laptop has Kubuntu LTS, which is on Plasma 5.27 with X11, whereas I get to use the latest Plasma with Wayland on my personal laptop. Granted, I don’t do much gaming or such, but I definitely run into fewer bugs with the latter…

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

        Nope, plasma-session crash means all your windows are goooone.

        If it’s only plasma-desktop or kwin crash, you can generally restart it from a terminal, and you need one terminal window open at all times to do that, since you won’t be able to launch a new window with no desktop, or you try to launch it from the text console, which works badly because it won’t see your plasma-session environment.

        • cornshark@lemmy.world
          link
          fedilink
          arrow-up
          3
          ·
          edit-2
          3 days ago

          Kwin is now the Wayland compositor instead of just the window manager, so I’m pretty sure on Wayland if Kwin crashes, all your programs go with it

    • furry toaster@lemmy.blahaj.zone
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      2 days ago

      I had 0 crashes with plasma 5.27 on debian 12 and I used it for 1.5 years, I have been using unstable for 6 months with plasma and only 3 crashes of which plasma mamaged to recover gracefully on all of them, I genuinely dont know how people get Plasma to crash so much more often than I, and I have only used the wayland session

    • LH0ezVT@sh.itjust.works
      link
      fedilink
      arrow-up
      1
      ·
      3 days ago

      I’ve been on Debian Kde with X11 for this very reason, well, this and the lack of wacom support. But I heard upstream in Kde land, things are a lot better now, so I’m happy to try again. If not, well… see ya in 2 years or so.

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

    As someone who hosts multiple web servers with https let me just say SSL is the absolute worst, it doesn’t matter how you use it it just sucks getting set up

    • Possibly linux@lemmy.zip
      link
      fedilink
      English
      arrow-up
      3
      ·
      2 days ago

      *TLS

      You could just use a reverse proxy at the edge and Let’s encrypt certs. Caddy works with only a few lines of config.

    • Overspark@feddit.nl
      link
      fedilink
      arrow-up
      3
      ·
      2 days ago

      It’s pretty easy when you use the Caddy web/proxy server. Does everything automatically for you after initial setup.

    • dil@lemmy.zip
      link
      fedilink
      arrow-up
      1
      arrow-down
      1
      ·
      edit-2
      2 days ago

      Go the lazy way and use an open source panel, I like runtipi. There is also dokploy, caprover, cosmos cloud, casaos, coolify, yunohost (not docker), etc. all make that part easy