m-a username checking broken

Bug #123984 reported by moma
16
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Invalid
Medium
Evan

Bug Description

Binary package hint: ubiquity

Hello all,

I want to report a couple of findings of Gutsy Gibbon Tribe 2.
Installation iso: gutsy-desktop-i386.iso

In the LiveCD, I did manual partitioning and started the "ubiquity" installer from the command line as instructed in the release notes (otherwise the manual partitioning provably freezes).
$ sudo ubiquity

It seemed to copy all files to harddisk but the migration assistant failed with these error messages.

<code>Traceback (most recent call last):
  File "/usr/lib/ubiquity/bin/ubiquity", line 202, in <module>
    main()
  File "/usr/lib/ubiquity/bin/ubiquity", line 199, in main
    install()
  File "/usr/lib/ubiquity/bin/ubiquity", line 65, in install
    ret = wizard.run()
  File "/usr/lib/ubiquity/ubiquity/frontend/gtk-ui.py", line 400, in run
    self.process_step()
  File "/usr/lib/ubiquity/ubiquity/frontend/gtk-ui.py", line 888, in process_step
    self.progress_loop()
  File "/usr/lib/ubiquity/ubiquity/frontend/gtk-ui.py", line 685, in progress_loop
    (ret, realtb))

RuntimeError: Install failed with exit code 1
Traceback (most recent call last):
  File "/usr/share/ubiquity/install.py", line 1594, in <module>
    install.run()
  File "/usr/share/ubiquity/install.py", line 377, in run
    self.configure_ma()
  File "/usr/share/ubiquity/install.py", line 1005, in configure_ma
    raise InstallStepError("MigrationAssistantApply failed with code %d" % ret)
InstallStepError: MigrationAssistantApply failed with code 1 </code>
---------------------

BTW: The migration assistant did not show all possibilities in its distro list.
Eg. my main Ubuntu distro on /dev/sdb3 was not presented in the list.
---------------------

GRUB:
The installer did not set any GRUB boot loader so I manually added "Gutsy Gibbon" to my existing /grub/menu.lst on /dev/hda2.
There is not /grub folder.

$ ls -l /boot/
total 16860
-rw-r--r-- 1 root root 423721 2007-06-25 21:48 abi-2.6.22-7-generic
-rw-r--r-- 1 root root 75196 2007-06-25 21:48 config-2.6.22-7-generic
-rw-r--r-- 1 root root 7209687 2007-07-04 14:34 initrd.img-2.6.22-7-generic <-- appeared first after upgrade
-rw-r--r-- 1 root root 6804899 2007-06-27 15:10 initrd.img-2.6.22-7-generic.bak
-rw-r--r-- 1 root root 103204 2007-05-21 14:56 memtest86+.bin
-rw-r--r-- 1 root root 821673 2007-06-25 21:48 System.map-2.6.22-7-generic
-rw-r--r-- 1 root root 1762584 2007-06-25 21:48 vmlinuz-2.6.22-7-generic

One thing I noticed is that the /boot directory provided "initrd.img-2.6.22-7-generic.bak" but no "initrd.img-2.6.22-7-generic" there.
So I booted with vmlinuz-2.6.22-7-generic and initrd.img-2.6.22-7-generic.bak.

After boot, Ubuntu downloaded many updates and "initrd.img-2.6.22-7-generic" was one that appeared.
------------------------

Rebooted.
More findings to come.

Attachments come in the next posting.

Revision history for this message
moma (osmoma) wrote :
Revision history for this message
moma (osmoma) wrote :
Revision history for this message
moma (osmoma) wrote :
Evan (ev)
Changed in ubiquity:
assignee: nobody → evand
status: New → Confirmed
Revision history for this message
Colin Watson (cjwatson) wrote :

Wow, it's trying to create a user called "-". Is m-a's username checking broken?

Revision history for this message
Evan (ev) wrote :

It looks like a bug in the ubiquity end of migration-assistant. The code in gtkui.py uses '-' as a key for a null username to prevent a partially filled out user details form from appearing wherever a username is not filled in. I know that doesn't make much sense, I'll have to look over that section of code again to give a more thorough explanation.

moma, can you run the installer again with the --debug option (`ubiquity --debug` in a terminal window), and attach /var/log/installer/debug and /var/log/syslog to this bug report? It will make it easier for me to figure out exactly what is going wrong here.

Thanks!

Revision history for this message
Nanley Chery (nanoman) wrote :

I had the same problem:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/135656
*marking mine as a duplicate*

Revision history for this message
Nanley Chery (nanoman) wrote :

I should add that I was using Tribe 5.

Revision history for this message
Nanley Chery (nanoman) wrote :

This same bug occurred on a Feisty install:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/112811

This should be fixed in gutsy and sent to feisty as well.

Revision history for this message
David Balažic (xerces8) wrote :

Bug 112811 is about not properly detecting a too small install partition. Are you sure it is a duplicate ?
As I see it, this bug is about user creation ?

Revision history for this message
Nanley Chery (nanoman) wrote :

You're right, it's supposed to be a dupe of 48355 instead. This bug is about the Migration Assistant failing, I accidentally marked 112811 as a duplicate because it had all the symptoms of of this bug. I'll be more careful next time.

Revision history for this message
Nanley Chery (nanoman) wrote :

Messed up again -- 112811 is a duplicate of 77966.

Evan (ev)
Changed in ubiquity:
importance: Undecided → Medium
Revision history for this message
Evan (ev) wrote :

I'm bumping this back to incomplete as the code in ubiquity for the migration-assistant page has been greatly simplified and no longer creates multiple users, thus removing the need for and in turn removing the code itself for the block in question. Are you able to reproduce this using any of the Hardy Live CDs?

Thanks!

Changed in ubiquity:
status: Confirmed → Incomplete
Revision history for this message
Evan (ev) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in ubiquity:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.