New Feisty (Jan 12) can't install

Could you please attach /var/log/syslog and /var/log/partman to this bug, following the directions in http://wiki.ubuntu.com/DebuggingUbiquity/AttachingLogs? Thanks in advance.

VAR/SYS LOG is...

Jan 12 09:35:10 steve-desktop syslogd 1.4.1#18ubuntu6: restart.
Jan 12 09:35:10 steve-desktop anacron[4374]: Job `cron.daily' terminated
Jan 12 09:35:10 steve-desktop anacron[4374]: Normal exit (1 job run)
Jan 12 09:38:17 steve-desktop gconfd (root-5253): starting (version 2.16.0), pid 5253 user 'root'
Jan 12 09:38:17 steve-desktop gconfd (root-5253): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0
Jan 12 09:38:17 steve-desktop gconfd (root-5253): Resolved address "xml:readwrite:/root/.gconf" to a writable configuration source at position 1
Jan 12 09:38:17 steve-desktop gconfd (root-5253): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2
Jan 12 09:38:17 steve-desktop gconfd (root-5253): Resolved address "xml:readonly:/var/lib/gconf/debian.defaults" to a read-only configuration source at position 3
Jan 12 09:38:17 steve-desktop gconfd (root-5253): Resolved address "xml:readonly:/var/lib/gconf/defaults" to a read-only configuration source at position 4
Jan 12 09:38:47 steve-desktop gconfd (root-5253): SIGHUP received, reloading all databases
Jan 12 09:38:47 steve-desktop gconfd (root-5253): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0
Jan 12 09:38:47 steve-desktop gconfd (root-5253): Resolved address "xml:readwrite:/root/.gconf" to a writable configuration source at position 1
Jan 12 09:38:47 steve-desktop gconfd (root-5253): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2
Jan 12 09:38:47 steve-desktop gconfd (root-5253): Resolved address "xml:readonly:/var/lib/gconf/debian.defaults" to a read-only configuration source at position 3
Jan 12 09:38:47 steve-desktop gconfd (root-5253): Resolved address "xml:readonly:/var/lib/gconf/defaults" to a read-only configuration source at position 4
Jan 12 09:38:47 steve-desktop gconfd (root-5253): GConf server is not in use, shutting down.
Jan 12 09:38:47 steve-desktop gconfd (root-5253): Exiting
Jan 12 09:55:10 steve-desktop -- MARK --
Jan 12 10:15:10 steve-desktop -- MARK --
Jan 12 10:17:01 steve-desktop /USR/SBIN/CRON[6307]: (root) CMD ( run-parts --report /etc/cron.hourly)
Jan 12 10:35:10 steve-desktop -- MARK --
Jan 12 10:55:10 steve-desktop -- MARK --
Jan 12 11:15:11 steve-desktop -- MARK --
Jan 12 11:17:01 steve-desktop /USR/SBIN/CRON[7744]: (root) CMD ( run-parts --report /etc/cron.hourly)
Jan 12 11:35:11 steve-desktop -- MARK --
Jan 12 11:55:11 steve-desktop -- MARK --
Jan 12 12:15:11 steve-desktop -- MARK --
Jan 12 12:17:01 steve-desktop /USR/SBIN/CRON[9202]: (root) CMD ( run-parts --report /etc/cron.hourly)
Jan 12 12:35:11 steve-desktop -- MARK --
Jan 12 12:55:11 steve-desktop -- MARK --
Jan 12 13:05:43 steve-desktop kernel: [17192570.176000] cdrom: This disc doesn't have any tracks I recognize!
Jan 12 13:07:27 steve-desktop kernel: [17192674.660000] scsi: unknown opcode 0x01
Jan 12 13:17:02 steve-desktop /USR/SBIN/CRON[10884]: (root) CMD ( run-parts --report /etc/cron.hourly)
Jan 12 13:30:16 steve-desktop gconfd (...

I have no VAR/LOG/PARTMAN file (!)

Steve K, in Feisty, the right path to partman log is:
/var/log/installer/partman

You should also attach (better than add as comment) syslog from the installer, which is also stored on new location:
/var/log/installer/syslog

Sorry, have stuffed this up. Now realise that you wanted the file logs created while running the Live CD. Will send these in next week, when am back at work.

Thanks

Hi Steve,

Any progress on getting these logs? I'd also suggest testing with a current image, as a lot of partitioning problems have been fixed since then.

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Hardy Heron. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help.

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. 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!