Application missing on freshly installed Qubes OS 4.1.2

PrinceXaahid · March 15, 2023, 5:41pm

Just installed a fresh copy of Qubes OS 4.1.2.

Facing following problems:

Application missing in templates.
Unable to open application from others’ Qubes (Personal, Vault, Untrusted, Fedora and Debian)

PrinceXaahid · March 15, 2023, 5:44pm

Can’t do a thing…!

ephile · March 15, 2023, 7:27pm

The refresh button under Qubes Settings > Applications should reset these for you. If the button is still greyed out for some reason, try:

qvm-scan-appmenus <vmname>

You can find more information in the Qubes documentation:

qubes_noob · June 26, 2024, 7:01pm

I am having the same issue. Did you figure out how to solve it?

apparatus · June 26, 2024, 7:14pm

Did you try @ephile’s suggestion?

qubes_noob · June 27, 2024, 9:45pm

I tried qvm-sync-appmenus sys-usb. I get the error “Appmenus can be retrieved only from running VM.”

When I try to start sys-usb, I get the error: "has failed to start internal error: libxenlight has filed to create new domain ‘sys-usb’, see /var/log/libvirt/libxl/libxl-driver.log for details’

When I open that file, I these lines (among others):
libxl: libxl_dm.c:2857:stubdom_xswait_cb:domain 5:Stubdom 6 for 5 startup: startup timed out.
libxl_create.c:1975:domcreate_devmodel_started: Domain 5:device model did not start: -9

I should note that I ripped the wifi card out of my laptop because I want to use this as an air-gapped computer.

I should also note that NONE of the Qubes are usable except for Dom0.

apparatus · June 28, 2024, 3:48am

Maybe you had some issue during installation.
Reinstalling Qubes OS helped in similar case:

github.com/QubesOS/qubes-issues

Some error during install results in no Qubes/VMs starting when type is HVM

opened 04:36PM - 02 Jun 24 UTC

closed 11:32PM - 02 Jun 24 UTC

docelic

T: bug P: default R: self-closed

(The issue is *not* related to Intel 13th gen; but text is preserved just for re…ference. The issue ended up being something wrong during install; a reinstallation helped.) ### Qubes OS release 4.2.1 ### Brief summary After clean installation of Qubes 4.2.1 on Intel i9 13th gen, HVM qubes (including `sys-net`) fail to start with: ``` libxl: libxl_dm.c:2857:stubdom_xswait_cb: Domain 15:Stubdom 16 for 15 startup: startup timed out libxl: libxl_create.c:1975:domcreate_devmodel_started: Domain 15:device model did not start: -9 ``` This must be related to software because I did have some earlier version of Qubes running fine on this same machine as well as on Intel NUC 13th gen. It happens on HVM-type qubes; other work fine. Also it is not related to PCI; for test I removed all assigned devices from a HVM qube before attempting to start it. An error similar/identical to this has already been reported in https://github.com/QubesOS/qubes-issues/issues/9150, but according to authoritative comment on it, that bug was related to (old) AMD processors and is not related to Intel. ### Steps to reproduce 1. Install Qubes 4.2.1 on 13th gen Intel i9-13980HX (possibly others). (Issue #9150 also mentions Intel NUC 13th gen) 2. Install will succeed and machine will reboot to finish installing templates etc. 3. The error about `sys-net` qube will show up 4. Same error happens on automatic start as well as on manual attempts ### Expected behavior 1. `sys-net` and any other HVM qubes to start normally 2. Other qubes depending on them to start normally ### Actual behavior 1. HVM qubes cannot start 2. Dependent qubes cannot start ### Other info Seems at least partially related problem was also reported in https://forum.qubes-os.org/t/no-qubes-vms-boot-after-latest-updates/26033 Thanks.

Try to install Qubes OS 4.2.2-rc1. Maybe you can also install it with kernel-latest option so you can test the latest kernel if the issue persists with stable kernel after reinstall.