Can't launch inside dispvm instances in new app menu

[gust]

The announcement for the new application menu (which is very nice) stated:

In order to make the use of disposable qubes more conveniently, now programs can be started in a running disposable qube from the menu. It works just like any other qube. There’s only one limitation: If the qube was started for a program (which is usually the case), it will shut down when that first program is closed.

This sounds like a great feature because I use dispvms a ton and have long wished for this.

But when I select a running dispvm instance in the new app menu, it does not show any available applications at all. For example I have one called “dvm-web” where I do most of my web browsing. The dvm-web menu contains firefox, files, terminal. But when I select a dispXXX menu for an instance based on dvm-web, it shows nothing in the app section (network indicator still there, Settings, Shut down Qube, pause Qube). (I could understand if Firefox was hidden, as this is open, but the other two will not show. And the same for dvms with additional apps in the menu.)

Maybe I misunderstand this feature, or it is work-in-progress / forthcoming? Thanks for any guidance.

[marmarek]

It should work already. Does the issue apply to all dispvm instances, or only those started from dvm-web?

[gust]

I have the same issue with the two others I tested (just reconfirmed). For example, dvm-media has various (~5) tools for ripping / encoding media in its app list, but there are no items shown in the instance app list, same for another called dvm-print which has Firefox, LibreWriter, Files, Terminal in app list.

I would send a screenshot but can’t seem to screenshot the menu (disappears when I press the keys).

[enmus]

I missed announcement about this great feature. I’m running Qubes 4.1 updated to stable since early 4.1 betas, but I don’t even have dispxxx entries in the new or any other app menu when started and running?

So, I still use Qube Manager → Run command in qube (dispxxx) to start additional programs inside the same disposable qube. Although, running multiple programs inside single qube isn’t the best security treat…

[gust]

The new app menu is in testing and must be installed separately:

New Qubes application menu

The new application menu is here! If you are running a release candidate of Qubes OS 4.1 and wish to just dive on in, the new app menu can be found here. But first, a couple important caveats: This new menu requires 4.1 and cannot run on 4.0. This is experimental software for testing purposes only! Still want to give it a go? To install, enter this command in a dom0 terminal: sudo qubes-dom0-update --enablerepo=qubes-dom0-unstable qubes-desktop-linux-menu Once installed, add the ne…

Although it is referred to in that post as the “new Qubes application menu,” I should perhaps call it the “experimental application menu” for clarity

[GWeck]

For me, the new menu of the dispvm shows just those entries defined for the correspondig dispvm template. I always start the menu with the qualifier --restart - maybe that helps?

[gust]

I did try adding --restart (along with --page=1 , an option I just discovered) but did not help, still have a blank menu on the instances. Curious that it works for some folks. I wonder if I’m missing some install.

[enmus]

This helps definitely. Thanks! The only drawback is that the menu will not refresh itself upon dispVM shutdown, or starting new one meanwhile, so this has to be executed whenever new dispVM opens/shuts down.