oem-config with debconf_ui does not remove itself after finishing
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubiquity (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: ubiquity
now oem-config does not go into an endless loop anymore. it finishes the setup properly and configures the system. i can log in as the created user with proper keyboard timezone and locale settings. sadly it does not seem to remove itself at the end so on next boot the oem-config process starts over again. the final lines in the log are:
Feb 14 12:05:24 ubiquity: Starting up '['log-output', '-t', 'ubiquity', '--pass-stdout', '/bin/hw-detect']' for ubiquity.
debconf (developer): <-- GET hw-detect/load-ide
debconf (developer): --> 0 false
debconf (developer): <-- PROGRESS START 0 1000 hw-detect/
debconf (developer): --> 0 OK
debconf (developer): <-- PROGRESS INFO hw-detect/
debconf (developer): --> 0 OK
debconf (developer): <-- PROGRESS STEP 20
debconf (developer): --> 0 OK
debconf (developer): <-- PROGRESS STEP 20
debconf (developer): --> 0 OK
debconf (developer): <-- PROGRESS STEP 900
debconf (developer): --> 0 OK
debconf (developer): <-- PROGRESS STEP 20
debconf (developer): --> 0 OK
debconf (developer): <-- PROGRESS SET 1000
debconf (developer): --> 0 OK
debconf (developer): <-- PROGRESS STOP
debconf (developer): --> 0 OK
debconf (developer): <-- PROGRESS INFO ubiquity/
Can't call method "info" on an undefined value at /usr/share/
grep: /target/
full log will be attached separately
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running only once:
apport-collect 521662
and any other logs that are relevant for this particular issue.