New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Appmenus from HVM- and other-than-fedora-based AppVMs populate System Tools menu #2277

Closed
rootkovska opened this Issue Aug 29, 2016 · 3 comments

Comments

Projects
None yet
5 participants
@rootkovska
Member

rootkovska commented Aug 29, 2016

No description provided.

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Aug 30, 2016

Member

Does it apply to VMs restored from backup? It should be fixed after you
update template of those VMs.

Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

Member

marmarek commented Aug 30, 2016

Does it apply to VMs restored from backup? It should be fixed after you
update template of those VMs.

Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

@mfc

This comment has been minimized.

Show comment
Hide comment
@mfc

mfc Sep 7, 2016

Member

Does it apply to VMs restored from backup?

yes, and ones that were not (like sys-firewall). seems like a quite arbitrary collection of apps with no clear pattern.

I can also confirm in my case that Appmenus for fedora 23-based AppVMs also populate the menu.

Member

mfc commented Sep 7, 2016

Does it apply to VMs restored from backup?

yes, and ones that were not (like sys-firewall). seems like a quite arbitrary collection of apps with no clear pattern.

I can also confirm in my case that Appmenus for fedora 23-based AppVMs also populate the menu.

@jpouellet

This comment has been minimized.

Show comment
Hide comment
@jpouellet

jpouellet Dec 10, 2016

Contributor

The root cause was fixed by QubesOS/qubes-core-admin-linux@7080c03

To fix existing VMs, perform:

Dom0$ for x in /var/lib/qubes/appvms/*/apps.templates/qubes-start.desktop; do \
>   cp -v /usr/share/qubes-appmenus/qubes-start.desktop "$x"; \
> done

and qvm-sync-appmenus (or add/remove a shortcut from the qubes-manager gui) for the affected VM(s).

I think this issue can be closed now.

Contributor

jpouellet commented Dec 10, 2016

The root cause was fixed by QubesOS/qubes-core-admin-linux@7080c03

To fix existing VMs, perform:

Dom0$ for x in /var/lib/qubes/appvms/*/apps.templates/qubes-start.desktop; do \
>   cp -v /usr/share/qubes-appmenus/qubes-start.desktop "$x"; \
> done

and qvm-sync-appmenus (or add/remove a shortcut from the qubes-manager gui) for the affected VM(s).

I think this issue can be closed now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment