Ubuntu
ubiquity package

crash on ARM at the end of install

Bug #871785 reported by Jani Monoses
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Fix Released
High
Ubuntu Installer Team
Precise
Fix Released
High
Ubuntu Installer Team

Bug Description

On the preinstalled Ubuntu ARM images sometimes ubiquity, oem-config oem-config-gtk and jasper are not removed so they get rerun on every reboot until manually removed.
Last noticed on the Oneiric mx5 image of Oct 9

Revision history for this message
Jani Monoses (jani) wrote :
Changed in ubiquity (Ubuntu):
assignee: nobody → Canonical ARM (canonical-arm)
Revision history for this message
Jani Monoses (jani) wrote :
Revision history for this message
Jani Monoses (jani) wrote :
Revision history for this message
Jani Monoses (jani) wrote :
Revision history for this message
Jani Monoses (jani) wrote :
Revision history for this message
Jani Monoses (jani) wrote :
Revision history for this message
Jani Monoses (jani) wrote :
Revision history for this message
Adam Conrad (adconrad) wrote :

Pretty sure this is oem-config-remove-gtk suffering a dbus timeout to aptdaemon, however I'm not entirely sure how to fix it. Talking to mvo.

Brian Murray (brian-murray)
Changed in ubiquity (Ubuntu):
importance: Undecided → Medium
importance: Medium → High
Ubuntu Foundations Team Bug Bot (crichton)
tags: added: ubiquity-2.8.4
tags: added: oneiric
Revision history for this message
Jani Monoses (jani) wrote :

The whole /var/log dir tarball after the installer crashed but no reboot/X restart having taken place.
Previously I got a new ubitquity started as I set autologin on during the install phase.

Nothing in /var/crash

Revision history for this message
nooperation (nooperation) wrote :

On the preinstalled ARM (OMAP4) package (currently the Oneiric Ocelot release version) for Pandaboard I can reproduce a crash each time I try to change the keyboard settings at the initial setup procedure. If I don't try to change it, I might get it through the setup process (but not every time). If it fails I normally end up with a 'read-only filesystem'.
I currently don't have any logs I could attach. I think at the release notes I read something about race conditions of the kernel but I'm not sure if that's the same problem.

Tobin Davis (gruemaster)
Changed in ubiquity (Ubuntu):
assignee: Canonical ARM (canonical-arm) → Ubuntu Installer Team (ubuntu-installer)
Ubuntu QA Website (ubuntuqa)
tags: added: iso-testing
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote : ISO tracker notification

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/871785

Kate Stewart (kate.stewart)
tags: added: rls-mgr-p-tracking
Revision history for this message
Stéphane Graber (stgraber) wrote :

Is that still happening on Precise?
If so, can you please attach up to date log files?

Revision history for this message
Tobin Davis (gruemaster) wrote :

Closing as "Fix released". This was fixed in Precise Alpha 1.

Changed in ubiquity (Ubuntu Precise):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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