Ubiquity hangs (100% cpu) during installation

[Clemens Eisserer]

Binary package hint: ubiquity

1.) Ubuntu-Version: Kubuntu 8.10-beta

2.) Default packages distributed on CD

3.) What I expect to happen:
Installer should show up and allow me to continue installation.

4.) What happens instead:
When starting kubunto-8.10-beta (happens also with alpha6), and I choose to start into installation mode (not into live-cd mode) I get to the point where X starts, and I see the black/white cross instead of the mouse-cursor but then installation get stuck.

Top says the process ubiquity is spinning at 100%, I tried to generate a stack-trace with gdb, but I don't know if the result is successful at all.

When using the installer of the live-cd installation also fails, the application hangs at the stage when it should display the partition view - the progress dialog pops up (says something like "analyzing partition tables" or something like that) but when it goes away the installer does not respond anymore.

[Clemens Eisserer (linuxhippy)]

by the way I read the section howto generate useful debug data, but in the case ubiquity hangs the wiki is still empty.

If the bug-report does not contain the information you need, please don't close it - instead ask me for the things you need with a description howto generate that data.

Thanks - Clemens

[Klaus S. Madsen (ubuntu-hjernemadsen)]

I saw the exact same problem when installing Kubuntu 8.10 Beta 1.

I booted in the Installer mode, and I got the ubiquity window when X started but nothing happened. Switching to terminal two, top confirmed that ubiquity was using 100% cpu time (well, 50%, as its a dualcore machine). So I killed the ubiquity process, which caused KDE to start on the X terminal.

When KDE was started, I could click the installation icon, and the installation started, and finished as it should. However during the installation ubiquity was using 100% cpu most of the time. After the installation had completed, and I booted the machine, I got a warning from the package management that the installation of the language pack wasn't complete. I don't think that I was asked which language I would like to use, except at the isolinux prompt.

In the logs, I saw the same as in the already attached syslog, that ubiquity after two log-output lines output two identical "switched to page stepLanguage" lines.

The machine I installed on was a Fujitsu-Siemens Lifebook P7320, which has a 32-bit processor. If you need any more information, I'll happily provide it.

[Klaus S. Madsen (ubuntu-hjernemadsen)]

I just tried running the installation on a Thinkpad T61p, which doesn't trigger this bug.

However I noticed the language selection dialog at the beginning of the installation, which I didn't see when I installed on the Lifebook yesterday, so it seems that it is this page that causes Ubiquity to go into the 100% mode.

However the "language pack installation isn't complete" message still popped up after installation.

[Clemens Eisserer (linuxhippy)]

Klaus, do you see ubiquity before it hangs?
I don't see it at all, it seems like it hangs in the start-process and therefor never appears.

[Klaus S. Madsen (ubuntu-hjernemadsen)]

I see a window called Ubiquity, but it's white and empty. It doesn't respond to any of the buttons in the window decoration (but that might be natural, since there doesn't seem to be a Window Manager running at that point). After I killed the ubiquity process and started the installer from the KDE desktop, I'm 99% certain that I didn't get to see the language selection page.

However my syslog looks similar to yours (with the two switched to page stepLanguage lines in it), which seems to suggest that the hang is in the same place.

[Phillip Susi (psusi)]

Are you able to reproduce this on 12.04+?

[Clemens Eisserer (linuxhippy)]

Sorry, I don't know.

Because of Ubuntu's polititics to replace crucial parts of its Linux desktop with self-written components (unity, mir, upstart, ...), I've decided to switch to a distribution which embraces free software, instead of replacing it.

[Launchpad Janitor (janitor)]

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