Installer Crashed

Bug #49533 reported by Kyle Getz
12
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Invalid
High
Unassigned

Bug Description

This is the information that was given to me when the installer crashed:

Traceback (most recent call last):
  File "/usr/bin/ubiquity", line 130, in ?
    install(sys.argv[1])
  File "/usr/bin/ubiquity", line 55, in install
    ret = wizard.run()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/kde-ui.py", line 311, in run
    self.process_step()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/kde-ui.py", line 734, in process_step
    self.mountpoints_to_summary()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/kde-ui.py", line 1047, in mountpoints_to_summary
    self.progress_loop()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/kde-ui.py", line 524, in progress_loop
    raise RuntimeError, ("Install failed with exit code %s; see "
RuntimeError: Install failed with exit code 1; see /var/log/installer/syslog and /var/log/syslog

Revision history for this message
William Grant (wgrant) wrote :

Thanks for the bug report. Can you please attach /var/log/syslog, /var/log/partman and /var/log/installer/syslog, as mentioned in the error text?

Changed in ubiquity:
importance: Untriaged → High
status: Unconfirmed → Needs Info
Revision history for this message
Kyle Getz (kyle-getz) wrote : /var/log/installer/syslog

/var/log/installer/syslog

Revision history for this message
Kyle Getz (kyle-getz) wrote : /var/log/partman

/var/log/partman

Revision history for this message
Kyle Getz (kyle-getz) wrote : /var/log/syslog

/var/log/syslog

Revision history for this message
Chalk (chalk) wrote :

Same thing happened to me (or I got an error code very close to this) when I tried to manually edit the partition table, but not out of intention to test this bug. I had some JFS partitions on my hard drive, and a swap partition, and a partition without any actual format. I removed all of those partitions, and then then manually editting the partition table worked (and the "use the largest contiguous free space" option showed up this time too), but get this, when I did go into manual editting, the only partitions I could create were ext2, fat32, fat16, and linux-swap. What in the world? When I installed this on my downstairs stationary computer, it worked fine. I set up two JFS partitions and one swap partition no problem. But now on my Sony VAIO it's failing miserably. What gives?

So annoying, cause I use 6.06 on the stationary one and it's great and I'd really love it for my laptop.

Maybe I'll try using alternate, I guess. Oh, and by the vay... I suppose I had better put up my logs for this to prove I'm not just making this junk up. I didn't record the actual error message before I fixed the problem, which is a downer, and may make this effort useless, but it was pretty much the one above, I seem to remember the same line numbers. Here are the logs for my system and its problems anyway, in case you want to check'em'out. Sweetheart. (What can I say, I have an affection for you ([kxedu]{0-3}ubuntu developers)).

Revision history for this message
Chalk (chalk) wrote :

It's cheesy pizza's /var/log/syslog of his disgrace of an install attempt!

Revision history for this message
Chalk (chalk) wrote : /var/log/installer/syslog

It's cheesy pizza's /var/log/installer/syslog of his disgrace of an install attempt!

Revision history for this message
Chalk (chalk) wrote : /var/log/partman

It's cheesy pizza's /var/log/partman of his disgrace of an install attempt!

Me and my installation-self-esteem issues.

Revision history for this message
matus mihalak (matus) wrote :

the same error occured to me, just with different numbers in "lines". what I did was:
1. installing windows on one (and only) partition
2. running Ubuntu 6.06 live cd and installing ubuntu - worked fine
3. updating Ubuntu - wifi stopped working
4. running ubuntu live cd and trying to re-install (the unpatched ubuntu system) - trying to use manual mount/partition - as it was created by the first ubuntu partition - crashed as mentioned in the first comment

Revision history for this message
Pål Arne Hoff (paal-arne) wrote :
Download full text (228.0 KiB)

Same crash for me it seems. Tried to install Kubuntu 6.06 LTS on an IBM Thinkpad T60 which already had Windows XP on /dev/sda1 (and two fat32 partitions). The error occured just before the installer had finished installing all packages (I think, wasn't watching...).

Actual error message:

Traceback (most recent call last):
  File "/usr/bin/ubiquity", line 130, in ?
    install(sys.argv[1])
  File "/usr/bin/ubiquity", line 55, in install
    ret = wizard.run()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/kde-ui.py", line 311, in run
    self.process_step()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/kde-ui.py", line 734, in process_step
    self.mountpoints_to_summary()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/kde-ui.py", line 1047, in mountpoints_to_summary
    self.progress_loop()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/kde-ui.py", line 524, in progress_loop
    raise RuntimeError, ("Install failed with exit code %s; see "
RuntimeError: Install failed with exit code 1; see /var/log/installer/syslog and /var/log/syslog

-----------/var/log/installer/syslog----------------------
Ubiquity 1.0.12
X Error: BadDevice, invalid or uninitialized input device 166
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 166
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
/usr/bin/iceauth: creating new authority file /root/.ICEauthority
X Error: BadDevice, invalid or uninitialized input device 166
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 166
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
kbuildsycoca running...
kio (KSycoca): ERROR: No database available!
Invalid entry (missing '=') at /tmp/kde-root/kconf_updatejGRp9b.tmp:1
ubiquity: Starting up '['/usr/lib/ubiquity/localechooser/localechooser']' for ubiquity.components.language.Language
ubiquity: Watching for question patterns ^languagechooser/language-name
Thu, 22 Jun 2006 19:03:05 INFO Step_before = stepLanguage
Thu, 22 Jun 2006 19:03:06 INFO Step_after = stepLocation
QSocketNotifier: invalid socket 15 and type 'Read', disabling...
QSocketNotifier: invalid socket 15 and type 'Write', disabling...
QSocketNotifier: invalid socket 15 and type 'Exception', disabling...
ubiquity: Starting up '['/usr/share/ubiquity/tzsetup']' for ubiquity.components.timezone.Timezone
ubiquity: Watching for question patterns ^time/zone$
X Error: BadDevice, invalid or uninitialized input device 166
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 166
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
ScimInputContextPlugin()
22 Jun 21:03:48 ntpdate[7036]: no server suitable for synchronization found
X Error: BadDevice, invalid or uninitialized input device 166
  Major opcode: 144
  Minor opcode: 3
  Resource id: ...

Revision history for this message
charlie turner (chjtr) wrote :
Download full text (41.8 KiB)

Same thing happens to me, but only after a reboot after the install hangs during formatting after custom partitioning.
Fujitsu Lifebook A3040 AMD Turion64, pulled the factory
hard disk, installed a WD120GB unit, started a fresh install
of 6.06 AMD64. I choose custom partitioning wanting to
setup a 1GB swap, 1GB /boot, 5GB /root, 40 GB /usr, and a
64GB /home. Everything appears to go correctly, I select format for all of the partitions except swap, and then I click
finish, or accept, or whatever (I don't remember), and when the formatting starts, the install hangs. After 10-15 minutes
I get tired of waiting, and reboot to start again. That is when I
 get the installer crashed message with the following :
Traceback (most recent call last):
  File "/usr/bin/ubiquity", line 130, in ?
    install(sys.argv[1])
  File "/usr/bin/ubiquity", line 54, in install
    wizard = ui.Wizard(distro)
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/kde-ui.py", line 158, in __init__
    cloexec=True))
  File "/usr/lib/python2.4/site-packages/debconf.py", line 125, in __init__
    write=self.dccomm.tochild)
  File "/usr/lib/python2.4/site-packages/debconf.py", line 48, in __init__
    self.setUp(title)
  File "/usr/lib/python2.4/site-packages/debconf.py", line 51, in setUp
    self.version = self.version(2)
  File "/usr/lib/python2.4/site-packages/debconf.py", line 60, in <lambda>
    lambda *args, **kw: self.command(command, *args, **kw))
  File "/usr/lib/python2.4/site-packages/debconf.py", line 81, in command
    status = int(status)
