Installer crashes in partitioning

Bug #107234 reported by Kjetil Kjernsmo
2
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Invalid
Undecided
Colin Watson

Bug Description

I just tried Feisty, and I don't have the box online, so it is cumbersome to provide you the information and I'm in an awful rush.

However, I'm pretty sure I have observed twice now that the installer crashes if you click "new partition" if "free space" isn't highlighted...

Revision history for this message
Brian Murray (brian-murray) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. You should have received a crash report dialog if that is the case. Do you recall seeing one? Thanks in advance.

Revision history for this message
Kjetil Kjernsmo (kjetil) wrote :

Yup, there was a crash report dialog telling me to file a bug and attach a couple of logs. Sorry, I don't have the logs, but the system is up and running now, it worked if I was careful to always highlight "free space".

If it is likely that the logs are kept on the finished system, please remind me what they were called and I'll dig.

Revision history for this message
Brian Murray (brian-murray) wrote :

Crash reports are kept in the '/var/crash' directory and you might find one there with ubiquity in the file name.

Revision history for this message
Kjetil Kjernsmo (kjetil) wrote :

Sorry, /var/crash is empty on my system, and I didn't find anything else either.

Revision history for this message
Colin Watson (cjwatson) wrote :

The logs should be in /var/log/installer/ (specifically /var/log/installer/syslog).

Is it possible that you were using the Kubuntu 7.04 beta?

Changed in ubiquity:
assignee: nobody → kamion
status: Unconfirmed → Needs Info
Revision history for this message
Henrik Nilsen Omma (henrik) wrote :

Hei Kjetil!
(I believe we know each other from astro.uio.no)

If you did a clean install using different settings then the crash and log files will indeed be lost. If you'd like to help us track this down you'd need to attempt the install again, retracing you steps and catch the logs. You should be able to save them to a USB key or floppy if available. A screen shot of the dialog just before the crash would also be helpful. Thanks.

Revision history for this message
Kjetil Kjernsmo (kjetil) wrote : Re: [Bug 107234] Re: Installer crashes in partitioning

On Sunday 03 June 2007, Henrik Nilsen Omma wrote:
> Hei Kjetil!
> (I believe we know each other from astro.uio.no)

Hi there! Yes, that's right! Nice to hear that you're working for
Ubuntu!

> If you did a clean install using different settings then the crash
> and log files will indeed be lost. If you'd like to help us track
> this down you'd need to attempt the install again,

Hmmmm, I think that's hard... The system in question is now my main work
system and I don't have the time to back it up and reinstall, nor do I
have a system right now I can try another install. So, I'm afraid
that's hard...

Presumably, the crash is related to the hardware I have, a Compal HGL30
notebook. It was 100% reproducible on this system, but I have not tried
any other systems. And it did turn out to be as simple as I described
in my original report, clicking "new partition" when "free space" was
not highlighted. If this works for you, then I would simply close the
bug.

Cheers,

Kjetil
--
Kjetil Kjernsmo
Programmer / Astrophysicist / Ski-orienteer / Orienteer / Mountaineer
<email address hidden>
Homepage: http://www.kjetil.kjernsmo.net/ OpenPGP KeyID: 6A6A0BBC

Revision history for this message
Henrik Nilsen Omma (henrik) wrote :

I wasn't able to reproduce this on my virtualbox setup, though the drive I used didn't have free space on it (not sure if it needs to. I'll leave it open for now and do some more testing during the Tribe 1 release process.

Michael Losonsky (michl)
Changed in ubiquity:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.