• GreenKnight23@lemmy.world
    link
    fedilink
    arrow-up
    2
    ·
    1 hour ago

    windows: installing updates, do not power off

    me: the fuck you are dismantles laptop and rips out battery

    Linux: shutdown now

  • AlsaValderaan@lemmy.blahaj.zone
    link
    fedilink
    arrow-up
    6
    ·
    6 hours ago

    On my work PC I disabled automatic restarts and I’ll just hibernate it for weeks at a time, keeping my work stuff open. Convenient, and I can install updates when I choose to.

  • Aganim@lemmy.world
    link
    fedilink
    arrow-up
    1
    arrow-down
    5
    ·
    edit-2
    4 hours ago

    Meanwhile:

    My W11 Pro PC: I’ll wait installing my monthly updates until you give me the okay. And I’ll wait for the reboot until you say so.

    My Manjaro laptop: sorry, I couldn’t build package X. Go f*ck yourself while I provide you with no information on how to fix this.

    *A manual build cache clear later*: all good! But now perform our weekly reboot.

    It’s horrible, but these days Windows updates actually give me less issues AND require less reboots than Manjaro. 😞

    • ZkhqrD5o@lemmy.world
      link
      fedilink
      arrow-up
      4
      ·
      2 hours ago

      If you want something easy, you can install one of the “Just Works” distros. Even though Manjaro advertises themself as beginner-friendly, they certainly are far from it.

      Debian and PopOS are both great choices.

    • enbipanic@lemmy.blahaj.zone
      link
      fedilink
      English
      arrow-up
      7
      arrow-down
      1
      ·
      4 hours ago

      The problem there is the word “Manjaro”

      Unfortunately while they market themselves as beginner friendly that’s simply not true

    • mrgoosmoos@lemmy.ca
      link
      fedilink
      English
      arrow-up
      5
      ·
      9 hours ago

      one of the reasons I’m moving away. pisses me off so much at work, I don’t even want it at home

  • lemmyknow@lemmy.today
    link
    fedilink
    arrow-up
    4
    ·
    11 hours ago

    One thing I’ve seen my computer do a few times: log me out, by itself. Some rare times I try and unlock back into my session, my current open and active user with my programs running, and instead I am greeted not by my desktop as it was when I locked the screen, but rather the lock screen as it was before I even logged in the first time around

  • Squiddork@lemmy.world
    link
    fedilink
    arrow-up
    25
    ·
    edit-2
    20 hours ago

    Managed to wreck my NVMe drive with an unsafe shutdown on linux the other week, gave it a few hours for the self check, booted back into the distro and has been running fine ever since.

    Pretty sure windows would’ve just set the computer on fire at this point.

    • LordAmplifier@pawb.social
      link
      fedilink
      English
      arrow-up
      4
      ·
      7 hours ago

      That’s weak. I always pull on the power cord until the plug comes out. That shuts it down in a second flat.

      • Avid Amoeba@lemmy.ca
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        2 hours ago

        I was talking about a laptop with non-removable battery of course! I turn off my desktop via Zigbee remote hooked to Home Assistant which flips a Zigbee power switch that the AC power cord is hooked up to. Even faster death than going under the desk and unplugging the power cord. Even just unplugging itself takes time.

    • ragas@lemmy.ml
      link
      fedilink
      arrow-up
      6
      ·
      12 hours ago

      “&&” will only run shutdown if the update runs correctly.

      I do “;” to definitely run the shutdown after the update process exits. (Don’t want to keep the system running if nothing is happening any more.)

    • baltakatei@sopuli.xyz
      link
      fedilink
      arrow-up
      5
      ·
      edit-2
      16 hours ago

      Assuming you enter your password upon running sudo, isn’t there the risk of sudo’s privilege timing out if pacman takes too long to complete? I believe I tried something similar, intending to run a one-liner I could start then walk away from. However, I ended up returning to see the system not rebooted hours later.

      Or is yes somehow supposed to take care of this? Sorry, newish Debian user here who hasn’t ventured outside the distribution much.

      • Matriks404@lemmy.world
        link
        fedilink
        arrow-up
        4
        ·
        edit-2
        10 hours ago

        The command after && runs only if the previous command returns non-error exit status (0), if pacman returns error the latter command won’t be executed.

        Additionally there’s probably a configuration option for sudo for it to not time out, but it doesn’t matter since you can just use systemctl reboot as a normal user to reboot your system (at least on Debian). If that’s too long I recommend to add this to your .bashrc (if you use Bash): alias reb='systemctl reboot' or something similar.

      • Successful_Try543@feddit.org
        link
        fedilink
        arrow-up
        4
        ·
        edit-2
        13 hours ago

        Yes, in this command one liner, the system should not power off when the update took too long.

        Or is yes somehow supposed to take care of this?

        No, yes is simply answering all questions asked during the update procedure (start upgrade, replace config files, restart services) with “yes”.

        • somerandomperson@lemmy.dbzer0.com
          link
          fedilink
          arrow-up
          3
          ·
          edit-2
          12 hours ago

          There’s no timeout for sudo. When permitted, a process runs as root and then closes.

          Also, the system will still shutdown when update fails because pipes do not care if previous commands exit with a nonzero code, unless pipefail is set.

          Edit: i’m blind.