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

R4.0: User 'qubes' is allowed to be created during install but doesn't work. #3777

Closed
btric-development opened this Issue Apr 2, 2018 · 5 comments

Comments

Projects
None yet
4 participants
@btric-development

Qubes OS version:

R4.0

Affected component(s):

Installation


Steps to reproduce the behavior:

  1. Install Qubes with defaults, specify the name of user to be created as 'qubes'.
  2. After first reboot, on Qubes OS option selection screen, selecting Done produces an error that a user is needed.
  3. After second reboot, at Qubes Login dialog, user 'qubes' plus the password you chose earlier cannot login.

Expected behavior:

Probably the best behavior is to prevent a user account called 'qubes' from being created. If there are any other reserved words that should be avoided, they should be added to a blacklist and not allowed as the username of the first user you install with.

Actual behavior:

Unsure. It does not appear to create a user, yet it allows me to pass that part of installation. Believe that it does create the user but is then overwritten with an internal 'qubes' user. That makes sense but I selected qubes to be the install user because I then create additional users for access to the secure information stored in our Qubes laptop.

General notes:

Thank you for such a great piece of software.


Related issues:

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Apr 2, 2018

Member

In theory qubes user should be perfectly fine user name. Only group qubes is reserved, but those facts may be related. Can you extract installation logs from /var/log/anaconda? If you can't log in, try using recovery mode of installation image (available in non-uefi mode).

Member

marmarek commented Apr 2, 2018

In theory qubes user should be perfectly fine user name. Only group qubes is reserved, but those facts may be related. Can you extract installation logs from /var/log/anaconda? If you can't log in, try using recovery mode of installation image (available in non-uefi mode).

@btric-development

This comment has been minimized.

Show comment
Hide comment
@btric-development

btric-development Apr 3, 2018

Here you go. I ran through the install with a different username and confirmed it worked fine. Went back and tried qubes again, and it failed the same way.

First error occurs after reboot, after confirming default setup it says [Dom0] Error: You must create a user account to create default VMs. Then I click OK to close that and it allows you to complete the initial setup phase, but it then boots into Qubes with "Other..." in the top of the login box and using username qubes with the password fails.

Attached are the contents of the /var/log/anaconda and /root folders, in case the /root/anaconda-ks.cfg file is helpful. Dummy password used for the reproduction so nothing has been redacted.

root-all.tar.gz
var-log-anaconda-all.tar.gz

Here you go. I ran through the install with a different username and confirmed it worked fine. Went back and tried qubes again, and it failed the same way.

First error occurs after reboot, after confirming default setup it says [Dom0] Error: You must create a user account to create default VMs. Then I click OK to close that and it allows you to complete the initial setup phase, but it then boots into Qubes with "Other..." in the top of the login box and using username qubes with the password fails.

Attached are the contents of the /var/log/anaconda and /root folders, in case the /root/anaconda-ks.cfg file is helpful. Dummy password used for the reproduction so nothing has been redacted.

root-all.tar.gz
var-log-anaconda-all.tar.gz

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Apr 3, 2018

Member

Oh, interesting line:

20:24:04,107 INFO anaconda: Creating users
20:24:04,108 INFO anaconda: user account root setup with no password
20:24:04,109 INFO anaconda: user account root locked
20:24:04,777 WARN anaconda: User qubes already exists
Member

marmarek commented Apr 3, 2018

Oh, interesting line:

20:24:04,107 INFO anaconda: Creating users
20:24:04,108 INFO anaconda: user account root setup with no password
20:24:04,109 INFO anaconda: user account root locked
20:24:04,777 WARN anaconda: User qubes already exists
@qubesos-bot

This comment has been minimized.

Show comment
Hide comment
@qubesos-bot

qubesos-bot Jul 3, 2018

Automated announcement from builder-github

The package pykickstart-2.32-4.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 pykickstart-2.32-4.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

This comment has been minimized.

Show comment
Hide comment
@qubesos-bot

qubesos-bot Jul 23, 2018

Automated announcement from builder-github

The package pykickstart-2.32-4.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 pykickstart-2.32-4.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