Hello,

Well I will try to explain what I did, bud I not a advance user and my
English is not so well, so please excuse me.

First let me explain that at this point I have installed ubuntu 9.04 64 bits
edition successful, but I had to try to installed several times with the
same error, I also try installing 32 bits version with the same error, so I
notice that maybe I was doing something wrong in the installation.

Before I tried to install Ubuntu and had this errors, I had installed ubuntu
9.04 64bits edition installed with wubi, from windows xp, but I wanted to
install ubuntu on a exclusive partition, so I make a partition ext 3, and
use LVPM to migrated the previus installation in windows to the partition
ext3. I only had to modify the menu.lst file to work propertly, and I had
ubuntu on a exclusive partition. But with the incoming realease of ubuntu
9.10, I wanted to be ready for the instalation, so I managed to make and new
partition and move /home to the new partition.

Now when I have installed ubuntu 9.04 64 bits edition propertly, I did
realized that the problem was that I didn't marked the home partition to be
formated,  and when the instalation finish coping the files and try to
proceed with the instalation detect that already was a information of the
/home and aborted the instalation or just can't continue with it.

I hope this can help you understand what happend, and please let me know if
you need something else.

Best Regards!


2009/10/7 Evan Dandrea <[email protected]>

> What is happening here is that the part of the installer that handles
> removing system files from a partition that was not marked to be
> formatted told the part of the installer that adds a user to the new
> system to create said user with uid 0, the uid of root, which wont ever
> work.
>
> We've worked around this for the next release of the installer (ubiquity
> 1.99.29) by not trying to preserve the uid of the default user that was
> in place on the operating system that you're installing over top of.
>
> However, I'm curious to know what's causing this to happen in the first
> place, so we can better understand the scope of the problem.  So would
> you be so kind as to explain the exact steps you took when partitioning,
> and to confirm that the home directory of user you inputted while
> installing Ubuntu was owned by root before you attempted to install?
> Any additional information about how you installed the Linux operating
> system you had before installing Ubuntu would be equally appreciated.
>
> Thanks!
>
> ** Changed in: ubiquity (Ubuntu)
>       Status: New => Incomplete
>
> --
> ubiquity crashed with InstallStepError in configure_user()
> https://bugs.launchpad.net/bugs/445138
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “ubiquity” package in Ubuntu: Incomplete
>
> Bug description:
> Binary package hint: ubiquity
>
> I don't know is this error is common with the present in the options, what
> I can say is this error occur twice in the same percentage 80% approximately
> after coping files and when it start to create profiles.
>
> ProblemType: Crash
> Architecture: amd64
> DistroRelease: Ubuntu 9.04
> ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
> InterpreterPath: /usr/bin/python2.6
> MediaBuild: Ubuntu 9.04 "Jaunty Jackalope" - Release amd64 (20090420.1)
> Package: ubiquity 1.12.12
> ProcAttrCurrent: unconfined
> ProcCmdline: /usr/bin/python /usr/lib/ubiquity/bin/ubiquity --only
> ProcEnviron:
>  LANGUAGE=
>  PATH=(custom, no user)
>  LANG=es_ES.UTF-8
> PythonArgs: ['/usr/lib/ubiquity/bin/ubiquity', '--only']
> SourcePackage: ubiquity
> Title: ubiquity crashed with InstallStepError in configure_user()
> Uname: Linux 2.6.28-11-generic x86_64
> UserGroups:
>

-- 
ubiquity crashed with InstallStepError in configure_user()
https://bugs.launchpad.net/bugs/445138
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to