Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upR4.0: User 'qubes' is allowed to be created during install but doesn't work. #3777
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
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).
|
In theory |
andrewdavidwong
added
bug
C: installer
labels
Apr 2, 2018
andrewdavidwong
added this to the Release 4.0 updates milestone
Apr 2, 2018
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
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.
btric-development
commented
Apr 3, 2018
|
Here you go. I ran through the install with a different username and confirmed it worked fine. Went back and tried First error occurs after reboot, after confirming default setup it says Attached are the contents of the |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
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
|
Oh, interesting line:
|
marmarek
closed this
in
marmarek/qubes-installer-qubes-os@017018b
Jul 3, 2018
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
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
qubesos-bot
commented
Jul 3, 2018
|
Automated announcement from builder-github The package
|
qubesos-bot
added
the
r4.0-dom0-cur-test
label
Jul 3, 2018
qubesos-bot
referenced this issue
in QubesOS/updates-status
Jul 3, 2018
Closed
installer-qubes-os v25.20.9-13-anaconda (r4.0) #570
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
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.
qubesos-bot
commented
Jul 23, 2018
|
Automated announcement from builder-github The package
Or update dom0 via Qubes Manager. |
btric-development commentedApr 2, 2018
Qubes OS version:
R4.0
Affected component(s):
Installation
Steps to reproduce the behavior:
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: