Transcript:

Two panel meme.

Top panel: Woman in the front seat of a car screaming at a child in the rear seat. She’s saying “Why can’t you just shutdown?”

Bottom panel: A child screaming “A stop job is running for Session c2 of user … (1:30 / no limit)”

    • [object Object]@lemmy.ca
      30·
      13 days ago

      Ughh recently had an amd graphics kernel bug which would lock up some /proc file somehow

      You’d go “why are fabs at max” type ps or top and they would freeze. System monitor would freeze.

      “Okay, I’ll just reboot, this is fucked”, and systemd is just there:

      Luckily it’s patched now. Hopefully those hard reboots didn’t damage anything.

      • Kairos@lemmy.today
        11·
        13 days ago

        Hard reboots don’t damage anything but the OS state, and even that has been protected against the last 2 decades.

          • Kairos@lemmy.today
            71·
            13 days ago

            Some computer components don’t protect against voltage loss and some OS components aren’t tolerant to sudden shutdown but we’re 99% the way there. Any of the two which don’t have protection at this point are complete garbage.

    • disorderly@lemmy.world
      25·
      13 days ago

      Why? You can bypass it immediately if it’s a one-off, or go update the unit configuration to have a short timeout if it’s a regular error.

      More likely though, it’s something that should actually be fixed, like a misconfigured fstab. Systemd is rarely the problem here.

          • rhpp@programming.dev
            2·
            12 days ago

            Unless the culprit is that one process permanently stuck in uninterruptible disk sleep, in which case the timer would just perpetually go up, and pressing 7x Ctrl-Alt-Del as you mentioned will simply shut down systemd and the kernel itself will start complaining (faulty hardware can cause this)

  • ThunderComplex@lemmy.today
    80·
    13 days ago

    Idk if this is a hot take but „no limit“ should straight up not exist. Just set a limit and blow the whole PC up when it takes too long.

    • cley_faye@lemmy.world
      8·
      12 days ago

      Due to what I call some quirks (but what other people call “good, sane, excellent design decisions”), you can set a hard timeout… that can be flatly ignored by systemd for various reasons that might or might not be obvious. In that case it will happily show you <current timer> / <timeout>, then move to <current timer> / <timeout * 2>, and so on.

      Because that, for some reasons, makes a lot of sense to some people that are not me.

    • thevoidzero@lemmy.world
      71·
      13 days ago

      I’ve never see it, who sets it? I only have two processes that are like it and blth wait for 1:30

  • nixukty@lemmy.zip
    322·
    13 days ago

    if my PC takes more than 15 seconds to shut down im flipping the power switch

  • TrackinDaKraken@lemmy.worldEnglish
    25·
    13 days ago

    I hope my installation of Mint doesn’t start acting up, because I don’t want to learn whatever it is half y’all are talking about.

    I just want it to work, and so far it has.

    The only problem I’ve had is nvidia driver updates breaking Blender. So, I need to restore and tell update to ignore that one.

    • Deebster@infosec.pub
      10·
      13 days ago

      Same, my shutdowns take about about two seconds, although suspend can sometimes take about six seconds (but normally one).

      I’m on Gentoo, so it’s probably a leaner install than most.

        • Deebster@infosec.pubEnglish
          9·
          12 days ago

          So I should wish for my computer to start acting up so I can have an educational experience attempting to fix it? No thanks, there’s less frustrating ways to learn.

          Also, if you’re trying to go for a greentext-style formatting, put two spaces at the end of your first line.

        • Deebster@infosec.pubEnglish
          1·
          11 days ago

          I’m still using shutdown -h now, even though the -h flag has been pointless for, what, 20 years?

          edit: looks like sysvinit’s shutdown still defaults to single-user mode, so I guess that muscle memory will still be useful if I ever use a Devuan or antiX box.

    • MintyFresh@lemmy.world
      1·
      12 days ago

      I’ve been using mint for years without learning a single thing about terminal command stuff. It just works. Granted I’m a pretty light user. Light gaming, high seas stuff.

    • jj4211@lemmy.world
      1·
      12 days ago

      Sometimes this just happens with systemd, it wants to manage every thing as a session and sometimes things running in the session don’t exit like systemd expects.

      Also, sometimes logging into a headless ssh session takes quite a while, because systemd is not super responsive to setting up the user session and ssh blocks waiting for that to happen.

    • reksas@sopuli.xyz
      1·
      11 days ago

      mine has started acting up quite badly,

      -from the start the internet has cut off randomly, likely due to driver issues or hardwareissue. Fixed only by complete restart. There seems to be no pattern, only that machine spirit gets angry if i use internet too much or sometimes just because i woke it up.

      -Sometimes when i start the pc it takes really long time to boot and just stays in black screen,

      -there are always kind of worrying error messages on startup and shutdown, something about rdseed being broken, something about data being lost, something about a thing hogging the processor and maybe switch to hq_unbound,

      -sometimes the pc just refuses to shutdown when shutdown and everything else goes offline but fans keep running.

      All of this has just slowly accumulated overtime, without me doing anything that should have caused it.

      Yet funnily enough, i’m STILL very much more satisfied than with windows that didnt have that much immidiate issues.

    • kalkulat@lemmy.worldEnglish
      1·
      11 days ago

      Got rid of Vista, installed Mint in 2012. Never a single regret. I am so good at Mint now, it’s hard to be humble.

  • cannedtuna@lemmy.worldEnglish
    274·
    13 days ago

    Transcript:

    Top: A woman in a parked car screaming at a child in the back seat

    Caption: Why can’t you just SHUTDOWN ?

    Bottom: a child buckled in the back seat screaming back

    Caption: ᵢₘgfₗᵢₚA.cSₒtₘop job is running for Session c2 of user … (1:30/no limit)

  • palordrolap@fedia.io
    21·
    13 days ago

    This actually got me to go track down the systemd service that has been responsible for being unresponsive and causing a 90-second shutdown delay way more often than it should.

    Do you really want technical details?

    In my case it’s the MPRIS service that’s supposed to provide playback control on media players and related software.

    … and so now it’s disabled to see what, if anything, breaks without it. So far, none of the media apps I regularly use seem to be affected (browsers, a computer emulator, DOSBox, VLC).

    It looks to be Bluetooth-associated based on the package it’s installed with, and I don’t need Bluetooth 99.9%+ of the time, so it might be a while, if ever, before I notice anything wrong.

      • palordrolap@fedia.io
        1·
        13 days ago

        What about it? I admit that I don’t know a great deal about systemd and all its subcommands - it took me a while to figure out how to disable that service properly, for example - but the manual seems to suggest that systemd-analyze is for startup processes, not shutdown.

        I’ll gladly take pointers on how to get it to say why a particular service hung on shutdown.

    • JTskulk@lemmy.worldEnglish
      2·
      13 days ago

      Recently I had to reboot to fix a zombie process (caused by a GPU crash, not sure if it was hardware or the driver). When shutting down systemd waited 2 minutes for all process to be killed and then another 2 minutes for the specific zombie process.

    • lost_faith@lemmy.ca
      14·
      13 days ago

      Used it a few times now, so much better than holding the power button.

      For users that are not aware: alt+print screen then one at a time with a few seconds inbetween press the keys above, switch the O for a B to reboot instead of shutting down

      • otacon239@lemmy.world
        19·
        13 days ago

        When I first used this trick, they sent me my black hoodie and green text projector in the mail as a prize.

      • OwOarchist@pawb.socialEnglish
        1·
        13 days ago

        This sounds a lot more difficult than just holding the power button for a few seconds. How is it better?

        (Though I guess it could be beneficial for some laptops that don’t have a traditional power button.)

        • volore@scribe.disroot.org
          7·
          12 days ago

          REISUB basically does the same thing but slightly more gracefully. It will still reboot through basically any lockup (I have yet to encounter one it didn’t work on), but it gives your machine the chance to settle some things before cutting the power.

          If a Linux machine locks up or freezes completely, use REISUB to restart it more gently than pushing the Power Button.

          Hold down Alt and the SysReq (Print Screen) keys, and then type R E I S U B, with 2-3 second delays between the key presses to give the commands a better chance to complete.

          R: Switch the keyboard from raw mode to XLATE mode
          E: Send the SIGTERM signal to all processes except init
          I: Send the SIGKILL signal to all processes except init
          S: Sync all mounted filesystems
          U: Remount all mounted filesystems in read-only mode
          B: Immediately reboot the system, without unmounting partitions or syncing

          source

          I suppose if you wanted to be extra quick and liked living dangerously you could just do alt + sysrq + R + B (I’m assuming switching the keyboard mode is necessary for getting the other commands to work during a complete lockup, but I could be wrong, you might only need B). But I wouldn’t recommend it, REISUB is plenty fast for me.

          There are other commands too, like alt + sysrq + F to summon the OOM killer.

          Lastly, and perhaps most critically, it also feels way cooler than just holding a single button. Comme ça:

  • AceFuzzLord@lemmy.zip
    8·
    13 days ago

    I am lucky enough to not have had any problems with calling a shutdown… just now with a problem I recently learned where my desktop treats shutdown as reboot. Definitely gotta look into that.

      • AceFuzzLord@lemmy.zip
        2·
        13 days ago

        I think I figured out my issue, literally a few minutes ago. I’ve never really dealt with ethernet, so I just learned my bios might have some sort of “wake up on lan” setting enabled that stops me from fully shutting down.

        Why would I ever want something like that, though?

        • Nailbar@sopuli.xyz
          5·
          13 days ago

          Why would I ever want something like that, though?

          I should look into wake on lan for my media center so I wouldn’t have to run downstairs to the living room to turn it on if I want to browse my photo/video collection.

          I prefer keeping it off when it’s not in use.

  • hirihit640@sh.itjust.worksEnglish
    6·
    12 days ago

    One of the reasons i like the new atomic/immutable distros is you can just power cycle with little worry of bricking your system, even if a system update is running.

  • rumba@lemmy.zipEnglish
    2·
    13 days ago

    I have less issues with that than i do shit getting slow at startup. I hunted down a PAM problem (that I didn’t even configure) for a couple of days of my spare time. 5 minutes startup, i could feel my hail/nails growing between power on and Graphical.