manual partitioning hangs indefinitely

[Martin Pitt]

Binary package hint: ubiquity

WhenI select manual partitioning on my real desktop system (amd64, two HDs, lots of different file systems), I get the 'Scanning disks' dialog quickly, then it disappears, and then ubiquity is just hanging. This does not happen in vmware (with only an ext3 and swap partition), and it does not happen if ubiquity is started with --debug.

Adilson is currently preparing for providing some logs.

[Oliver Grawert (ogra)]

seeing the same on edubuntu

[Adilson Oliveira (agoliveira)]

Syslog just after hang

[Adilson Oliveira (agoliveira)]

Partman logs just after hang. I'm testing using a Intel macbook which already have installed Windows and MacOS X so it had efi, ntfs and afs, ext3 and swap partitions (ext3 and swap from a previous Ubuntu instalation). All the previous instalations that way, including Tribe 1, went fine. If I also try to run ubiquity with --debug, it works.

[Oliver Grawert (ogra)]

running it as:

sudo ubiquity --debug

seems to work fine,

gksudo ubiquity --debug

actually reproduces the hang for me

[Patrice Vetsel (vetsel-patrice)]

I confirm Oliver Grawert

running it as:
sudo ubiquity --debug

seems to work fine

[Tim Hull (thully)]

I seem to be experiencing a related issue - when I tried manual partitioning in Tribe 2, it hung just after I tried to make changes to the partitions.
This is on a MacBook Core Duo 1.83GHz w/a preexisting OS X partition.

[Alex Launi (alexlauni)]

+1 confirmed. Hangs when gksudo is used. if sudo is used the install goes just fine. Gutsy tribe2 i386 livecd on HP Pavillion dv5139us Turion64 system, 2gb ram.

[Andrew Conkling (andrewski)]

For the record, running `sudo ubiquity` seems to work just fine; the '--debug' flag does not seem necessary.

[Sarah Kowalik (hobbsee-deactivatedaccount)]

This definetly appears to be a bug in the way sudo/gksudo handles things...

No matter which window manager you use, using sudo ubiquity will always work fine, and using gksudo ubiquity, even from a command line, will fail.

