[SOLVED] Computer no longer shuts down correctly - hangs on LM logo

[rateempty]

So everything was working fine but recently I went to shut down my PC and noticed it just hung on the LM logo and refused to shut down even after waiting an extended period of time.

I know this is a boot section of the forum and this seems to be the opposite of that but it seemed the best fit from what I could work out, especially as I found another topic (with no replies) on the same subject that was moved to this section.

Upon hitting esc or del it shows the following which prints again and again every other time esc/del is pressed (as one press takes to to this screen, the other to the LM logo).



It isn't related to the user directly as I can log out and log in again as another (brand new) user and this shows the same behaviour.

I found the following topic (viewtopic.php?t=353152) that seems to show the same behaviour but with no resolution (other than reinstalling entirely or suggestions to update a bios - neither of which seem appropriate here surely).

Everything is up to date (save the update to 20.3) from update manager.

I ran the command as suggested in that thread (journalctl -b -1 -r | grep -i "error\|warn\|fail"| tee >(gzip --stdout > journalctl_$USER.gz) and this is the output file:

Code: Select all

Jan 07 01:54:55 RE-Mint cinnamon-session[2253]: WARNING: t+20.78942s: Application 'cinnamon.desktop' killed by signal 15
Jan 07 01:54:55 RE-Mint cinnamon-session[2253]: WARNING: t+20.78940s: Application 'cinnamon-settings-daemon-screensaver-proxy.desktop' killed by signal 15
Jan 07 01:54:55 RE-Mint cinnamon-session[2253]: WARNING: t+20.78939s: Application 'cinnamon-settings-daemon-orientation.desktop' killed by signal 15
Jan 07 01:54:55 RE-Mint cinnamon-session[2253]: WARNING: t+20.78938s: Application 'cinnamon-settings-daemon-cursor.desktop' killed by signal 15
Jan 07 01:54:55 RE-Mint cinnamon-session[2253]: WARNING: t+20.78936s: Application 'cinnamon-settings-daemon-print-notifications.desktop' killed by signal 15
Jan 07 01:54:55 RE-Mint cinnamon-session[2253]: WARNING: t+20.78933s: Application 'cinnamon-settings-daemon-a11y-keyboard.desktop' killed by signal 15
Jan 07 01:54:55 RE-Mint dockerd[2753]: time="2022-01-07T01:54:55.322202975Z" level=info msg="stopping event stream following graceful shutdown" error="<nil>" module=libcontainerd namespace=moby
Jan 07 01:54:55 RE-Mint cinnamon-session[2253]: WARNING: t+20.78929s: Application 'cinnamon-settings-daemon-clipboard.desktop' killed by signal 15
Jan 07 01:54:55 RE-Mint cinnamon-session[2253]: WARNING: t+20.78268s: Application 'cinnamon-settings-daemon-xrandr.desktop' killed by signal 15
Jan 07 01:54:55 RE-Mint cinnamon-session[2253]: WARNING: t+20.78267s: Application 'cinnamon-settings-daemon-mouse.desktop' killed by signal 15
Jan 07 01:54:55 RE-Mint cinnamon-session[2253]: WARNING: t+20.78265s: Application 'cinnamon-settings-daemon-automount.desktop' killed by signal 15
Jan 07 01:54:55 RE-Mint cinnamon-session[2253]: WARNING: t+20.78264s: Application 'cinnamon-settings-daemon-wacom.desktop' killed by signal 15
Jan 07 01:54:55 RE-Mint cinnamon-session[2253]: WARNING: t+20.78255s: Application 'cinnamon-settings-daemon-keyboard.desktop' killed by signal 15
Jan 07 01:54:50 RE-Mint cinnamon-session[2253]: WARNING: t+15.52333s: Attempting to shutdown using systemd...
Jan 07 01:54:50 RE-Mint cinnamon-session[2253]: WARNING: t+15.52323s: Requesting system shutdown...
Jan 07 01:54:49 RE-Mint cinnamon-session[2253]: WARNING: t+14.59661s: Resuming logout sequence...
Jan 07 01:54:49 RE-Mint cinnamon-session[2253]: WARNING: t+14.59658s: Finished playing logout sound
Jan 07 01:54:49 RE-Mint cinnamon-session[2253]: WARNING: t+14.48437s: Playing logout sound '/usr/share/mint-artwork/sounds/logout.ogg'
Jan 07 01:54:46 RE-Mint cinnamon-session[2253]: WARNING: t+12.06622s: Detected that screensaver has left the bus
Jan 07 01:54:37 RE-Mint dockerd[2753]: time="2022-01-07T01:54:37.314944855Z" level=warning msg="Your kernel does not support cgroup blkio weight_device"
Jan 07 01:54:37 RE-Mint dockerd[2753]: time="2022-01-07T01:54:37.314937995Z" level=warning msg="Your kernel does not support cgroup blkio weight"
Jan 07 01:54:37 RE-Mint dockerd[2753]: time="2022-01-07T01:54:37.314928915Z" level=warning msg="Your kernel does not support CPU realtime scheduler"
Jan 07 01:54:37 RE-Mint dockerd[2753]: time="2022-01-07T01:54:37.314900505Z" level=warning msg="Your kernel does not support swap memory limit"
Jan 07 01:54:37 RE-Mint /hpfax[2885]: [2885]: error: Failed to create /var/spool/cups/tmp/.hplip
Jan 07 01:54:36 RE-Mint cinnamon-session[2253]: WARNING: t+2.06458s: Detected that screensaver has appeared on the bus
Jan 07 01:54:36 RE-Mint cinnamon-session[2253]: WARNING: t+1.47256s: Failed to start app: Unable to start application: Failed to execute child process “/usr/bin/nextcloud” (No such file or directory)
Jan 07 01:54:35 RE-Mint cinnamon-session[2253]: WARNING: t+1.42118s: Failed to start app: Unable to start application: Failed to execute child process “/tmp/.mount_LBRY_0njuavK/lbry” (No such file or directory)
Jan 07 01:54:35 RE-Mint kernel: #PF: error_code(0x0000) - not-present page
Jan 07 01:54:35 RE-Mint kernel: ccp 0000:2a:00.1: SEV: failed to get status. Error: 0x0
Jan 07 01:54:34 RE-Mint appimagelauncherd[2249]: WARNING: RDRND generated: 0xffffffff 0xffffffff 0xffffffff 0xffffffff
Jan 07 01:54:34 RE-Mint appimagelauncherd[2249]: WARNING: CPU random generator seem to be failing, disable hardware random number generation
Jan 07 01:54:34 RE-Mint systemd[2240]: Failed to start Dunst notification daemon.
Jan 07 01:54:34 RE-Mint systemd[2240]: dunst.service: Failed with result 'exit-code'.
Jan 07 01:54:34 RE-Mint systemd[2240]: dunst.service: Main process exited, code=exited, status=1/FAILURE
Jan 07 01:54:33 RE-Mint snapd[1709]: stateengine.go:149: state ensure error: Get https://api.snapcraft.io/api/v1/snaps/sections: dial tcp: lookup api.snapcraft.io: no such host
Jan 07 01:54:32 RE-Mint containerd[1803]: time="2022-01-07T01:54:32.874716899Z" level=warning msg="could not use snapshotter devmapper in metadata plugin" error="devmapper not configured"
Jan 07 01:54:32 RE-Mint containerd[1803]: time="2022-01-07T01:54:32.874690019Z" level=info msg="skip loading plugin \"io.containerd.snapshotter.v1.zfs\"..." error="path /var/lib/containerd/io.containerd.snapshotter.v1.zfs must be a zfs filesystem to be used with the zfs snapshotter: skip plugin" type=io.containerd.snapshotter.v1
Jan 07 01:54:32 RE-Mint containerd[1803]: time="2022-01-07T01:54:32.872749958Z" level=warning msg="failed to load plugin io.containerd.snapshotter.v1.devmapper" error="devmapper not configured"
Jan 07 01:54:32 RE-Mint containerd[1803]: time="2022-01-07T01:54:32.871993307Z" level=info msg="skip loading plugin \"io.containerd.snapshotter.v1.btrfs\"..." error="path /var/lib/containerd/io.containerd.snapshotter.v1.btrfs (ext4) must be a btrfs filesystem to be used with the btrfs snapshotter: skip plugin" type=io.containerd.snapshotter.v1
Jan 07 01:54:32 RE-Mint NetworkManager[1654]: <warn>  [1641520472.7722] sup-iface: failed to cancel p2p connect: P2P cancel failed
Jan 07 01:54:32 RE-Mint networkd-dispatcher[1894]: WARNING: systemd-networkd is not running, output will be incomplete.
Jan 07 01:54:32 RE-Mint colord[1786]: failed to get session [pid 1651]: No data available
Jan 07 01:54:32 RE-Mint udisksd[1722]: Failed to load the 'mdraid' libblockdev plugin
Jan 07 01:54:32 RE-Mint udisksd[1722]: failed to load module mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file or directory
Jan 07 01:54:32 RE-Mint systemd[1]: Finished GRUB failed boot detection.
Jan 07 01:54:32 RE-Mint systemd[1]: Starting GRUB failed boot detection...
Jan 07 01:54:31 RE-Mint kernel: thermal thermal_zone0: failed to read out thermal zone (-61)
Jan 07 01:54:30 RE-Mint lvm[531]:   /dev/sdg: open failed: No medium found
Jan 07 01:54:30 RE-Mint lvm[531]:   /dev/sdb: open failed: No medium found
Jan 07 01:54:30 RE-Mint lvm[531]:   /dev/sdg: open failed: No medium found
Jan 07 01:54:30 RE-Mint lvm[531]:   /dev/sdb: open failed: No medium found
Jan 07 01:54:30 RE-Mint blkmapd[553]: open pipe file /run/rpc_pipefs/nfs/blocklayout failed: No such file or directory
Jan 07 01:54:30 RE-Mint kernel: EXT4-fs (sde1): re-mounted. Opts: errors=remount-ro
Jan 07 01:54:30 RE-Mint kernel: RAS: Correctable Errors collector initialized.
Jan 07 01:54:30 RE-Mint kernel: pcieport 0000:00:03.1: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 6, DL_ActiveErr+
Jan 07 01:54:30 RE-Mint kernel: pcieport 0000:00:01.3: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 6, DL_ActiveErr+
Jan 07 01:54:30 RE-Mint kernel: tsc: Fast TSC calibration failed

Code: Select all

$ inxi -Fxxxrz
System:
  Kernel: 5.4.0-92-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 
  Desktop: Cinnamon 5.0.7 wm: muffin 5.0.2 dm: LightDM 1.30.0 
  Distro: Linux Mint 20.2 Uma base: Ubuntu 20.04 focal 
Machine:
  Type: Desktop Mobo: Micro-Star model: B450 GAMING PRO CARBON AC (MS-7B85) 
  v: 1.0 serial: <filter> UEFI [Legacy]: American Megatrends v: 1.70 
  date: 07/09/2019 
CPU:
  Topology: 6-Core model: AMD Ryzen 5 3600X bits: 64 type: MT MCP arch: Zen 
  L2 cache: 3072 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
  bogomips: 91203 
  Speed: 2199 MHz min/max: 2200/3800 MHz boost: enabled Core speeds (MHz): 
  1: 2200 2: 2200 3: 2200 4: 2195 5: 2199 6: 2197 7: 2200 8: 2198 9: 2199 
  10: 2200 11: 2200 12: 2200 
Graphics:
  Device-1: AMD Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] 
  driver: amdgpu v: kernel bus ID: 28:00.0 chip ID: 1002:731f 
  Display: x11 server: X.Org 1.20.13 driver: amdgpu,ati 
  unloaded: fbdev,modesetting,radeon,vesa 
  resolution: 3440x1440~75Hz, 1920x1080~60Hz 
  OpenGL: renderer: AMD Radeon RX 5700 XT (navi10 LLVM 13.0.0 DRM 3.35 
  5.4.0-92-generic) 
  v: 4.6 Mesa 22.0.0-devel (git-d57b10a 2022-01-06 focal-oibaf-ppa) 
  direct render: Yes 
