Reinstalling template is broken

[hyperfekt]

Qubes OS version:

R4.0rc5

Affected component(s):

qubes-dom0-update

---

Steps to reproduce the behavior:

As described in the documentation,
execute the command sudo qubes-dom0-update --action=reinstall qubes-template-[template name]

Expected behavior:

The template is reinstalled, only affecting the template's part of the application menu.
Afterwards, the template can be started and used normally.

Actual behavior:

The entire System Tools category as well as the Log Out menu, the Run Program dialog and the Create Qubes VM dialog are gone from the dom0 application menu, which instead displays No applications found.
Upon further inspection, all the .desktop files turn out to be missing.
Additionally, trying to start the template fails with VM directory does not exist: /var/lib/qubes/vm-templates/[template name].

General notes:

The application menu entries can be restored by reinstalling the relevant packages with sudo qubes-dom0-update --action=reinstall $(rpm -qa | grep 'qubes\|xfce4' | grep -v 'template\|kernel').

---

Related issues:

[tasket]

Current title and description = Duplicate of issue #3169

@hyperfekt - This could be rephrased more like original title to address the problem of erasing menu entries when a template-related operation fails.

[tasket]

Current title and description = Duplicate of issue #3169

@hyperfekt - This could be rephrased more like original title to address the problem of erasing menu entries when a template-related operation fails.

[andrewdavidwong]

This could be rephrased more like original title to address the problem of erasing menu entries when a template-related operation fails.

I think that should be taken care of #3169 too. Once reinstallation works correctly, erasing menu entries on failure shouldn't be an issue anymore, right?

[andrewdavidwong]

This could be rephrased more like original title to address the problem of erasing menu entries when a template-related operation fails.

I think that should be taken care of #3169 too. Once reinstallation works correctly, erasing menu entries on failure shouldn't be an issue anymore, right?

[andrewdavidwong]

Duplicate of #3169

[andrewdavidwong]

Duplicate of #3169

[andrewdavidwong]

This appears to be a duplicate of an existing issue. If you believe this is not really a duplicate, please leave a comment briefly explaining why. We'll be happy to take another look and, if appropriate, reopen this issue. Thank you.

[andrewdavidwong]

This appears to be a duplicate of an existing issue. If you believe this is not really a duplicate, please leave a comment briefly explaining why. We'll be happy to take another look and, if appropriate, reopen this issue. Thank you.

[tasket]

Once reinstallation works correctly, erasing menu entries on failure shouldn't be an issue anymore, right?

Issue #3169 triggers it, but underlying problem is #3294 where the rpm script doesn't work right. We should be able to get install errors without unrelated menus disappearing.

[tasket]

Once reinstallation works correctly, erasing menu entries on failure shouldn't be an issue anymore, right?

Issue #3169 triggers it, but underlying problem is #3294 where the rpm script doesn't work right. We should be able to get install errors without unrelated menus disappearing.

[hyperfekt]

I see. Sorry for the duplicate, as you can see it started out with the application menu which I didn't find an issue for and I didn't search again when I discovered it had failed completely. Thanks for the pointers!

[hyperfekt]

I see. Sorry for the duplicate, as you can see it started out with the application menu which I didn't find an issue for and I didn't search again when I discovered it had failed completely. Thanks for the pointers!