Ubiquity 2.3.13 (oem-config) fails to create initial user

missing:
ubuntu user with encrypted passwd...

Alpha-3's Ubiquity 2.3.3 (oem-config)

Alpha-3's syslog for comparison

Alpha-3's passwd, with correct user/password combo..

Ubiquity 2.3.15 (oem-config) just hit the armel repo, same problem...

Slowly been bisecting between the releases.. (rebuilding in a native chroot, and with testing it takes about 3-4 hours per build..)

Original Alpha-3's 2.3.3 is still first good, and 2.3.5 is current first bad..

Rebuilding 2.3.3 and 2.3.4 should know more tomorrow..

Regards,

Bisect complete, it looks like the changes from 2.3.3 (last good) to 2.3.4 (first bad) caused this regression..

somewhere in:
https://launchpad.net/ubuntu/+archive/primary/+files/ubiquity_2.3.3_2.3.4.diff.gz

Regards,

Ubiquity 2.3.17 (oem-config) still fails the same way...

Can you test with the released maverick repo and report back if this is still an issue?

Sure, I had stopped reporting as it would have been mostly the same spam.. ;)

With Ubiquity 2.4.4 (oem-config) (this is the console not X11/GTK version, which works ish..) Same issue.. Attaching recent oem-config log...

Regards,

Using the debconf frontend, this behavior looks to be expected - there is no support for calling out to plugininstall when in oem-config mode. Installation using the debconf frontend is most likely broke too.

Based on the behavior, I think this patch should help at least oem-config mode.

Thanks for looking into this Mario..

Unfortunally no dice with the last patch..

Traceback (most recent call last):
  File "/usr/sbin/oem-config", line 530, in <module>
    main(oem_config)
  File "/usr/sbin/oem-config", line 517, in main
    install(query=options.query)
  File "/usr/sbin/oem-config", line 242, in install
    ret = wizard.run()
  File "/usr/lib/ubiquity/ubiquity/frontend/debconf_ui.py", line 129, in run
    dbfilter = plugininstall.Install(self)
NameError: global name 'plugininstall' is not defined

Side note, due to a conversation on irc, i did switch the rootstock tar and untarring scripts to use "--numeric-owner" but no help from that either..

--numeric-owner only helps with the issue where ubiquity-dm doesnt start at all due to the dbus ownership being switched over to the UID/GUI found in the hosts passwd/group files ... (completely different bug)

on the preinstalled images for omap3/4 we use oem-config successfully the exact same way as rootstock does, this bug is a very strange weirdness...

Hi Mario,

With the last patch:

Traceback (most recent call last):
  File "/usr/sbin/oem-config", line 530, in <module>
    main(oem_config)
  File "/usr/sbin/oem-config", line 517, in main
    install(query=options.query)
  File "/usr/sbin/oem-config", line 242, in install
    ret = wizard.run()
  File "/usr/lib/ubiquity/ubiquity/frontend/debconf_ui.py", line 132, in run
    ret = dbfilter.run_unfiltered()
  File "/usr/lib/ubiquity/ubiquity/filteredcommand.py", line 205, in run_unfiltered
    prep = self.prepare(unfiltered=True)
  File "/usr/lib/ubiquity/ubiquity/components/plugininstall.py", line 38, in prepare
    install_bootloader_seen = self.db.fget('ubiquity/install_bootloader',
AttributeError: 'NoneType' object has no attribute 'fget'

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 628587

and any other logs that are relevant for this particular issue.

[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]