Audio:
  Device-1: AMD Navi 10 HDMI Audio driver: snd_hda_intel v: kernel 
  bus ID: 28:00.1 chip ID: 1002:ab38 
  Device-2: AMD Starship/Matisse HD Audio vendor: Micro-Star MSI 
  driver: snd_hda_intel v: kernel bus ID: 2a:00.4 chip ID: 1022:1487 
  Device-3: Samson Meteor condenser microphone type: USB 
  driver: hid-generic,snd-usb-audio,usbhid bus ID: 3-1.1.1:8 
  chip ID: 17a0:0310 
  Sound Server: ALSA v: k5.4.0-92-generic 
Network:
  Device-1: Intel Wireless-AC 9260 driver: iwlwifi v: kernel bus ID: 21:00.0 
  chip ID: 8086:2526 
  IF: wlo1 state: down mac: <filter> 
  Device-2: Intel I211 Gigabit Network vendor: Micro-Star MSI driver: igb 
  v: 5.6.0-k port: f000 bus ID: 22:00.0 chip ID: 8086:1539 
  IF: enp34s0 state: up speed: 100 Mbps duplex: full mac: <filter> 
  IF-ID-1: docker0 state: down mac: <filter> 
  IF-ID-2: virbr0 state: down mac: <filter> 
  IF-ID-3: virbr0-nic state: down mac: <filter> 
