Launching application from menu in a AppVM do not work

[pdinoto]

Qubes OS version:

R4.0

Affected component(s):

dom0 GUI

---

Steps to reproduce the behavior:

Restore a R3.2 AppVM qube into a stock R4.0 system, and then select any of the AppVM applications on the Xfce menu (except for " Qube Settings" menu item, obviously)

Expected behavior:

The AppVM is started if it was not already running. Once the AppVM has booted the requested application is launched in that qube.

Actual behavior:

The AppVM is launched if it was not already running, but then nothing happens.
If the AppVM was running, nothing happens.

General notes:

The same application can be launched by using dom0 command line, like:

dom0$ qvm-run <appvm-qube-name> <application>

It does not seem related to the type of launched application.
Only common denominator is that this happens on restored from backup qubes.
ServiceVMs applications launch fine.
Application from newly created qubes also launch fine.

Editing the AppVM exposed applications on the Qube Settings dialog, "Application" tab does not fix the issue.

---

Related issues:

[marmarek]

Is is TemplateBasedVM or StandaloneVM? Is is on template also restored, or fresh one from Qubes 4.0? Is the template version the same as was on R3.2?

[marmarek]

Is is TemplateBasedVM or StandaloneVM? Is is on template also restored, or fresh one from Qubes 4.0? Is the template version the same as was on R3.2?

[pdinoto]

All the affected AppVM are TemplateBasedVM, and the template was also restored from a R3.2 backup.

Based on you questions, I did some more tests:

• Created a new qube, based on a stock debian-9 R4.0 template
• Created a new qube, based on a stock fedora-26 R4.0 template
  and the issue also happens on the debian-9 template. The menu launching on the fedora-26 template works fine.

This means the restored nature of the qube may be unrelated. I just happen to have all my AppVMs based on debian-9 templates (stock, or derived from it).

Please note that when I launch "Terminal" from a newly created, debian-9-based template, I can briefly see some flicker on the Xfce Workspace switcher, as if the application window would be actually opened and closed so fast it is not visible.

Any ideas how to troubleshoot this?

[pdinoto]

All the affected AppVM are TemplateBasedVM, and the template was also restored from a R3.2 backup.

Based on you questions, I did some more tests:

• Created a new qube, based on a stock debian-9 R4.0 template
• Created a new qube, based on a stock fedora-26 R4.0 template
  and the issue also happens on the debian-9 template. The menu launching on the fedora-26 template works fine.

This means the restored nature of the qube may be unrelated. I just happen to have all my AppVMs based on debian-9 templates (stock, or derived from it).

Please note that when I launch "Terminal" from a newly created, debian-9-based template, I can briefly see some flicker on the Xfce Workspace switcher, as if the application window would be actually opened and closed so fast it is not visible.

Any ideas how to troubleshoot this?

[pdinoto]

Well, it seems that this issue was solved by an update in qubes-* debian packages in the debian-9 template.

Also, the templates I migrated started to work properly when the qubes repository on them was changed to .../r4.0/..., which I did not realize until now 🤦‍♂️

Unless this happens to others, I think we should close this issue.

[pdinoto]

Well, it seems that this issue was solved by an update in qubes-* debian packages in the debian-9 template.

Also, the templates I migrated started to work properly when the qubes repository on them was changed to .../r4.0/..., which I did not realize until now 🤦‍♂️

Unless this happens to others, I think we should close this issue.

[andrewdavidwong]

Closing this as "resolved." If you believe the issue is not yet resolved, or if anyone is still affected by this issue, please leave a comment, and we'll be happy to reopen this. Thank you.

[andrewdavidwong]

Closing this as "resolved." If you believe the issue is not yet resolved, or if anyone is still affected by this issue, please leave a comment, and we'll be happy to reopen this. Thank you.