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

Qubes Manager - VM testing repo enabled (new bugs) #3623

Closed
Simon-Davies opened this Issue Feb 22, 2018 · 4 comments

Comments

Projects
None yet
5 participants
@Simon-Davies

Simon-Davies commented Feb 22, 2018

Qubes OS version:

Qubes 4.0 R4.0

Affected TemplateVMs:

All


Steps to reproduce the behavior:

Enable VM testing repo
Update template
Shutdown template
Start template

First bug:

Click the stop VM button in Qubes Manager to shut down the template

Second bug:

Right click VM template - Kill qube

Third bug:

Right click VM template - Restart qube

Expected behavior:

Template shutsdown/is killed/restarts

Actual behavior:

First bug:

Whoops. A critical error has occurred. This is most likely a bug in Qubes Manager.

AssertionError:
at line 771
of file /usr/lib/python3.5/site-packages/qubesmanager/qubesmanager.py.

Second bug:

Whoops. A critical error has occurred. This is most likely a bug in Qubes Manager.

AssertionError:
at line 829
of file /usr/lib/python3.5/site-packages/qubesmanager/qubesmanager.py.

Third bug:

Whoops. A critical error has occurred. This is most likely a bug in Qubes Manager.

AssertionError:
at line 809
of file /usr/lib/python3.5/site-packages/qubesmanager/qubesmanager.py.

General notes:


Related issues:

@Simon-Davies Simon-Davies changed the title from Qubes Manager - VM testing repo enabled (new bug) to Qubes Manager - VM testing repo enabled (new bugs) Feb 22, 2018

@andrewdavidwong andrewdavidwong added this to the Release 4.0 milestone Feb 23, 2018

@lunarthegrey

This comment has been minimized.

Show comment
Hide comment
@lunarthegrey

lunarthegrey Feb 24, 2018

I'm not getting this in qubes-manager version 4.0.15-1.fc25

What version do you have?

I'm not getting this in qubes-manager version 4.0.15-1.fc25

What version do you have?

@Simon-Davies

This comment has been minimized.

Show comment
Hide comment
@Simon-Davies

Simon-Davies Feb 24, 2018

I've got the latest version from the dom0 current-testing repo. These bugs don't happen all the time but I experienced them yesterday

I've got the latest version from the dom0 current-testing repo. These bugs don't happen all the time but I experienced them yesterday

@qubesos-bot

This comment has been minimized.

Show comment
Hide comment
@qubesos-bot

qubesos-bot Mar 28, 2018

Automated announcement from builder-github

The package qubes-manager-4.0.17-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

Automated announcement from builder-github

The package qubes-manager-4.0.17-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 qubesos-bot referenced this issue in QubesOS/updates-status Mar 28, 2018

Closed

manager v4.0.17 (r4.0) #468

@qubesos-bot

This comment has been minimized.

Show comment
Hide comment
@qubesos-bot

qubesos-bot Apr 18, 2018

Automated announcement from builder-github

The package qubes-manager-4.0.17-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

Automated announcement from builder-github

The package qubes-manager-4.0.17-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

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