Drives:
  Local Storage: total: 9.32 TiB used: 248.29 GiB (2.6%) 
  ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 1TB 
  size: 931.51 GiB speed: 31.6 Gb/s lanes: 4 serial: <filter> rev: 2B2QEXM7 
  scheme: GPT 
  ID-2: /dev/sda vendor: Samsung model: SSD 860 EVO 1TB size: 931.51 GiB 
  speed: 6.0 Gb/s serial: <filter> rev: 2B6Q scheme: GPT 
  ID-3: /dev/sdb vendor: Seagate model: ST4000DM004-2CV104 size: 3.64 TiB 
  speed: 6.0 Gb/s rotation: 5425 rpm serial: <filter> rev: 0001 scheme: GPT 
  ID-4: /dev/sdd vendor: Seagate model: ST2000DM001-1ER164 size: 1.82 TiB 
  speed: 6.0 Gb/s rotation: 7200 rpm serial: <filter> rev: CC25 scheme: GPT 
  ID-5: /dev/sde vendor: SanDisk model: SDSSDA240G size: 223.57 GiB 
  speed: 6.0 Gb/s serial: <filter> rev: 00RL scheme: MBR 
  ID-6: /dev/sdf vendor: Seagate model: ST2000DM001-1CH164 size: 1.82 TiB 
  speed: 6.0 Gb/s rotation: 7200 rpm serial: <filter> rev: CC24 scheme: MBR 
