debconf-communicate crashed with SIGSEGV in __libc_start_main()

Bug #971312 reported by Richard Foulkes
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
debconf (Ubuntu)
New
Medium
Unassigned

Bug Description

All i was doing was changing the size of the launcher, having done a fresh oem install on my netbook!

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: debconf 1.5.42ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-21.34-generic-pae 3.2.13
Uname: Linux 3.2.0-21-generic-pae i686
ApportVersion: 2.0-0ubuntu2
Architecture: i386
Date: Mon Apr 2 08:13:47 2012
Disassembly: => 0xdf170: Cannot access memory at address 0xdf170
ExecutablePath: /usr/bin/debconf-communicate
InterpreterPath: /usr/bin/perl
PackageArchitecture: all
ProcCmdline: /usr/bin/perl -w /usr/bin/debconf-communicate
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 TERM=linux
 LANGUAGE=en_GB:en
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: debconf
StacktraceTop:
 ?? ()
 ?? ()
 __libc_start_main () from /lib/i386-linux-gnu/libc.so.6
 _start ()
Title: debconf-communicate crashed with SIGSEGV in __libc_start_main()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Richard Foulkes (rbsfou) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceTop.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in debconf (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
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.