ubiquity panel crashed with a segfault during oem-config-remove step

Bug #924456 reported by Tobin Davis on 2012-01-31
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Undecided
Unassigned

Bug Description

Ubiquity panel crashed during oem-config-remove step on omap4 preinstalled desktop image. Not much else to go on.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: ubiquity-frontend-gtk 2.9.15
ProcVersionSignature: Ubuntu 3.2.0-1405.7-omap4 3.2.1
Uname: Linux 3.2.0-1405-omap4 armv7l
ApportVersion: 1.91-0ubuntu1
Architecture: armel
Date: Tue Jan 31 11:18:41 2012
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

Tobin Davis (gruemaster) wrote :
Ubuntu QA Website (ubuntuqa) wrote :

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/924456

tags: added: iso-testing
Changed in ubiquity (Ubuntu):
assignee: nobody → Canonical Foundations Team (canonical-foundations)
Brian Murray (brian-murray) wrote :

Is there a crash file for this crash in /var/crash on the system? This is the location where crashes get written by apport and having the file would help us debug the issue - without details about the crash there isn't much we can do.

Changed in ubiquity (Ubuntu):
status: New → Incomplete
Tobin Davis (gruemaster) wrote :

Crash file didn't have much in it, and apport-bug wouldn't deal with it because the packages had been uninstalled. Reinstalling the packages didn't help either with filing the bug.

I'm going to leave this as incomplete because I am not able to reproduce it with the current daily images, so it may have resolved itself.

Brian Murray (brian-murray) wrote :

Setting to invalid as it has not been recreated.

Changed in ubiquity (Ubuntu):
assignee: Canonical Foundations Team (canonical-foundations) → nobody
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers