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

Deleting a VM with autostart enabled does not delete the autostart Symlink #1929

Closed
MarioGeckler opened this Issue Apr 22, 2016 · 4 comments

Comments

Projects
None yet
2 participants
@MarioGeckler

Qubes OS version:

R3.1

Expected behavior:

Deleting a AppVM with autostart enabled should delete the Symlink
/etc/systemd/system/multi-user.target.wants/qubes-vm@VMNAME.service

Actual behavior:

The Symlink isn't deleted so on each Boot Qubes tries to start a non existent VM and fails

Steps to reproduce the behavior:

Create a VM with autostart enabled and delete it. The Symlink for starting the VM is not deleted

General notes:


Related issues:

Relevant labels:

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Apr 22, 2016

Member

A side effect of this bug: if you create later a VM with the same name, it will have autostart enabled.

Member

marmarek commented Apr 22, 2016

A side effect of this bug: if you create later a VM with the same name, it will have autostart enabled.

@marmarek

This comment has been minimized.

Show comment
Hide comment

@marmarek marmarek closed this Apr 28, 2016

marmarek added a commit to QubesOS/qubes-core-admin that referenced this issue Jun 25, 2016

Fixed #1930: Delete autostart Symlink when deleting a VM
(cherry picked from commit d9b8516)
Notes from origin:
    Fixes QubesOS/qubes-issues#1929
@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Jun 25, 2016

Member

Automated announcement from builder-github

The package qubes-core-dom0-3.1.17-1.fc20 has been pushed to the r3.1 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

Member

marmarek commented Jun 25, 2016

Automated announcement from builder-github

The package qubes-core-dom0-3.1.17-1.fc20 has been pushed to the r3.1 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

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Jul 25, 2016

Member

Automated announcement from builder-github

The package qubes-core-dom0-3.1.17-1.fc20 has been pushed to the r3.1 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

Member

marmarek commented Jul 25, 2016

Automated announcement from builder-github

The package qubes-core-dom0-3.1.17-1.fc20 has been pushed to the r3.1 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

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