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

Progress bar erratic immediately after first boot #3817

Open
trueriver opened this Issue Apr 13, 2018 · 1 comment

Comments

Projects
None yet
3 participants
@trueriver

Qubes OS version:

R4.0

Affected component(s):

The component that sets up and configures selected VMs on first boot


Steps to reproduce the behavior:

Follow usual install procedure on Asus laptop c Nov 2015. When asked which VMs to initialise, select Fedora 26, Debian 9, and all the sys-* options.

Either select the whonix VMs as well, or leave them out (same behaviour both ways)

Expected behavior:

When Qubes is initialising selected VMs, a progress bar shows a short bar osciallating to and fro. I expected this to continue moving throughout the process

Actual behavior:

The slider stopped moving after 2-3 minutes, even though the initialisation took another 10-20 mins to complete. The only evidence of progress was that the name of the VM occasionally changed

General notes:

This behaviour is potentially worrying to a newcomer who may assume the process has crashed.

Workaround is to tell users this may happen and encourage the to show patience if the GUI apparently freezes. Wait for the button to appear to complete initialisation.

NB: R3.2 worked fine on the same hardware, so this bug has been introduced in R4.0

If there will be any relevant logs please specify which files on whick VM(s) you would like to see

regards


Related issues:

@lunarthegrey

This comment has been minimized.

Show comment
Hide comment
@lunarthegrey

lunarthegrey Apr 13, 2018

I've experienced the same when installing the first 4.0 stable release.

I've experienced the same when installing the first 4.0 stable release.

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