I’ve been using Qubes OS for 1 week and i’m having a problem shutting down my computer. I use the classic procedure of going to the taskbar menu and clicking on “shutdown”. The screen goes black with a white stripe at the bottom, but the PC continues to run. I have to keep pressing the on/off button on my computer for it to shutdown.
The TPM is a chip on your computer that helps protect against physical attacks. As I understand it, moving to 1.2 would require reflashing the firmware but I’m not 100% sure because I’ve never had to deal with this personally. Reflashing can be a dangerous process if you don’t know what you’re doing. If there’s a computer repair shop you trust nearby they might be able to help you.
But before going through all that trouble you can check your current TPM version by opening the Qubes menu, clicking on the gear icon (final icon in the left column) and opening “Qubes Global Config” from the “Qubes Tools” submenu (I tried to take a screenshot but pressing prtscr on my keyboard causes the menu to disappear ). Unde the “This Device” tab (near the bottom-left of the window) there will be a “Qubes OS Security Report” section where your TPM version will be listed.
I’ve already tweaked it but i didn’t take notes on what i did noob that i am.
I did find the menu you’re talking about in Qubes OS and the TPM field says : Device not found. Probably because the “Security Device Support” option in my bios is now set to “Disabled”.
I’ll have to investigate further to find out which option does what, and then maybe i’ll know if the problem really related to TPM.
It should show you the shutdown log and you can check where is it stuck at.
If you still won’t see the log then maybe you’ll have to remove rhgb quiet and add plymouth.enable=0 kernel command line options in GRUB to show the log.
I’ve tried pressing the Esc key but nothing happens.
I’ve managed to get some logs from dom0 juste after booting, but I don’t think there’s any information there that’s relevant to this problem. But i may be mistaking.
I’ll try to apply your changes in the Grub when I’ve figured out how to do it :-).
I imagine that the following line corresponds to the moment when I press the on/off button on my PC to turn it off.
oct. 21 23:27:02 dom0 systemd-logind[2739]: System is powering down.
But I’m not sure.
Set the kernel command line options and try to shutdown with them to see the shutdown log, maybe you’ll see the relevant log because after this line:
oct. 21 23:27:02 dom0 systemd-logind[2739]: System is powering down.
The log is not written to the disk anymore but you should be able to see it on the screen.
If a can trust Mistral AI, this line says that it’s all fine lol.
Edit : the computer finally stopped while I was copying and writing my reply…
I’m going to reset the grub conf file to its original state and run another test.
oct. 25 21:21:37 dom0 systemd[1]: lightdm.service: Triggering OnFailure= dependencies.
oct. 25 21:21:37 dom0 systemd[1]: Requested transaction contradicts existing jobs: Transaction for plymouth-quit.service/start is destructive (systemd-modules-load.service has ‘stop’ job queued, but ‘start’ is included in transaction).
oct. 25 21:21:37 dom0 systemd[1]: lightdm.service: Failed to enqueue OnFailure= job, ignoring: Transaction for plymouth-quit.service/start is destructive (systemd-modules-load.service has ‘stop’ job queued, but ‘start’ is included in transaction).
It seems i have some issues concerning Xorg who remains running and some dependencies.
Qubes os stops after 7min after requesting power-off.
Is this a log of the Qubes OS shutdown when you manually shutdown all qubes including sys-* qubes before shutting down the Qubes OS?
Because I see in the log the messages indicating that the sys-* qubes are still running:
Um, I don’t think I’d stopped the qubes manually there. I’m starting to get mixed up in what I’ve done. I’m starting from scratch log-wise.
I just stopped all qubes except :
Dom0
sys-usb because otherwise I lose the use of the mouse and keyboard.
Here are the logs:
Searching for the term “Entering failed mode”, we see on the previous line that there are only “sys-usb”
oct. 26 16:30:02 dom0 qrexec[20886]: qubes.WindowIconUpdater+: sys-usb → @adminvm: allowed to dom0
oct. 26 16:31:07 dom0 systemd[1]: lightdm.service: State ‘final-sigterm’ timed out. Killing.
oct. 26 16:31:07 dom0 systemd[1]: lightdm.service: Killing process 20627 (Xorg) with signal SIGKILL.
oct. 26 16:32:02 dom0 qrexec[21363]: qubes.WindowIconUpdater+: sys-usb → @adminvm: allowed to dom0
On a positive note, I’m learning to be more precise in my commands with: journalctl --since “2024-10-26 16:27:00” > logs_20241026.txt
If you think you need something more specific, don’t hesitate to ask. I’ll try to be less messy. I’ll have to make a cleaner post again, I’ve made a mess here.