-
Notifications
You must be signed in to change notification settings - Fork 23
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
New username feature breaks Mobile install #25
Comments
Thanks for the details; I'll look into this soon, yes. |
How is the user setup presently? I guess |
That's it exactly. The username (the original config option) was only
there to allow distributions to configure the user that would have their
password set on install. The user itself is created when the image is
created, not at install time.
To actually change the name of the user you'd need to do something like
this:
https://wiki.mobian.org/doku.php?id=tweaks&s[]=username#changing-the-default-username-from-mobian
(note this is an example and really isn't ready for use as-is)
|
I haven't tested #26, but it's where my mind's at currently about it |
Backport patches to fix a regression from the 1.3.0 release that cause the mobile installer to be stuck at the "new user" screen. Related: calamares/calamares-extensions#26 Related: calamares/calamares-extensions#25
On testing the new release while packing for Debian I noticed that the Mobile module now cannot get past the
User Password
screen. No matter whether the default username is left unchanged or replaced with a custom one the user cannot continue the install.The following log line is seen on pressing "continue":
Looking at the code, this is exactly what I'd expect.
calamares-extensions/modules/mobile/Config.h
Line 27 in 349acad
CONSTANT FINAL
, so attempting to write it from QML will always fail.setUsername( QString username )
function defined in https://github.com/calamares/calamares-extensions/blob/calamares/modules/mobile/Config.cppcalamares-extensions/modules/mobile/UsersJob.cpp
Line 52 in 349acad
UsersJob
would fail because the custom user does not exist on the system.@nmschulte: Sorry I couldn't review the PR at the time. Are you interested in taking on the last bit to get username changing working? Otherwise I'll probably propose a patch to disable the feature.
The text was updated successfully, but these errors were encountered: