/qubes-issues

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

Sys-net and firewall stay 'yellow' after bootup; No systray or notifications #1250

Closed
tasket opened this Issue Sep 29, 2015 · 5 comments

Comments

Assignees
No one assigned
Labels
Projects
None yet
Milestone
  Release 3.0 updates
2 participants
@tasket @marmarek
@tasket

tasket commented Sep 29, 2015

When booting into Qubes 3rc3 the initially started VMs (usually sys-net and sys-firewall) stay in a state that is disconnected from the UI. As a result, the user is blocked from the systray apps and status messages from these VMs.

It is conceivable that VMs which are chosen to start at boot time may attempt to present critical messages or functions for the user.

A workaround is to use 'Run command in VM' context menu function to manually run some program in each of the semi-disconnected VMs to bring them to the 'green' state.
@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Oct 5, 2015

Member

Do you have sys-firewall set as a default netvm? Or have you changed that default? By default login prompt is displayed only after default netvm (and its "parent" VMs) are fully operational.
Member

marmarek commented Oct 5, 2015

Do you have sys-firewall set as a default netvm? Or have you changed that default? By default login prompt is displayed only after default netvm (and its "parent" VMs) are fully operational.

@marmarek marmarek added bug C: core P: minor labels Oct 5, 2015

@marmarek marmarek modified the milestones: Release 3.0, Release 3.0 updates Oct 5, 2015

@marmarek marmarek closed this in marmarek/old-qubes-core-admin@a30e8d1 Dec 26, 2015

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Dec 26, 2015

Member

Automated announcement from builder-github

The package qubes-core-dom0-3.1.8-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 Dec 26, 2015

Automated announcement from builder-github

The package qubes-core-dom0-3.1.8-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 marmarek added the r3.1-dom0-cur-test label Dec 26, 2015

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Jan 12, 2016

Member

Automated announcement from builder-github

The package qubes-core-dom0-3.1.10-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 Jan 12, 2016

Automated announcement from builder-github

The package qubes-core-dom0-3.1.10-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

@marmarek marmarek added r3.1-dom0-stable and removed r3.1-dom0-cur-test labels Jan 12, 2016

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

@marmarek
systemd: fix starting VMs _before_ allowing user login 
systemd-user-sessions.service is specicically for that, do not use hack
(plymouth-quit.service), which doesn't work when the service is
disabled.

Fixes QubesOS/qubes-issues#1250

(cherry picked from commit a30e8d1)
Verified
This commit was signed with a verified signature.
@marmarek marmarek Marek Marczykowski-Górecki
GPG key ID: 063938BA42CFA724 Learn about signing commits
1d8dd0c
@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Jan 15, 2016

Member

Automated announcement from builder-github

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

marmarek commented Jan 15, 2016

Automated announcement from builder-github

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

@marmarek marmarek added the r3.0-dom0-testing label Jan 15, 2016

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 13, 2016

Member

Automated announcement from builder-github

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

marmarek commented Mar 13, 2016

Automated announcement from builder-github

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

@marmarek marmarek added r3.0-dom0-stable and removed r3.0-dom0-testing labels Mar 13, 2016

@pugege pugege referenced this issue Jun 29, 2016

Closed

sys-usb, sysfirewall and others stay 'yellow' after bootup and manual startup #2128

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