I accidentally saved the reboot image attachment before I completed the comment, so that's where it hangs. This time I only waited about a minute and a half before holding down control+alt+del to force the reboot, but I've walked away for an hour and let it sit, it does not finish beyond this point.
Strangely reboot and shutdown work but not systemctl reboot. Tried deleting tor to see if it was causing issues, got past thermald but still hung, see logs2. ** Attachment added: "systemctl reboot after removing tor." https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1928564/+attachment/5498330/+files/logs2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1928564 Title: systemctl reboot hangs the machine under hirsute 21.04 Status in systemd package in Ubuntu: Incomplete Bug description: If you type "systemctl reboot" instead of rebooting the machine hangs hard, nothing except a hard power cycle seems to get it's attention. This is true of both physical hardware and virtual machines, it was NOT a problem under groovy. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.3-3ubuntu3 Uname: Linux 5.12.4 x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Sat May 15 19:12:59 2021 InstallationDate: Installed on 2020-08-10 (278 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.12.4 root=UUID=1065426b-f156-4c90-a98b-e7258e07a88f ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: Upgraded to hirsute on 2021-05-12 (3 days ago) dmi.bios.date: 06/04/2020 dmi.bios.release: 16.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1602 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z390-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1602:bd06/04/2020:br16.2:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer mtime.conffile..etc.systemd.resolved.conf: 2020-12-17T10:04:04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1928564/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
