two debconf frontends active in progress_loop

[Pranas]

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():

[John Vivirito (gnomefreak)]

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.

[Pranas (pranas-baliuka)]

----- Original Message -----
From: "John Vivirito" <email address hidden>
To: <email address hidden>
Sent: Monday, July 17, 2006 7:15 PM
Subject: [Bug 53213] Re: Installer Crashed on ASUS Vintage 2-AE1

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 (Ubuntu)
       Status: Unconfirmed => Needs Info

--
Installer Crashed on ASUS Vintage 2-AE1
https://launchpad.net/bugs/53213

/bin/partman: *******************************************************
/lib/partman/init.d/01unsupported: *******************************************************
/lib/partman/init.d/30parted: *******************************************************
parted_server: ======= Starting the server
parted_server: main_loop: iteration 1
parted_server: Opening infifo
/lib/partman/init.d/30parted: IN: OPEN =dev=sda /dev/sda
parted_server: Read command: OPEN
parted_server: command_open()
parted_server: Request to open =dev=sda
parted_server: Opening outfifo
parted_server: OUT: OK

parted_server: OUT: OK

parted_server: Note =dev=sda as unchanged
parted_server: Closing infifo and outfifo
parted_server: main_loop: iteration 2
parted_server: Opening infifo
/lib/partman/init.d/35dump: *******************************************************
/lib/partman/init.d/35dump: IN: DUMP =dev=sda
parted_server: Read command: DUMP
parted_server: command_dump()
parted_server: Opening outfifo
parted_server: OUT: OK

parted_server: Closing infifo and outfifo
parted_server: main_loop: iteration 3
parted_server: Opening infifo
Device: yes
Model: ATA SAMSUNG SP2004C
Path: /dev/sda
Sector size: 512
Sectors: 390721968
Sectors/track: 63
Heads: 255
Cylinders: 24321
Partition table: yes
Type: msdos
Partitions: # id length type fs path name
(0,0,0) (0,0,62) -1 0-32255 32256 primary label /dev/sda-1
(0,1,0) (24319,254,62) 1 32256-200038809599 200038777344 primary unknown /dev/sda1
(24320,0,0) (24320,254,62) -1 200038809600-200047034879 8225280 pri/log free /dev/sda-1
(24321,0,0) (24321,80,62) -1 200047034880-200049647615 2612736 primary label /dev/sda-1
Dump finished.
/lib/partman/init.d/70update_partitions: *******************************************************
/lib/partman/init.d/70update_partitions: IN: PARTITIONS =dev=sda
parted_server: Read command: PARTITIONS
parted_server: command_partitions()
parted_server: Opening outfifo
parted_server: OUT: OK

parted_server: OUT: 1 32256-200038809599 200038777344 primary unknown /dev/sda1

parted_server: OUT: -1 200038809600-200047034879 8225280 pri/log free /dev/sda-1

parted_server: Partitions printed
parted_server: OUT:

parted_server: Closing infifo and outfifo
parted_server: main_loop: iteration 4
parted_server: Opening infifo
/lib/partman/update.d/20bootable: *******************************************************
/lib/partman/update.d/20bootable: IN: GET_FLAGS =dev=sda 32256-200038809599
parted_server: Read command: GET_FLAGS
parted_server: command_get_flags()
parted_server: Opening outfifo
parted_server: partition_with_id(32256-200038809599)
parted_server: Partition found (32256-20003880...

[John Vivirito (gnomefreak)]

Could you please attach /var/log/installer/syslog, /var/log/syslog. Thank you for sending the partman file but we still need the 2 above. Please try to use the "Add Attachment" link on the bug's web page.

[Pranas (pranas-baliuka)]

Hello,

Please find installer syslog. Will try to recreate situation and attach
additional /var/log/syslog later on.

Thank you
Pranas
----- Original Message -----
From: "John Vivirito" <email address hidden>
To: <email address hidden>
Sent: Wednesday, July 19, 2006 9:44 PM
Subject: [Bug 53213] Re: Installer Crashed on ASUS Vintage 2-AE1

Could you please attach /var/log/installer/syslog, /var/log/syslog.
Thank you for sending the partman file but we still need the 2 above.
Please try to use the "Add Attachment" link on the bug's web page.

--
Installer Crashed on ASUS Vintage 2-AE1
https://launchpad.net/bugs/53213

Ubiquity 1.0.12
X Error: BadDevice, invalid or uninitialized input device 171
  Major opcode: 146
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 171
  Major opcode: 146
  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 171
  Major opcode: 146
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 171
  Major opcode: 146
  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!
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_updateq7BmPa.tmp:1
ubiquity: Starting up '['/usr/lib/ubiquity/localechooser/localechooser']' for ubiquity.components.language.Language
ubiquity: Watching for question patterns ^languagechooser/language-name
Wed, 19 Jul 2006 18:13:30 INFO Step_before = stepLanguage
Wed, 19 Jul 2006 18:13:31 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$
Wed, 19 Jul 2006 18:13:33 INFO Step_before = stepLocation
Wed, 19 Jul 2006 18:13:33 INFO Step_after = stepKeyboardConf
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: kbd-chooser prepare
ubiquity: Starting up '['/bin/sh', '-c', '. /usr/share/debconf/confmodule; exec /usr/lib/ubiquity/kbd-chooser/kbd-c...

[Henrik Nilsen Omma (henrik)]

We are seeing a large number of these bugs (which we are tagging as debconf-frontend-crash). While we are not 100% that they all have the same cause (we have not yet found the cause) we are grouping them together as duplicates.