VM Kubuntu 9.10 Installer crashes in VMware Workstation 6.5.3

[Seegorkesolot]

Binary package hint: ubiquity

Traceback (most recent calls)
File "/usr/lib/ubiquity/frontend/kde_ui.py", line 410, in <lambda> QTimer.singleShot(0, lambda: self.dbfilter.start(auto_process=True))
File "/usr/lib/ubiquity/filteredcommand.py", line 87, in start self.db = DebconfCommunicator(PACKAGE, cloexec=True)
File "/usr/lib/ubiquity/ubiquity/debconfcommunicator.py", line 35, in __init__ write=self.dccomm.stdin)
File "/usr/lib/python2.6/dist-packages/debconf.py", line 53, in __init__ self.setUp(title)
File "/usr/lib/python2.6/dist-packages/debconf.py", line 56, in setUP self.version = self.version(2)
File "/usr/lib/python2.6/dist-packages/debconf.py", line 65, in <lambda> lambda *args, **kw: self.command(command, *args, **kw))
File "/usr/lib/python2.6/dist-packages/debconf.py", line 86, in command status = int(status)
ValueError: invalid literal for int() with base 10: "

I tipped the error messages from the VM (copying was not possible), so there are maybe some typos in it. Unfortunatly, I cannot append /var/syslog and /var/log/partman at the moment, as they are stored on the VM. I will setup another functioning one (Ubuntu 9.10), copy and append them here if necessary.

The error is reproduceable the following way:
- Try installing Kubuntu 9.10 as VM in VMware Workstation 6.5.3 under Windows
- Choose the "Easy Install" option and accept the default values

A manual install the usual way without using Easy Install with the same .iso file works without any problems.

[Monkey (monkey-libre)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't start working on it yet, because your description didn't include enough information.

Please include the information requested at https://wiki.ubuntu.com/DebuggingUbiquity/AttachingLogs as separate attachments by visiting your bug's web page. Thanks in advance.

[Monkey (monkey-libre)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comment. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!