ValueError: invalid literal for int():

/var/log/installer/syslog :
Ubiquity 1.0.12
X Error: BadDevice, invalid or uninitialized input device 166
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 166
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
/usr/bin/iceauth: creating new authority file /root/.ICEauthority
X Error: BadDevice, invalid or uninitialized input device 166
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 166
  Major opcode: 144
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
kbuildsycoca running...
kio (KSycoca): ERROR: No database available!
kio (KSycoca): ERROR: No database available!
kio (KSycoca): ERROR: No database available!
kio (KSycoca): ERROR: No database available!
kio (KSycoca): ERROR: No database available!
kio (KSycoca): ERROR: No database available!
kio (KSycoca): ERROR: No database available!
kio (KSycoca): ERROR: No database available!
kio (KSycoca): ERROR: No database available!
kio (KSycoca): ERROR: No database available!
kio (KSycoca): ERROR: No database available!
kio (KSycoca): ERROR: No database available!
Invalid entry (missing '=') at /tmp/kde-root/kconf_updateun3XKb.tmp:1
ubiquity: Starting up '['/usr/lib/ubiquity/localechooser/localechooser']' for ubiquity.components.language.Language
ubiquity: Watching for question patterns ^languagechooser/language-name
Ubiquity 1.0.12
X Error: Bad...

