4.0rc1 default dvm removal causes many issues

[3hhh]

Qubes OS version (e.g., R3.2):

4.0rc1

Steps to reproduce the behavior:

1. Start a dispVM from the default dvm template.
2. Use qvm-remove to delete the default dvm (see qubes-prefs)
3. Check the output of qvm-ls, qubes-prefs, qvm-prefs, ... They will all show some strange Python error messages which are not helpful at all. Apparently they all expect a dispvm to exist which isn't there anymore

Expected behavior:

Either qvm-remove should check that it's not deleting anything essential or qvm-ls & Co should have some fallback mechanism (qvm-ls could e.g. show that the template doesn't exist anymore).

[qubesos-bot]

Automated announcement from builder-github

The package qubes-core-dom0-4.0.8-1.fc25 has been pushed to the r4.0 testing repository for dom0.
To test this update, please install it with the following command:

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing

Changes included in this update

[qubesos-bot]

Automated announcement from builder-github

The package qubes-core-dom0-4.0.8-1.fc25 has been pushed to the r4.0 testing repository for dom0.
To test this update, please install it with the following command:

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing

Changes included in this update

[qubesos-bot]

Automated announcement from builder-github

The package qubes-core-dom0-4.0.11-1.fc25 has been pushed to the r4.0 stable repository for dom0.
To install this update, please use the standard update command:

sudo qubes-dom0-update

Or update dom0 via Qubes Manager.

Changes included in this update

[qubesos-bot]

Automated announcement from builder-github

The package qubes-core-dom0-4.0.11-1.fc25 has been pushed to the r4.0 stable repository for dom0.
To install this update, please use the standard update command:

sudo qubes-dom0-update

Or update dom0 via Qubes Manager.

Changes included in this update