Ubiquity goes into an infinite loop on Thinkpad X130e

[Larry Hastings]

I own a Lenovo X130e (2338CT). If I attempt to install Ubuntu 12.04 on it, the installer goes into an infinite loop, ceasing to respond to user input and consuming 100% of one core, as well as slowly consuming additional RAM. If I let it run for a half hour the machine goes completely unresponsive. (I assume this is a side-effect of running out of RAM.)

Ubiquity always fails at the same spot. It's just after I fill out my account information (full name, account name, computer name, whether I want an encrypted home directory). Immediately after I press "Continue" on that dialog, the cursor changes to the round busy clock cursor, and Ubiquity begins consuming 100% of CPU etc etc. (I believe the next screen is the "choose your account picture / take a picture" wizard.)

Barry Warsaw (and a helpful Toshio from Red Hat) examined the machine at PyCon and observed this behavior. They weren't able to discover any more than the above.

I have reproduced it with 12.04 daily builds over the past several weeks. The most recent one I tried was the 3/28 build (sha1sum started with "8a235"). They all exhibit the exact same behavior.

Varying the install options doesn't seem to affect the behavior--it still stops at the same spot. It doesn't matter whether I have a separate home partition, or what filesystem I use for the partitions, or whether or not I have swap. (I admit I haven't tried experimenting with different time zones and keyboard configurations.)

My X130e is configured as following:

  * Intel Core i3-2367M
  * 4GB memory
  * OCZ Vertex 2 SSD 240GB MAX-IOPS (installed myself)
  * Bluetooth module
  * Intel Centrino Advanced-N + WiMAX 6250 (2x2 ABGN)
  * No integrated broadband adapter

I am a reasonably sophisticated computer user and am willing to run experiments on the laptop upon request.

[Jean-Baptiste Lallement (jibel)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 966294, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.