oem-config-firstboot runs on every reboot
Bug #432180 reported by
U Das
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| ubiquity (Ubuntu) |
Fix Released
|
High
|
Colin Watson | ||
| Karmic |
Fix Released
|
High
|
Colin Watson | ||
Bug Description
Binary package hint: oem-config
oem-config-
If I proceed to fill in requested data, it also changes my hostname to
user-laptop :(
I am able to log in via a tty, stop the oem-config UpStart service
manually, and then restart GDM. That allows me to log in as usual.
However, after that, I cannot create a terminal, either from
gnome-termial or xterm. Both report:
"There was an error creating the child process for this
terminal"
Interestingly, if I do not answer any of the oem-config questions, and
proceed to stop oem-config, GDM starts up on its own. Now, logging in I
can start up terminal programs.
oem-config version: 1.99.21
lsb_release -rd:
Description: Ubuntu karmic (development branch)
Release: 9.10
| description: | updated |
| affects: | oem-config (Ubuntu) → ubiquity (Ubuntu) |
| Changed in ubiquity (Ubuntu): | |
| assignee: | nobody → Colin Watson (cjwatson) |
| importance: | Undecided → High |
| status: | New → Fix Committed |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in ubiquity (Ubuntu Karmic): | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
This bug was fixed in the package ubiquity - 1.99.23
---------------
ubiquity (1.99.23) karmic; urgency=low
[ Evan Dandrea ]
* Add missing definition of self.controller for the noninteractive
page in the language plugin.
[ Colin Watson ]
* Use an explicit state file to determine whether oem-config runs, since
with Upstart it's no longer straightforward to just add/remove rc*.d
symlinks (LP: #432180).
* We already avoid copy-blacklisting files in packages that have a prerm,
since they might require non-trivial work before removing their files.
Now also avoid copy-blacklisting files in dependencies of such packages,
as otherwise we risk leaving programs in the target system for a while
that don't have their library dependencies satisfied, causing confusion
when other programs try to use them (LP: #436613).
-- Colin Watson <email address hidden> Fri, 25 Sep 2009 14:59:33 +0100