Bug #42774 “Installer Crash: ValueError: invalid literal for int...” : Bugs : ubiquity package : Ubuntu

Revision history for this message

Colin Watson (cjwatson) wrote on 2006-05-03:

#1

What were you doing when this problem occurred?

Can you attach /var/log/installer/syslog to this bug?

Changed in ubiquity:
status:	Unconfirmed → Needs Info

Revision history for this message

Esben Mose Hansen (kubuntu-mosehansen) wrote on 2006-05-04:

#2

I am not the original reporter, but I got this exact backtrace exactly after clicking next on the very first page of the wizard. In other words, steps to reproduce:
1. boot
2. Click install
3. Click next
4. crash

Was 100% reproducible.

I'll get on attaching that syslog as soon as I can.

Keep up the good work... Kubuntu looks awsome on the live CD :D

Revision history for this message

Simon Law (sfllaw) wrote on 2006-05-11:

#3

Thanks for the bug report. This particular bug has already been
reported into our bug tracking system, but please feel free to report
any further bugs which you find.

Changed in ubiquity:
status:	Needs Info → Rejected

Revision history for this message

Colin Watson (cjwatson) wrote on 2006-05-11:

#4

It's not obvious to me that this is quite the same as bug 39062. In any event I certainly intend to do different things with 39062 ...

Changed in ubiquity:
status:	Rejected → Unconfirmed

Revision history for this message

Manuel López-Ibáñez (manuellopezibanez) wrote on 2006-06-07:

#5

Could you please attach /var/log/installer/syslog, /var/log/syslog, and /var/log/partman to this bug, using the "Add Attachment" link on the bug's web page? Thanks in advance.

Changed in ubiquity:
status:	Unconfirmed → Needs Info

Revision history for this message

Chris Hecker (christopher-hecker-gmail) wrote on 2006-07-29:

#6

Syslog file Edit (9.2 KiB, text/plain)

I'm getting the same bug as well. Judging from this report, the 6.06 fix to #39062 didn't fix this.

The traceback follows; the requested files are attached.

FWIW, I'm running an AMD Athlon64 system with 1GB of memory, and downloaded the 64-bit install CD.

Regards,

Chris.

--- traceback ---
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 299, in run
    self.dbfilter.start(auto_process=True)
  File "/usr/lib/python2.4/site-packages/ubiquity/filteredcommand.py", line 45, in start
    self.db = DebconfCommunicator(PACKAGE, 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():

Revision history for this message

Chris Hecker (christopher-hecker-gmail) wrote on 2006-07-29:

#7

attachment corresponding to previous traceback. Edit (54.9 KiB, text/plain)

Revision history for this message

Chris Hecker (christopher-hecker-gmail) wrote on 2006-07-29:

#8

One more note: the /var/log/partman file is empty, even after the installer crash.

Revision history for this message

Mark Janney (markjanney) wrote on 2006-11-05:

#9

Contents of requested log files Edit (208.3 KiB, text/plain)

Download full text (4.2 KiB)

I experienced the same problem trying to install Ubuntu 6.0.6. LTS from the Live CD. [I downloaded and burned the ISO image. It's self-check passed]

My computer is a Presario 5000Z-1.0 GHz circa 2001
(Full specs at http://h10025.www1.hp.com/ewfrf/wc/document?docname=c00008665&lc=en&cc=us&dlc=en&product=239426)
I have upgraded this machine in four ways: (a) maxed out the RAM to 768 MB, (b) replaced the original HD with a 80 GB parallel ATA drive, (c) Added a 300 GB SATA drive accesssed through a PCI bus multi-function card, (d) replaced the original video card with a WinFast GeForce2 Ultra.

The 80 GB drive is configured to dual boot both WinME and WinXP. (I use WinME to play certain video games that never migrated to XP). The primary partition is a 5 GB FAT 32 partition for WinME. The extended partition contains a 30 GB NTFS partition for WinXP, and a 1 GB NTFS partition for burning CDs. The rest of the drive is free space.

The 300 GB SATA drive was partitioned into 60 GB primary partition and a 300 GB extended partition split into two logical drives of 150 GB each. All partitions used NTFS.

My plan was to install Ubuntu on the primary partition of the SATA drive, and then select Ubuntu by selecting the SATA drive as the boot HD via my BIOS.

So, I booted Ubuntu from the Live CD and fired up the installer. I chose the manual partitioning becuase I have data in the extended partiton that I didn't want to trash. I used the 'resize' and 'new' operations to split the original 60 GB primary partition into a 1.5 GB swap partition (formatted as 'linux-swap' and a 58.5 boot partition (which in my ignorance I left as NTFS). The installer completed without complaint but nothing was written to the boot partition. After some reading I learned that Linux can't write NTFS file systems and I needed to format the boot partition as Ext3.

Armed with this knowledge, I boot again from the Live CD and fire up the installer. I split the 58.5 GB boot partition into a 15 GB boot partition (for / and /boot) and a 43.5 GB partition (for /home). Both partitions were to be formatted as Ext3. When I tried to go from page 5 to page 6 of the installer, I got the following crash message. (I have attached the requested logs in a single file, CrashLogs.txt. The log contents re separated by a delimiter '===== <filename> ====' ).
---------------
We're sorry; the installer crashed. Please file a new bug report at https://launchpad.net/distros/ubuntu/+source/ubiquity/+filebug (do not attach your details to any existing bug) and a developer will attend to the problem as soon as possible. To help the developers understand what went wrong, include the following detail in your bug report, and attach the files /var/log/installer/syslog, /var/log/syslog, and /var/log/partman:

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 755, in process_step
    self.mountpoints_to_su...

I experienced the same problem trying to install Ubuntu 6.0.6. LTS from the Live CD. [I downloaded and burned the ISO image. It's self-check passed]

My computer is a Presario 5000Z-1.0 GHz circa 2001
(Full specs at http://h10025.www1.hp.com/ewfrf/wc/document?docname=c00008665&lc=en&cc=us&dlc=en&product=239426)
I have upgraded this machine in four ways: (a) maxed out the RAM to 768 MB, (b) replaced the original HD with a 80 GB parallel ATA drive, (c) Added a 300 GB SATA drive accesssed through a PCI bus multi-function card, (d) replaced the original video card with a WinFast GeForce2 Ultra.

The 80 GB drive is configured to dual boot both WinME and WinXP. (I use WinME to play certain video games that never migrated to XP). The primary partition is a 5 GB FAT 32 partition for WinME. The extended partition contains a 30 GB NTFS partition for WinXP, and a 1 GB NTFS partition for burning CDs. The rest of the drive is free space.

The 300 GB SATA drive was partitioned into 60 GB primary partition and a 300 GB extended partition split into two logical drives of 150 GB each. All partitions used NTFS.

My plan was to install Ubuntu on the primary partition of the SATA drive, and then select Ubuntu by selecting the SATA drive as the boot HD via my BIOS.

So, I booted Ubuntu from the Live CD and fired up the installer. I chose the manual partitioning becuase I have data in the extended partiton that I didn't want to trash.  I used the 'resize' and 'new' operations to split the original 60 GB primary partition into a 1.5 GB swap partition (formatted as 'linux-swap' and a 58.5 boot partition (which in my ignorance I left as NTFS).  The installer completed without complaint but nothing was written to the boot partition.  After some reading I learned that Linux can't write NTFS file systems and I needed to format the boot partition as Ext3.

Armed with this knowledge, I boot again from the Live CD and fire up the installer. I split the 58.5 GB boot partition into a 15 GB boot partition (for / and /boot) and a 43.5 GB partition (for /home). Both partitions were to be formatted as Ext3.  When I tried to go from page 5 to page 6 of the installer, I got the following crash message. (I have attached the requested logs in a single file, CrashLogs.txt. The log contents re separated by a delimiter '===== <filename> ===='  ).
---------------
We're sorry; the installer crashed. Please file a new bug report at https://launchpad.net/distros/ubuntu/+source/ubiquity/+filebug (do not attach your details to any existing bug) and a developer will attend to the problem as soon as possible. To help the developers understand what went wrong, include the following detail in your bug report, and attach the files /var/log/installer/syslog, /var/log/syslog, and /var/log/partman:

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 755, in process_step
    self.mountpoints_to_summary()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/gtkui.py", line 1101, in mountpoints_to_summary
    if partman_commit.PartmanCommit(self).run_command(auto_process=True) != 0:
  File "/usr/lib/python2.4/site-packages/ubiquity/filteredcommand.py", line 128, in run_command
    self.start(auto_process=auto_process)
  File "/usr/lib/python2.4/site-packages/ubiquity/filteredcommand.py", line 45, in start
    self.db = DebconfCommunicator(PACKAGE, 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(): 
-------------

Revision history for this message

Mark Janney (markjanney) wrote on 2006-11-06: Re: Installer Crash: A Possible Cause

#10

It's possible that the problem is caused by moving back and forth between screens 5 and 6 of the installer. Here's why:

I was able to install Ubuntu on the system described in my previous comment (2006-11-05 08:43:56 UTC). In this successful sequence I did not go back from screen 6 to screen 5. (Screen 6 is the one that shows your configuration and asks for confirmation before actually installing files. Screen 5 is the screen that allows manual adjustment of partitions).

In the previous attempt (described in the previous comment), I had moved back and forth several times because I wasn't sure which partition name ('sda5', 'sda6', etc.) was assigned to each of my newly created primary partitions.

I still have my old 40 GB drive. If I find time, I'll use it to test this hypothesis.

Revision history for this message

Colin Watson (cjwatson) wrote on 2007-03-26:

#11

It's not entirely clear why debconf failed to acquire the lock here. Perhaps another instance was running somewhere, or perhaps something else unclear went wrong.

This change (which was NOT in time for the Feisty beta release, but will be in all future releases, including Feisty final) fixes one major known cause of this problem, namely that if the attempt to lock the file was unlucky enough to be interrupted by delivery of a signal then it wouldn't be retried. Even if that wasn't the problem here, debconf will now print more information which may help to determine the real cause of the problem. Thus, I do still welcome reports of this bug from users of more recent versions of Feisty than the beta.

debconf (1.5.13ubuntu1) feisty; urgency=low

  * Resynchronise with Debian. Remaining changes:
    - Install Python confmodule for python2.5 as well.
  * Retry flock() on EINTR. Failing that, print the errno if flock() fails
    so that we have a better chance of working out why.
  * Set Maintainer to me for DebianMaintainerField (even though I'm part of
    the maintenance team upstream ...).

-- Colin Watson <email address hidden> Fri, 23 Mar 2007 10:16:04 +0000

Changed in ubiquity:
assignee:	nobody → kamion
status:	Needs Info → Fix Released

Ubuntu
ubiquity package

Installer Crash: ValueError: invalid literal for int()

Bug Description

Duplicates of this bug

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntuubiquity package

Installer Crash: ValueError: invalid literal for int()

Bug Description

Duplicates of this bug

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
ubiquity package