On compiz, the window is drawn, but hidden (you find out if you try to kill it - it pops up, saying "are you sure you want to quit the installer?), and in metacity, the entire installer just freezes.

[Sero (sero4linux)]

I can confirm this bug, too in Tribe 2. The workaround to use sudo ubiquity in the terminal instead of the install link on the desktop helped.

[Evan (ev)]

I can finally reproduce this (in VMWare), at least with respect to gksu. Assigning it to myself.

[Martin Pitt (pitti)]

In version 1.5.6, Evan uploaded a workaround which should do for tribe-3. Moving over to tribe-4.

[Martin Pitt (pitti)]

Would be nice to fix for Tribe 4, but with the workaround in place, it is fine for me to slip.

[OS/2-User (fzf7a2c02)]

Being a bloody Linux beginner, this one kept me for the last 3 weeks from getting 7.10 tribe-2 and tribe-3 installed, using the desktop install icon. Luckily, someone eventually pointed me to this bug, describing, how to circumvent the problem after all, right before I was about to give up on Ubuntu for good.
I was so happt, when I saw the other day, that this bug was listed in the to be dealt with stuff for https://launchpad.net/ubuntu/+milestone/tribe-4, but today I had to realize, that it got shifted to tribe-5 instead.
So it likes like there, will be no fun then with tribe-4 either, for all those still ignorant first timers like myself :-(

[Martin Pitt (pitti)]

Hi,

OS/2-User [2007-08-08 0:57 -0000]:
> I was so happt, when I saw the other day, that this bug was listed
> in the to be dealt with stuff for
> https://launchpad.net/ubuntu/+milestone/tribe-4, but today I had to
> realize, that it got shifted to tribe-5 instead. So it likes like
> there, will be no fun then with tribe-4 either, for all those still
> ignorant first timers like myself :-(

That shouldn't affect you. In Tribe 3 we implemented a workaround
which unbreaks the installer. We just didn't manage to get the 'clean'
solution into Tribe 4, but that doesn't stop anyone from installing.

So, good luck!

[OS/2-User (fzf7a2c02)]

Mmmh, you wrote: "In Tribe 3 we implemented a workaround

which unbreaks the installer", so I guess that should be "Tribe 4" instead, since it was Tribe 3, I still had the trouble with. But good to hear, that this pit fall will be gone in tomorrow's Tribe 4 :-) Thank you.

Now someone only still needs to eventually fix the "grub-install crashes on everything but an ext3 formatted /boot partition." (Bug 123102 & 14010)

[Henrik Nilsen Omma (henrik)]

Moving milestone.

[jerrylamos (jerrylamos)]

Gutsy Tribe 5 manual partitioning installed fine, Ubuntu, Xubuntu, Kubuntu on two different systems (multi boot). Tribe 4 would not, Tribe 5 does install O.K. on these computers.

Cheers, Jerry Amos

[Henrik Nilsen Omma (henrik)]

Jerry, did you have the bug pre-tribe5?

[jerrylamos (jerrylamos)]

Yes, Tribe 4 had the bug on both the IBM NetVista 2 gHz P4 and also on 1.2 gHz Celeron motherboard. Last Tribe 4 daily build I tried was 20070816 which still had the bug.
Cheers, Jerry

[droid (andrey-mak)]

Hi people, first post, sorry if it's not the place/time/method.

Encountered this problem during installation of standard desktop 7.04.

Running a PC with Gigabyte mobo that has a Gigabyte SATA raid.
Wanted to use the RAID controller for RAID1 configuration.

Booted into the graphical installation mode.
Ubuntu did not detect the RAID controller until "dmraid" package was installed.

"dmraid -ay" dispayed my array name as "jmicron_GRAID".

Running ubiquity at this point had caused the partitioning stage to fail with "could not stat device name" error.

Apparently Gigabyte controller reports the array name as "jmircron_GRAID " (yes, those are blank spaces used to fill a total of 16 characters).

Partman was not able to handle this until the following operations were performed:
1. "dmsetup rename jmicron_GRAID\ \ \ \ \ \ \ \ \ \ jmicron_GRAID" (in order to reproduce the correct ammount of spaces - type /dev/mapper/jm & start tabbing until bash completes the name for you).
2. "/etc/init.d/udev restart"

Afterwards I was able to run Ubiquity using the icon on the desktop.

Hope this helps anyone!

Bregs,
Droid

[Henrik Nilsen Omma (henrik)]

Moving milestone to beta.

[Evan (ev)]

Droid,
Please open a separate bug report as your problems are unrelated to this one.

Thanks

[Evan (ev)]

I never managed to figure out why my patch to libgksu worked, and what was causing libgksu to lose stderr. I am leery of introducing such a patch so late in the release cycle, especially given that our workaround is non-invasive and continues to work without issue (though please let me know if you've found otherwise).

I think it would be best to defer this. Thoughts?

[Martin Pitt (pitti)]

Hi,

Evan Dandrea [2007-09-20 4:15 -0000]:
> I think it would be best to defer this. Thoughts?

I agree. Please apply it early in Hardy, so that we get much testing.

[Yotam Medini (yotam-medini-gmail)]

I just installed Feisty. I had to restart the process twice, since
when I tried creating an 'unused' (or 'not used' ?) partiton,
the partitioner seemed to hang.

[Andrew Conkling (andrewski)]

On 10/1/07, Yotam Medini <email address hidden> wrote:
>
> I just installed Feisty. I had to restart the process twice, since
> when I tried creating an 'unused' (or 'not used' ?) partiton,
> the partitioner seemed to hang.

This bug relates to a problem in Gutsy. Maybe another bug has been reported
for your issue?

[droid (andrey-mak)]

it is a known problem with Gigabyte's motherboards (their SATA controller,
to be exact) - does this machine run on a Gigabyte mobo?

On 10/2/07, Yotam Medini <email address hidden> wrote:
>
> I just installed Feisty. I had to restart the process twice, since
> when I tried creating an 'unused' (or 'not used' ?) partiton,
> the partitioner seemed to hang.
>
> --
> manual partitioning hangs indefinitely
> https://bugs.launchpad.net/bugs/122645
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[dale gallagher (zoot)]

Installed 7.10 beta from the downloadable ISO on a IBM ThinkPad T43p (system info attached).

initially ubiquity would not run, so I ran it in a terminal, which indicated an IO error when trying to access a library, but running it under sudo: sudo ubiquity... got it going.

When using manual installer to specify a mount-point for a FAT32 partition, the entire OS and UI froze. Only recourse was to reboot.

Finally, about a 3rd of the way through my 3rd attempt (leaving out the FAT32 partition mounting) the installer complained about the CD/disk/CPU temp being possible culprits for the aborted installation attempt.

[rfurman24 (rfurman24)]

Just tried to install amd64 beta iso and ubiquity crashes with manual partition hanging. I will try to sudo ubiquity when I get home and report back.

[rfurman24 (rfurman24)]

The only way I could get past manual partitioning in the 64bit was to gksu ubiquity in a terminal but the system never finished the install and did not have any crash reports. I tried x86 version ubiquity runs normally but does the same as far as never finishing install.

[rfurman24 (rfurman24)]

I finally got 64bit installed with gksu ubiquity --no-migration-assistant. I can not get x86 to install no matter what. Migration assistant I believe is the cause but ubiquity will not run with the gksu or sudo command with --no-migration-assistant.

[Evan (ev)]

rfurman24,

As your bug could be entirely different given that description, can you please run the installer again using the most recent desktop CD (http://cdimage.ubuntu.com/daily-live/20071008/) and create a new bug report? Please use the --debug option for this test and not --no-migration-assistant. When the installer hangs, please attach /var/log/installer/debug and /var/log/syslog to your bug report. Also, please do not run ubiquity with sudo as ubiquity handles its own privilege escalation.

Thanks!

[rfurman24 (rfurman24)]

I will do that as soon as I get home. The only reason I used sudo is because nothing else was working. Even after using the gksu option I still had to use the --no-migration-assistant option. Hopefully the daily build will fix my concern. Thanks.

[rfurman24 (rfurman24)]

Here you go.

Ubiquity 1.6.2
debconf (developer): <-- VERSION 2
debconf (developer): --> 0 2.0
debconf (developer): <-- CAPB
debconf (developer): --> 0 multiselect escape
debconf (developer): <-- GET oem-config/enable
debconf (developer): --> 10 oem-config/enable doesn't exist
debconf (developer): <-- VERSION 2
debconf (developer): --> 0 2.0
debconf (developer): <-- CAPB
debconf (developer): --> 0 multiselect escape
debconf (developer): <-- GET ubiquity/failure_command
debconf (developer): --> 0
debconf (developer): <-- VERSION 2
debconf (developer): --> 0 2.0
debconf (developer): <-- CAPB
debconf (developer): --> 0 multiselect escape
debconf (developer): <-- GET ubiquity/success_command
debconf (developer): --> 0
debconf (developer): <-- VERSION 2
debconf (developer): --> 0 2.0
debconf (developer): <-- CAPB
debconf (developer): --> 0 multiselect escape
debconf (developer): <-- GET debian-installer/locale
debconf (developer): --> 0
debconf (developer): <-- GET debian-installer/fallbacklocale
debconf (developer): --> 0
debconf (developer): <-- VERSION 2
debconf (developer): --> 0 2.0
debconf (developer): <-- CAPB
debconf (developer): --> 0 multiselect escape
debconf (developer): <-- FSET languagechooser/language-name seen false
debconf (developer): --> 0 false
debconf (developer): <-- SET localechooser/alreadyrun false
debconf (developer): --> 0 value set
Oct 9 00:43:25 ubiquity: Starting up '['log-output', '-t', 'ubiquity', '--pass-stdout', '/usr/lib/ubiquity/localechooser/localechooser']' for ubiquity.components.language.Language
Oct 9 00:43:25 ubiquity: Watching for question patterns ^languagechooser/language-name, ^countrychooser/shortlist$
Oct 9 00:43:25 debconf (filter): <-- CAPB backup
debconf (developer): <-- CAPB backup
debconf (developer): --> 0 multiselect escape
Oct 9 00:43:25 debconf (filter): <-- REGISTER debian-installer/language debconf/language
debconf (developer): <-- REGISTER debian-installer/language debconf/language
debconf (developer): --> 0
Oct 9 00:43:25 debconf (filter): <-- SET debconf/language C
debconf (developer): <-- SET debconf/language C
debconf (developer): --> 0 value set
Oct 9 00:43:25 debconf (filter): <-- FGET languagechooser/language-name seen
debconf (developer): <-- FGET languagechooser/language-name seen
debconf (developer): --> 0 false
Oct 9 00:43:25 debconf (filter): <-- GET localechooser/alreadyrun
debconf (developer): <-- GET localechooser/alreadyrun
debconf (developer): --> 0 false
Oct 9 00:43:25 debconf (filter): <-- GET debian-installer/locale
debconf (developer): <-- GET debian-installer/locale
debconf (developer): --> 0
Oct 9 00:43:25 debconf (filter): <-- SET localechooser/alreadyrun true
debconf (developer): <-- SET localechooser/alreadyrun true
debconf (developer): --> 0 value set
Oct 9 00:43:25 debconf (filter): <-- GET debian-installer/framebuffer
debconf (developer): <-- GET debian-installer/framebuffer
debconf (developer): --> 0 true
Oct 9 00:43:25 debconf (filter): <-- INPUT critical languagechooser/language-name-fb
Oct 9 00:43:25 debconf (filter): widget found for languagechooser/language-name-fb
debconf (developer): <-- GET languagechooser/language-name
deb...

[mjfi9ja2 (mjfi9ja2)]

The manual partitioning tool hung on my laptop, with a Windows NTFS partition and an existing ext3 and swap partition(Running SuSE). I don't understand how Ubuntu still has issues with the partitioning tool. Looking through the bug reports I see similar errors since 5.10, I have been experiencing this since about that time. I haven't had chance to do any further testing as I installed Mandriva Linux as I had a CD for that lying around and it just worked. How about you just take their partitioning tool and use it here, or provide more, well tested, options like: install on existing Linux partition, rather that destroy all, or the manual option.

[mjfi9ja2 (mjfi9ja2)]

I was using 7.10 desktop.

[Mathiasdm (mathias-demare-gmail)]

I have this problem in Ubuntu Hardy Alpha 3 (I didn't have it with Gutsy).

I'll attach my logs the next time I boot the LiveCD.

[Mathiasdm (mathias-demare-gmail)]

I seem to be getting this bug both with sudo ubiquity --debug as well.
(I tried running the installer by double-clicking, and tried by typing 'sudo ubiquity --debug').

[Evan (ev)]

If you are seeing the installer hang it is probably another bug, not this one. Please file new bug reports for such issues. There has been a fix in place for this for quite some time, but this bug remains open as a reminder that we need a more elegant solution.

[Andreas Kern (kerna)]

maybe it is related, i had like the same problem but with gparted, the trick was for me to disable the floppy controller in the bios of my mainboard, sounded strange, but worked

[Phillip Susi (psusi)]

Is anyone still having this issue and does *NOT* have the floppy enabled in the bios ( and doesn't actually have a floppy )?

[Launchpad Janitor (janitor)]

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