How do I fix qubesd.service

User Support
41

Thanks for asking. This process is a series of 2 steps forward, 1 step back :wink:

/etc/fedora-release
4.3.0 (R4.3)

I don’t think it’s reboot stable.

For reasons I don’t understand, I can access applications only in the sys-* AppVMs.
I can also create new AppVMs, but I cannot access any of the applications in the AppVMs (new or old).
As a result, I am unable to open a terminal to update any of the AppVMs.

OpenAI suggested updating from Dom0 with:

qvm-run --pass-io debian-12 – ‘sudo apt update && sudo apt full-upgrade -y && sudo apt autoremove -y && sudo apt clean && sudo apt install -y qubes-core-agent qubes-core-agent-networking qubes-core-agent-qrexec && sudo systemctl enable --now qubes-agent.service || true’

Unfortunately, after starting the AppVM, the Dom0 terminal hangs and nothing appears to be done in the AppVM.

Today’s challenge is to get the applications working in the AppVMs. Any and all suggestions are welcome :slight_smile:

42

Well, my opinion - do a restart - worst case you brick it again.
Just see what happens - maybe everything works maybe not.

Either way you win. Worst case only the insight what is breaking first.

1 Like
43

Great suggestion.
The computer ran through the start-up without any errors. Qubesd started.

Only issue was with sys-net, it failed because it was looking for the kernel that I forced deleted (it’s the kernel that should have been deleted in Step 3 of the upgrade). So it was an easy fix to assign it to the default kernel and everything is up and running.

I will now proceed with step 4 of the 4.3 upgrade.

A very big thank you to everyone who helped out.

I hope this helps anyone else who runs into this issue.

FYI - I will not be marking a post as the solution because no one post is the “solution”, it is a process as documented in the above posts.