Revision history for this message
Andrew Yeomans (ayeomans) wrote : Almost identical crash

Trying to update a dual boot Ubuntu hoary / Fedora system. Set to preserve all partitions except swap. Partitions were:
/dev/hda1 - Fedora root partition, mounted under Ubuntu as /fedora
/dev/hda2 - swap
/dev/hda3 - /home for both distros
/dev/hda5 - / for Ubuntu, installed with hoary and extras.
Traceback (most recent call last):
  File "/usr/bin/ubiquity", line 130, in ?
    install(sys.argv[1])
  File "/usr/bin/ubiquity", line 55, in install
    ret = wizard.run()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/gtkui.py", line 266, in run
    self.process_step()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/gtkui.py", line 741, in process_step
    self.mountpoints_to_summary()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/gtkui.py", line 1029, in mountpoints_to_summary
    self.progress_loop()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/gtkui.py", line 538, in progress_loop
    raise RuntimeError, ("Install failed with exit code %s; see "
RuntimeError: Install failed with exit code 1; see /var/log/installer/syslog and /var/log/syslog

Installer crash message:

Revision history for this message
Andrew Yeomans (ayeomans) wrote : /var/log/installer/syslog from dual-boot install

/var/log/installer/syslog from dual-boot install

Revision history for this message
Andrew Yeomans (ayeomans) wrote : /var/log/syslog from dual boot install

/var/log/syslog from dual boot install

Revision history for this message
Andrew Yeomans (ayeomans) wrote : /var/log/partman from dual-boot install

/var/log/partman from dual-boot install

Revision history for this message
Andrew Yeomans (ayeomans) wrote : Work-round

Work-round is to format the Ubuntu / partition. Install is progressing nicely.

Revision history for this message
ecoolman (eric-coolman) wrote : doesn't work-around

I tried formatting the ubuntu / partition (xfs) as well as my existing swap partition, it still failed with the same error.

Revision history for this message
Churusaa (churusaa) wrote :

It would appear that the only workaround to this problem that currently makes itself known is simply allowing the partitioner to work on it's own. For some reason, manually editing the partition table crashes the installer. If you need your root partition and main swap to be different from the automatically generated defaults, I would suggest downloading an Ubuntu 5.10 release iso, installing that, and permitting the 6.06LTS upgrade once you boot into your properly configured 5.10 system.
---Churusaa

Revision history for this message
Witold Krakowski (wkrakowski-gmail) wrote :

Same crash for me, always at 12% copying files to a reiserfs / partition.

Revision history for this message
Marc Abramowitz (msabramo) wrote :

Just got the same error I believe:

Traceback (most recent call last):
  File "/usr/bin/ubiquity", line 130, in ?
    install(sys.argv[1])
  File "/usr/bin/ubiquity", line 55, in install
    ret = wizard.run()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/gtkui.py", line 264, in run
    self.progress_loop()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/gtkui.py", line 538, in progress_loop
    raise RuntimeError, ("Install failed with exit code %s; see "
RuntimeError: Install failed with exit code 1; see /var/log/installer/syslog and /var/log/syslog

I did not manually edit the partition table though. I was trying to install 6.06LTS on a system that had a 40 GB IDE drive of which about 12 GB was allocated to an NTFS partition for Windows 2000. I left the rest of the disk unpartitioned and when the Ubuntu installer got to the partitioning phase, I let it do what it wanted - seemingly to use the remaining space for an ext3 partition and a swap partition. Install went well for a while and then crashed at 81%.

Here's the partition info from fdisk:

Disk /dev/hda: 41.1 GB, 41110142976 bytes
255 heads, 63 sectors/track, 4998 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot Start End Blocks Id System
/dev/hda1 1 1507 12104946 7 HPFS/NTFS
/dev/hda2 * 1508 4852 26868712+ 83 Linux
/dev/hda3 4853 4998 1172745 5 Extended
/dev/hda5 4853 4998 1172713+ 82 Linux swap / Solaris

Revision history for this message
Marc Abramowitz (msabramo) wrote : /var/log/installer/syslog

/var/log/installer/syslog after installer crash.

Revision history for this message
Marc Abramowitz (msabramo) wrote : /var/log/syslog

/var/log/syslog after installer crash

Revision history for this message
Marc Abramowitz (msabramo) wrote : /var/log/partman

/var/log/partman after installer crash.

Revision history for this message
Marc Abramowitz (msabramo) wrote :

I tried a couple more times and it is continuing to fail. Since the first attempt created the partitions, all later attempts no longer offered the option for Ubuntu to choose the partitioning scheme. Only choices were to let Ubuntu use the whole disk or to manually edit the partition table. Naturally I chose the latter. This also eventually causes a crash during file copying. Nice thing is that the unusable /dev/hda2 ext3 partition is set bootable so the system is not bootable, including Windows. I fixed this by booting into the live CD and using fdisk to turn off the boot flag for /dev/hda2 and turn it on for the /dev/hda1 NTFS partition. This restored my ability to boot Windows.

Revision history for this message
Henri Tuhola (henri-tuhola) wrote :

This crashed with me as well.

I found these lines unique and intresting from installer/syslog:
/lib/partman/recipes.sh: line 31: local: `-': not a valid identifier
/lib/partman/recipes.sh: line 114: local: `-': not a valid identifier

I believe these two lines are causing the final crash.

Could somebody descbribe why that shell script is crashing, and possibly tell how to turnaround the problem?

Is Churusaa right in this point? Should I allow the installer partition by its own? I've nothing important on my harddisks.

Revision history for this message
Henri Tuhola (henri-tuhola) wrote : attachment to recipes.sh

This is the recipes.sh in /lib/partman/. I included it for easy examination for possible helpful people.

Revision history for this message
Fred Gauthier (frederic-gauthier-boutin) wrote :

DaNg ! I'm so desapointed... all these backup for nothing.

I tried to manualy manage my disks and partitions in QTParted... but it appear that even when formating them, nothing is done.

Maybe there's something with ReiserFS file system. I guess.

Revision history for this message
Przemek K. (azrael) wrote : /var/log/installer/syslog (another one)

Another log from installer crash

Revision history for this message
Przemek K. (azrael) wrote : /var/log/syslog (another one)

Another log from installer crash

Revision history for this message
Przemek K. (azrael) wrote : /var/log/partman (another one)

Another log from installer crash

Revision history for this message
Przemek K. (azrael) wrote :

Above logs are mine. I tried to install Kubuntu on my old PC (Athlon 1.1, 768MB RAM, GF FX 5200, 2xHD: 80GB & 20GB) - I tried to install Kubuntu on the second drive where I also have SLED10RC3 (reiserfs) and FC5 (ext3), the partition I created by installer for Kubuntu was xfs (I was curious if it was going to work).

Revision history for this message
Przemek K. (azrael) wrote :

Without restarting the livecd I tried once again and this time I chose ext3 and installation worked fine.

Revision history for this message
Fred Gauthier (frederic-gauthier-boutin) wrote :

SOLUTION : EXT3 file system

NOTE: After manually setup your partitions with the wizzard, don't bored your self with no data refresh. If at next page the "format" checkboxes appear in gray (disabled)... the installation should work.

Revision history for this message
husan (hx) wrote :

same problem,

Traceback (most recent call last):
  File "/usr/bin/ubiquity", line 130, in ?
    install(sys.argv[1])
  File "/usr/bin/ubiquity", line 55, in install
    ret = wizard.run()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/gtkui.py", line 266, in run
    self.process_step()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/gtkui.py", line 741, in process_step
    self.mountpoints_to_summary()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/gtkui.py", line 1029, in mountpoints_to_summary
    self.progress_loop()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/gtkui.py", line 538, in progress_loop
    raise RuntimeError, ("Install failed with exit code %s; see "
RuntimeError: Install failed with exit code 1; see /var/log/installer/syslog and /var/log/syslog

Revision history for this message
EngiBenchi (dejongester) wrote :

I have almost the same crash log.

Traceback (most recent call last):
  File "/usr/bin/ubiquity", line 130, in ?
    install(sys.argv[1])
  File "/usr/bin/ubiquity", line 55, in install
    ret = wizard.run()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/kde-ui.py", line 311, in run
    self.process_step()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/kde-ui.py", line 731, in process_step
    self.gparted_to_mountpoints()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/kde-ui.py", line 804, in gparted_to_mountpoints
    print >>self.qtparted_subp.stdin, "apply"
AttributeError: 'NoneType' object has no attribute 'stdin'

I'll tried to install kubuntu manually but at t the moment i had to start to make a partition the crash occurred.
i have a win xp partion and a linux swap file, a linux ext3 partion and a empty part on the disk plus a grub bootloader.

Revision history for this message
A. Daniel Sasson (adsasson) wrote :

Same experience. Manually edited partition table. Already had a Win partition and a previous Ubuntu disk (separate devices) already partitioned, including a jfs partition

Text as follows:
Traceback (most recent call last):
  File "/usr/bin/ubiquity", line 130, in ?
    install(sys.argv[1])
  File "/usr/bin/ubiquity", line 55, in install
    ret = wizard.run()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/gtkui.py", line 266, in run
    self.process_step()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/gtkui.py", line 741, in process_step
    self.mountpoints_to_summary()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/gtkui.py", line 1029, in mountpoints_to_summary
    self.progress_loop()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/gtkui.py", line 538, in progress_loop
    raise RuntimeError, ("Install failed with exit code %s; see "
RuntimeError: Install failed with exit code 1; see /var/log/installer/syslog and /var/log/syslog

Revision history for this message
A. Daniel Sasson (adsasson) wrote :

/var/log/syslog

Revision history for this message
A. Daniel Sasson (adsasson) wrote :

/var/log/partman

Revision history for this message
Johnny (xbitman) wrote : Me too

Traceback (most recent call last):
  File "/usr/bin/ubiquity", line 130, in ?
    install(sys.argv[1])
  File "/usr/bin/ubiquity", line 55, in install
    ret = wizard.run()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/gtkui.py", line 264, in run
    self.progress_loop()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/gtkui.py", line 538, in progress_loop
    raise RuntimeError, ("Install failed with exit code %s; see "
RuntimeError: Install failed with exit code 1; see /var/log/installer/syslog and /var/log/syslog

Revision history for this message
Johnny (xbitman) wrote : /var/log/installer/syslog
Revision history for this message
Johnny (xbitman) wrote : /var/log/syslog
Revision history for this message
Johnny (xbitman) wrote : /var/log/partman
Revision history for this message
Johnny (xbitman) wrote : Screenshot
Revision history for this message
Colin Watson (cjwatson) wrote :

Kyle, thanks for your report. At present, you must reformat system partitions (e.g. /, /boot, /usr, or /var) during installation; bug 47046 is filed to note that the partitioner should warn you about this up-front. If you are upgrading an existing installation, then please see http://wiki.ubuntu.com/DapperUpgrades rather than using this installer.

Everyone else who's been piling into this bug: please file new bugs about installer crashes rather than tagging your information onto an existing bug. Only two of two have the same issue as the original reporter, and I suspect that was more by luck than judgement. Installer crash bugs where lots of people pile in with differing problems very quickly turn into a nightmare for me to unpick.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

To post a comment you must log in.