• Holla@feddit.org
    17·
    1 hour ago

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

  • AlphaOmega@lemmy.worldEnglish
    2·
    16 minutes ago

    Windows 10 has had a bug for about 3 years now. Where if you choose “install update and shutdown” and instead it reboots.

  • JoeBigelow@lemmy.ca
    2·
    43 minutes ago

    Is there a “How to Linux” somewhere? I’d really like to get beyond using my CachyOS system as gui user, hell even some of the gui stuff is so alien. Felt like a lesser god when I found the repo… But terminal commands are just beyond me

    • BladeFederation@piefed.socialEnglish
      1·
      2 minutes ago

      Nothing wrong with GUI but yeah there are a lot of resources. I don’t know if I can point you to any because I usually just web search the command and add it to a ling running note of Linux commands

    • LandBasedDaveyJones@lemmy.today
      1·
      17 minutes ago

      Check out “Linux survival” if you’re old school, LabEx if you like experiential learning more, and less explanation. Both offer exercises, both are free, but Labex has a few restrictions for free accounts, and offers a paid tier at like 9 bucks a month. And ofc you don’t have to use the terminal irl, it’s just easier after getting used to it. Most things have a GUI program equivalent, you just have to seek it out. Most of the time.

      Edit: And also, Linux Mint and a few others are often recommended to new users for being both similarish to windows and approachable with GUI.

  • rumschlumpel@feddit.org
    1·
    34 minutes ago

    Big fan of hibernate (systemctl hibernate on systemd systems, and you need a swap file that’s at least as big as your RAM). Sure I wait some time until it’s shut down and booting takes longer, too, but not having to reopen all those terminal and editor windows I’m accumulating while working is worth it.

  • abominable_panda@lemmy.worldEnglish
    2·
    60 minutes 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
    2·
    2 hours 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
    2·
    2 hours ago

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

    • Kairos@lemmy.today
      15·
      5 hours ago

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

      • realitaetsverlust@piefed.zipEnglish
        5·
        4 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.orgEnglish
          4·
          3 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
        10·
        5 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.orgEnglish
          4·
          3 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
            1·
            3 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.orgEnglish
              1·
              2 hours 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
      6·
      4 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
      5·
      4 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