frontend crashed with SIGABRT in raise()

Bug #1046347 reported by Paul Larson
This bug affects 1 person
Affects Status Importance Assigned to Milestone
debconf (Ubuntu)

Bug Description

Installing Quantal beta 20120904.1 on panda, it got part way through the install and hit this. Looking to see if I can reproduce it now.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: debconf 1.5.46ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-209.15-omap4 3.5.2
Uname: Linux 3.5.0-209-omap4 armv7l
ApportVersion: 2.5.1-0ubuntu4
Architecture: armhf
CasperVersion: 1.321
Date: Wed Sep 5 08:57:10 2012
ExecutablePath: /usr/share/debconf/frontend
InterpreterPath: /usr/bin/perl
LiveMediaBuild: Ubuntu 12.10 "Quantal Quetzal" - Alpha armhf+omap4 (20120904.1)
PackageArchitecture: all
ProcCmdline: /usr/bin/perl -w /usr/share/debconf/frontend /var/lib/dpkg/info/dictionaries-common.postinst triggered update-default-wordlist
 PATH=(custom, no user)
Signal: 6
SourcePackage: debconf
 ?? () from /lib/arm-linux-gnueabihf/
 raise () from /lib/arm-linux-gnueabihf/
 abort () from /lib/arm-linux-gnueabihf/
 ?? () from /lib/arm-linux-gnueabihf/
 ?? () from /lib/arm-linux-gnueabihf/
Title: frontend crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Paul Larson (pwlars) wrote :
visibility: private → public
Revision history for this message
Paul Larson (pwlars) wrote :

Unable to reproduce this, and I'm pretty sure it was bogus and due to a bad USB stick. I opened it as a place holder, but will close for now and reopen if I actually hit it again.

Changed in debconf (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers