• Holla@feddit.org
    link
    fedilink
    arrow-up
    6
    ·
    22 minutes ago

    [**    ] A stop job is running for Session c1 of User gdm (49s / 1min 30s)

  • abominable_panda@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    16 seconds ago

    Last time this happened to me (read: yesterday) i ended up holding down the power button.

    You dont want to shut down when i ask i will make you.

  • OR3X@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    34 minutes ago

    This might sound crazy, but you don’t have to shutdown your computer every time you’re done using it. You can just lock the screen and walk away.

  • myszka@lemmy.ml
    link
    fedilink
    arrow-up
    1
    ·
    38 minutes ago

    I don’t know how but a windows 7 machine I’ve recently had to use still got an update before shutting down…

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

    I usually map the power button to shut down, although on laptop if I close the screen after shutdown it’ll go to sleep mid shutdown

    • Kairos@lemmy.today
      link
      fedilink
      arrow-up
      15
      ·
      4 hours ago

      (X time / 1:30) but the second time will be extended indefinitely for some fucking reason.

      • realitaetsverlust@piefed.zip
        link
        fedilink
        English
        arrow-up
        4
        ·
        3 hours ago

        I think that depends on the setting, I had situations where one of my docker containers took ages to shutdown and it would just say 00/02 00s but when it reached that limit, it would just go up.

        • TwilightKiddy@scribe.disroot.org
          link
          fedilink
          English
          arrow-up
          3
          ·
          2 hours ago

          Individual services can override the default 90 seconds timeout. But then you can override their override if you think you are smarter, of course.

      • Thorry@feddit.org
        link
        fedilink
        arrow-up
        9
        ·
        4 hours ago

        Well you say that, but I’ve seen the countdown go past and then reset to a higher number often.

        • TwilightKiddy@scribe.disroot.org
          link
          fedilink
          English
          arrow-up
          3
          ·
          edit-2
          2 hours ago

          I entrust you with this horror, go figure out what to blame.

          shutdown-analyze.sh
          #! /usr/bin/env bash
          shutdown_start=$(journalctl -b -1 -u systemd-logind --grep="System is (powering down|rebooting)" --output=cat --no-pager --output-fields=_SOURCE_REALTIME_TIMESTAMP)
          shutdown_start=$((shutdown_start / 1000000))
          units=$(journalctl -b -1 --since=@$shutdown_start --output=cat --no-pager --output-fields=UNIT JOB_TYPE=stop CODE_FUNC=job_emit_start_message)
          
          for u in $units; do
              stopping_start=$(journalctl -b -1 --since=@$shutdown_start -u "$u" --output=cat --no-pager --output-fields=_SOURCE_REALTIME_TIMESTAMP JOB_TYPE=stop CODE_FUNC=job_emit_start_message _SYSTEMD_UNIT=init.scope)
              stopping_end=$(journalctl -b -1 --since=@$shutdown_start -u "$u" --output=cat --no-pager --output-fields=_SOURCE_REALTIME_TIMESTAMP JOB_TYPE=stop CODE_FUNC=job_emit_done_message _SYSTEMD_UNIT=init.scope)
              duration_human=$(systemd-analyze timespan $((stopping_end - stopping_start))us | tail -1 | sed 's/.*: //')
              printf "%s\t%10s %s\n" $((stopping_end - stopping_start)) "$duration_human" "$u"
          done | sort -rn | cut -f 2
          
          • Thorry@feddit.org
            link
            fedilink
            arrow-up
            1
            ·
            2 hours ago

            Thanks, I usually know what it is tho. Most often it’s VMs I was using for testing stuff, which I forgot to shutdown. It takes a while for them to cleanly shutdown, which is what the wait is for. I have a shortcut on my desktop to a script that checks for any running VMs still and shuts them down. But I forget to click it sometimes and then I have to wait. No big deal, except I like to switch off the power bar that powers the computer and everything attached to it. An old habit from when such a thing mattered, these days standby power is probably nothing to worry about. But still I wait patiently for the computer to shut down till I switch off the power strip.

            • TwilightKiddy@scribe.disroot.org
              link
              fedilink
              English
              arrow-up
              1
              ·
              37 minutes ago

              If your script somehow shuts them down faster than plain old SIGTERM, putting it under /usr/lib/systemd/system-shutdown/ might be a good idea. Check man 8 systemd-shutdown for more info on that.

    • RustyNova@lemmy.world
      link
      fedilink
      arrow-up
      5
      ·
      3 hours ago

      My always plugged in HDD with bees on it does that. 1 minute to shutdown at least because there’s always some kind of extend read or dedupe that need a sync.

      … I brought this upon myself so I don’t have to complain.

    • anon5621@lemmy.ml
      link
      fedilink
      arrow-up
      4
      ·
      3 hours ago

      Yes but no, u can in config file of systemd change timeout to 5,10 second or other number of seconds which u wish before it will kill it

  • HM King Charles III DG FD@feddit.uk
    link
    fedilink
    English
    arrow-up
    8
    ·
    3 hours ago

    Everyone arguing about the amount of keypresses to type a shutdown command and time it takes to shutdown… I just power it off at the wall. One button press, shutdown is near instantaneous