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)”

  • palordrolap@fedia.io
    15·
    14 hours 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·
        9 hours 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.