I took a look at the code and in lib/components/user.py I see that
self.preseed is called or rather set (my guess). preseed is defined in
FilteredCommand and calls self.db.set(name,value). I suspect the problem
lies here, but I do not know how to debug this further...
--
oem-prepare cannot cope
This bug was fixed in the package oem-config - 1.31
---
oem-config (1.31) hardy; urgency=low
[ Colin Watson ]
* Remove /etc/udev/rules.d/70-persistent-cd.rules and
/etc/udev/rules.d/70-persistent-net.rules in oem-config-prepare, in case
the system is going to be cloned.
As user-setup-ask is part of the user-setup package, which is included
in oem-config, where would a patch that enables creation of additional
users during oem-config-firstboot best reside? As patch of the scripts
included in oem-config, or directly in user-setup?
A patch could look like this for
Patching anything in oem-config is a definite no-no. It would have to go
directly into user-setup.
I'd like to think about this a little bit, but some kind of environment
variable override for is_system_user sounds reasonable. Rather than
checking it every time is_system_user is called, it should
The following patch adds a check for OEMCONFIGUSER in the is_system_user
function and will always return true if the variable is set.
** Attachment added: user-setup.functions.patch
http://launchpadlibrarian.net/12375026/user-setup.functions.patch
--
oem-prepare cannot cope if oem creates
This patch adds the OEMCONFIGUSER variable to the user setup script in
oem-config and will cause is_system_user to always return true, combined
with the patch above for user-setup.
** Attachment added: oem-config.user-setup-wrapper.patch
If a non system user already exists user-setup-ask does terminate
immediately. This is caused by is_system_user in functions.sh in
/usr/lib/oem-config/user
Overriding is_system_user like this will allow to generate a second user
during oem-config-firstboot:
# Workaround when there is a user
After some more debugging it seems to me that the user/user-setup-
wrapper script is causing the problem. It is called from
components/user.py as command of a filteredCommand object.
I run the script from the command line:
$ DEBUG_DEBCONF developer debconf
** Attachment added: user-setup-wrapper.nouser.log
http://launchpadlibrarian.net/12279403/user-setup-wrapper.nouser.log
--
oem-prepare cannot cope if oem creates user (?)
https://bugs.launchpad.net/bugs/153310
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Attachment added: user-setup-wrapper.user.log
http://launchpadlibrarian.net/12279430/user-setup-wrapper.user.log
--
oem-prepare cannot cope if oem creates user (?)
https://bugs.launchpad.net/bugs/153310
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Some more debugging information. If no non-system user exits,
frontend/gtk_ui.py blocks at gtk.main() and waits for the forward to be
pressed. If there is a user it continues right away to if self.backup
and starts running the scripts (*_apply in scripts directory).
These are the lines the above
I tried to isolate the problem in the below script, reusing
debconfcommunicator.py and debconffilter.py. Here's the result of a run
with debugging of debconf enabled. No user is added to the system,
though all debconf calls seem to succeed. Open question is if this
script will add any user at
I've run across this too. What I wanted was to set up every user's
desktop to be like the 'oem' model, but I also wanted another user
already installed by default. (In my particular case, I needed to have
yours truly be able to access the box for customer support issues, so I
wanted an
Confirming. When user is created during OEM-user session, it is not
possible to create another user during OEM end-user customization, the
script ends, and the system is only accessible with credentials of the
first user account.
--
oem-prepare cannot cope if oem creates user (?)
I have filed another bug about these events, regarding the poor error
handling. That other bug is bug 153311.
--
oem-prepare cannot cope if oem creates user (?)
https://bugs.launchpad.net/bugs/153310
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
** Tags added: iso-testing
--
oem-prepare cannot cope if oem creates user (?)
https://bugs.launchpad.net/bugs/153310
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Changed in: oem-config (Ubuntu)
Importance: Undecided = Medium
Status: New = Confirmed
--
oem-prepare cannot cope if oem creates user (?)
https://bugs.launchpad.net/bugs/153310
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
17 matches
Mail list logo