Partition:
  ID-1: / size: 219.06 GiB used: 156.01 GiB (71.2%) fs: ext4 dev: /dev/sde1 
Sensors:
  System Temperatures: cpu: 53.1 C mobo: N/A gpu: amdgpu temp: 54 C 
  Fan Speeds (RPM): N/A gpu: amdgpu fan: 1215 
Repos:
  No active apt repos in: /etc/apt/sources.list 
  Active apt repos in: /etc/apt/sources.list.d/additional-repositories.list 
  1: deb https://dl.winehq.org/wine-builds/ubuntu/ focal main
  Active apt repos in: /etc/apt/sources.list.d/appimagelauncher-team-stable-focal.list 
  1: deb http://ppa.launchpad.net/appimagelauncher-team/stable/ubuntu focal main
  Active apt repos in: /etc/apt/sources.list.d/atom.list 
  1: deb [arch=amd64] https://packagecloud.io/AtomEditor/atom/any/ any main
  Active apt repos in: /etc/apt/sources.list.d/docker.list 
  1: deb [arch=amd64 signed-by=/usr/share/keyrings/docker-archive-keyring.gpg] https://download.docker.com/linux/ubuntu focal stable
  Active apt repos in: /etc/apt/sources.list.d/fish-shell-release-3-focal.list 
  1: deb http://ppa.launchpad.net/fish-shell/release-3/ubuntu focal main
  Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 
  1: deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
  Active apt repos in: /etc/apt/sources.list.d/home:selmf.list 
  1: deb http://download.opensuse.org/repositories/home:/selmf/xUbuntu_20.04/ /
  Active apt repos in: /etc/apt/sources.list.d/lutris-team-lutris-focal.list 
  1: deb http://ppa.launchpad.net/lutris-team/lutris/ubuntu focal main
  Active apt repos in: /etc/apt/sources.list.d/nodesource.list 
  1: deb [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_14.x focal main
  2: deb-src [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_14.x focal main
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 
  1: deb http://packages.linuxmint.com uma main upstream import backport #id:linuxmint_main
  2: deb http://archive.ubuntu.com/ubuntu focal main restricted universe multiverse
  3: deb http://archive.ubuntu.com/ubuntu focal-updates main restricted universe multiverse
  4: deb http://archive.ubuntu.com/ubuntu focal-backports main restricted universe multiverse
  5: deb http://security.ubuntu.com/ubuntu/ focal-security main restricted universe multiverse
  6: deb http://archive.canonical.com/ubuntu/ focal partner
  Active apt repos in: /etc/apt/sources.list.d/oibaf-graphics-drivers-focal.list 
  1: deb http://ppa.launchpad.net/oibaf/graphics-drivers/ubuntu focal main
  Active apt repos in: /etc/apt/sources.list.d/openrct2-nightly-focal.list 
  1: deb http://ppa.launchpad.net/openrct2/nightly/ubuntu focal main
  No active apt repos in: /etc/apt/sources.list.d/pgdg.list 
  Active apt repos in: /etc/apt/sources.list.d/signal-xenial.list 
  1: deb [arch=amd64 signed-by=/usr/share/keyrings/signal-desktop-keyring.gpg] https://updates.signal.org/desktop/apt xenial main
  Active apt repos in: /etc/apt/sources.list.d/spotify.list 
  1: deb http://repository.spotify.com stable non-free
  Active apt repos in: /etc/apt/sources.list.d/vscode.list 
  1: deb [arch=amd64,arm64,armhf] http://packages.microsoft.com/repos/code stable main
Info:
  Processes: 423 Uptime: 10m Memory: 15.64 GiB used: 2.97 GiB (19.0%) 
  Init: systemd v: 245 runlevel: 5 Compilers: gcc: 9.3.0 alt: 7/9 
  Shell: bash v: 5.0.17 running in: gnome-terminal inxi: 3.0.38 

[all41]

So everything was working fine but recently I went to shut down my PC and noticed it just hung on the LM logo and refused to shut down even after waiting an extended period of time.

That's a decent system
How did you accomplish power down with a frozen os?
Have you tried booting in the advanced mode and selecting the last known working kernel?

[rateempty]

How did you accomplish power down with a frozen os?

It isn't entirely frozen - it still takes some kind of input (pressing keys makes the cursor blink reset and pressing esc/del toggles between the LM logo and the stuff in the screenshot (systemd/ctl?).
I have had to take the, err, less than elegant approach analogous to suffocating with a pillow - had to hold down the power button to kill it - not knowing if there is a way to interact with the system at that point beyond what I just mentioned.

Have you tried booting in the advanced mode and selecting the last known working kernel?

No because of two reasons 1) didn't know that was an option (I'm still fairly new to the more nitty gritty areas of linux, it has all been pretty smooth sailing until recently) and 2) no idea what the last known working kernel would be - is there any indication? It just gets updated whenever the update manager tells me to do so.

That's a decent system

Served me well so far, the case, PSU and most of the drives are from when it was first built in 2011, its technically the same PC that I built in 2011 just in a ship of thesus kind of way. LM exists on its own dedicated SSD and HDD alongside the existing Windows SSD and HDDs.

[all41]

Got that.
at the grub bootloader screen press the arrow buttons to select advanced mode,
You will see visuals on how to revert to an earlier kernel.
Try this first--report back with your findings.

[rateempty]

So I tried all the options (bar the recovery ones).
5.4.0-92/91/90 all failed to shutdown (same symptom) (92 being my current one)
5.0.0-32 failed to shutdown (same symptom)

4.15.0-58 and 4.15.0-54 both shut down although I had complaints about non hardware accelerated graphics and no second monitor.

[all41]

So I tried all the options (bar the recovery ones).
5.4.0-92/91/90 all failed to shutdown (same symptom) (92 being my current one)
5.0.0-32 failed to shutdown (same symptom)

4.15.0-58 and 4.15.0-54 both shut down although I had complaints about non hardware accelerated graphics and no second monitor.

Everything is up to date (save the update to 20.3) from update manager.

this sounds ambiguous--20.3 upgrade should not be an Update Manager option at this point.
And the 4.xx kernel--so this is an in-place upgrade--not a fresh 20.2 install?--correct me if wrong

[rateempty]

20.3 upgrade should not be an Update Manager option at this point.

It isn't in upgrade manager but it is in system reports but the bit in brackets was designed to belong the first first half of the statement rather than the last

And the 4.xx kernel--so this is an in-place upgrade--not a fresh 20.2 install?--correct me if wrong

Yes, I think this was on LM19 originally but that was a long time ago and well before I started seeing this problem which has manifested within about the last 2 weeks or so.

[motoryzen]

20.3 showed up in my LM 20.2 cinnamon update Manager as an upgrade option last night * shrugs*

[DB [NOT Cooper]]

I have the same problem in LM 19.3, especially when I have a partitioned USB drive mounted. FWIW, I posted a solution I found on another thread here today...just noticed yours.
viewtopic.php?f=46&t=364873

Hope this helps!

[rateempty]

I have the same problem in LM 19.3, especially when I have a partitioned USB drive mounted. FWIW, I posted a solution I found on another thread here today...just noticed yours.
viewtopic.php?f=46&t=364873

Hope this helps!

Thanks but I don't have any USB storage devices mounted, I did wonder if it was anything to do with the HDD I set up to automount as a second drive but it makes no difference when I unmount it before shutdown.

I've upgraded to 20.3 to see if that will help (it hasn't although it has removed a couple of lines from what I can see when I hit esc/del with the LM logo showing, it now only shows the plymouth power off screen, permit user sessions and acpi event daemon lines).

I also checked to make sure it wasn't to do with logging out, I logged out of my user first then shutdown from the logon screen and it still hangs.

[deepakdeshp]

Did you try

Code: Select all

init 0 

command to shut down?It worked for me.

[rateempty]

No, it just ends up in the same stuck state as shutdown from terminal or the gui.

[SMG]

There were enhancements for Ryzen 3000 series CPUs added to the kernel after 5.4 came out. You would need to upgrade to a newer kernel series to see if those might help.

Considering how many people with Ryzens are having issues with the 5.13 kernel, I would suggest trying the 5.14-oem kernel to see if it clears your issue. Install the latest 5.14-oem kernel with sudo apt install linux-oem-20.04d and reboot.

You might also want to see if there are any BIOS/UEFI updates available.

[lolomeis13]

Hi all

it works properly with Kernel
5.11.xx
5.13.0-22

[rateempty]

So I've managed to fix it, nothing to do with the kernel itself - or at least not the kernel and LM by itself...

The problem seems to have been qemu/libvirt/kvm. I removed all of them with synaptic and now my computer reboots normally.

For anyone who stumbles upon this in the future, this is how I ended up finding out the (sort of) solution:

I was messing around with a VM and was trying to start it from virt-manager but it wasn't connecting to the KVM. After some googling I found I had to restart libvirt. When I restarted libvirt then it was able to connect. Worth noting that at this point systemctl implied that the libvirt service was running just fine before the restart even though it clearly wasn't.

When I rebooted the computer that time and hit delete on the LM logo I noticed a very different shutdown pattern to the previous attempts where it would hang forever, this time it looked like it was shutting down more "normally" but was still waiting a very long time on "systemd-shutdown[1]: Waiting for process: qemu-system-x86" and, after about a minutes wait, the computer shut down.

This led me to start googling this and I found this post on the forum - viewtopic.php?t=329305 - which indicated that when that user stopped the libvirt daemon they saw the same behaviour I was seeing.

So as a test I booted then shutdown without using any applications, same issue as always.
Next time I rebooted and ran "sudo systemctl stop libvirtd" then shut down, the computer then shutdown after waiting ages on "waiting for process: qemu-system-x86".

So this clearly seemed to be related.

I wasn't really using qemu and virt manager for much so I just decided to nuke them from my system instead.
I went through synaptic and marked most of the libvirt and qemu packages for removal, synaptic then got completely stuck on "Removing libvirt-daemon-system (6.0.0-0ubuntu8.15) ..." and refused to do anything after 20 mins. Not even shutdown worked correctly (shutting down brought me to the login manager but then shutdown wasn't an option...).
So hard rebooted again, now synaptic was broken so that had to be fixed with "dpkg --configure -a".
This time I ran "sudo systemctl libvirtd stop" before removing the rest of the packages which worked fine.

Rebooted a couple of times and everything is back to normal.

Now to install virtualbox, I wanted to use virt-manager but I'm not going through that ordeal again...

[motoryzen]

This sounds like a small journey that would have been right up Wendell's alley ( from Level1Techs) xD Bless your heart hehe. Odd frustration to deal with

Happy to read you got it sorted . cheers.