oem-config not removed after install on preinstalled desktop images due to debconf.dat being locked

Bug #856293 reported by Oliver Grawert on 2011-09-22
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Medium
Ubuntu Installer Team
Oneiric
Medium
Ubuntu Installer Team
Precise
Medium
Ubuntu Installer Team

Bug Description

doing an oem-config install of oneiric beta2 results in the ubiquity icon being on the desktop (and ubiquity/oem-config staying installed) after the installation.

checking syslog only reveals that debconf.dat was locked when ubiquity tried to get to the package removal.

Oliver Grawert (ogra) wrote :
Changed in ubiquity (Ubuntu):
importance: Undecided → Medium
Changed in ubiquity (Ubuntu Oneiric):
milestone: none → ubuntu-11.10
tags: added: iso-testing
tags: added: ubiquity-2.7.35
tags: added: oneiric

This looks a bit suspect to me:
Sep 22 12:26:39 ac100 AptDaemon.Worker: INFO: Upgrade system with safe mode: 1
Sep 22 12:27:28 ac100 kernel: [ 194.092879] kworker/u:2: page allocation failure. order:1, mode:0x4020
Sep 22 12:27:28 ac100 kernel: [ 194.092921] Backtrace:
Sep 22 12:27:28 ac100 kernel: [ 194.093049] [<c00427d0>] (unwind_backtrace+0x0/0xe0) from [<c00e29dc>] (__alloc_pages_nodemask+0x5c0/0x6dc)
Sep 22 12:27:28 ac100 kernel: [ 194.093168] [<c00e29dc>] (__alloc_pages_nodemask+0x5c0/0x6dc) from [<c0108908>] (allocate_slab+0x54/0xa8)
Sep 22 12:27:28 ac100 kernel: [ 194.093337] [<c0108908>] (allocate_slab+0x54/0xa8) from [<c0109d74>] (new_slab+0x2c/0x13c)
Sep 22 12:27:28 ac100 kernel: [ 194.093510] [<c0109d74>] (new_slab+0x2c/0x13c) from [<c04048ec>] (__slab_alloc.constprop.48+0x140/0x2c8)
Sep 22 12:27:28 ac100 kernel: [ 194.093687] [<c04048ec>] (__slab_alloc.constprop.48+0x140/0x2c8) from [<c010bbb0>] (__kmalloc_track_caller+0xa0/0x18c)
Sep 22 12:27:28 ac100 kernel: [ 194.093828] [<c010bbb0>] (__kmalloc_track_caller+0xa0/0x18c) from [<c0332d50>] (__alloc_skb+0x50/0xe0)
Sep 22 12:27:28 ac100 kernel: [ 194.093911] [<c0332d50>] (__alloc_skb+0x50/0xe0) from [<c0332df8>] (dev_alloc_skb+0x18/0x3c)
Sep 22 12:27:28 ac100 kernel: [ 194.094072] [<c0332df8>] (dev_alloc_skb+0x18/0x3c) from [<bf38b320>] (rt2x00queue_alloc_rxskb+0x40/0xb4 [rt2x00lib])
Sep 22 12:27:28 ac100 kernel: [ 194.094336] [<bf38b320>] (rt2x00queue_alloc_rxskb+0x40/0xb4 [rt2x00lib]) from [<bf388834>] (rt2x00lib_rxdone+0x3c/0x1bc [rt2x00lib])
Sep 22 12:27:28 ac100 kernel: [ 194.094582] [<bf388834>] (rt2x00lib_rxdone+0x3c/0x1bc [rt2x00lib]) from [<bf3bd4f8>] (rt2x00usb_work_rxdone+0x58/0x8c [rt2x00usb])
Sep 22 12:27:28 ac100 kernel: [ 194.094754] [<bf3bd4f8>] (rt2x00usb_work_rxdone+0x58/0x8c [rt2x00usb]) from [<c0087ce8>] (process_one_work+0x270/0x464)
Sep 22 12:27:28 ac100 kernel: [ 194.094852] [<c0087ce8>] (process_one_work+0x270/0x464) from [<c00881c0>] (worker_thread+0x134/0x230)
Sep 22 12:27:28 ac100 kernel: [ 194.095031] [<c00881c0>] (worker_thread+0x134/0x230) from [<c008c1a4>] (kthread+0x7c/0x84)
Sep 22 12:27:28 ac100 kernel: [ 194.095129] [<c008c1a4>] (kthread+0x7c/0x84) from [<c003c408>] (kernel_thread_exit+0x0/0x8)

Changed in ubiquity (Ubuntu Oneiric):
assignee: nobody → Ubuntu Installer Team (ubuntu-installer)
Tobin Davis (gruemaster) wrote :

To work around this, switch to a text console (<ctrl><alt><F1>) and log in using the username & password entered during the first run through oem-config. Next, type "sudo oem-config-remove && sudo reboot". This should remove all ubiquity related packages and reboot into the login screen (or default user if autologin was selected).

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubiquity (Ubuntu):
status: New → Confirmed
Tobin Davis (gruemaster) on 2011-10-13
Changed in ubiquity (Ubuntu Oneiric):
milestone: ubuntu-11.10 → none
tags: added: armel
Jani Monoses (jani) wrote :

I found that not setting login to automatic when asked in the installer, and letting it run after the installer window disappears and until it lands in the lightdm greeter works too.

It works very slowly but in the end it removes those installer related packages if allowed to.
But it is confusing with no installer window and more than once I just rebooted thinking it hung and then the manual removal is necessary.

Happy (happy-studying) wrote :

I did this command sudo oem-config remove, but it response with "Ubiquity already running". So it does not fix the installation problem. After reboot it returns to the language selection again

Oliver Grawert (ogra) wrote :

the command is oem-config-remove (note the dash) ...

if you call "oem-config remove" like you did above, you execute ubiquity in oem-config mode and hand the option "remove" to it, which will indeed result in a complaint from ubiquity ...

dino99 (9d9) wrote :

oneiric have reached EOL now

Changed in ubiquity (Ubuntu Oneiric):
status: Confirmed → Invalid
Changed in ubiquity (Ubuntu Precise):
status: Confirmed → Invalid
Changed in ubiquity (Ubuntu):
status: Confirmed → Invalid
Oliver Grawert (ogra) wrote :

@dino99:

could you pretty please stop to close *all* tasks on open bugs just because oneiric is EOL ? i got about 300 mails from the mess you made today, now someone has to go through all these bugs again and check if you actually only closed oneiric or natty tasks.

you are producing a ton of work for us, please make sure to really only close the tasks for the EOL releases !

Changed in ubiquity (Ubuntu Precise):
status: Invalid → Confirmed
Changed in ubiquity (Ubuntu):
status: Invalid → Confirmed
dino99 (9d9) on 2015-09-12
tags: removed: oneiric
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments