frontend crashed with signal 5

[Para Siva]

Occurred during a precise to quantal upgrade on a vm

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: debconf 1.5.46ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5
Uname: Linux 3.5.0-17-generic i686
ApportVersion: 2.6.1-0ubuntu2
Architecture: i386
Date: Tue Oct 9 19:16:24 2012
ExecutablePath: /usr/share/debconf/frontend
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20121002.1)
InterpreterPath: /usr/bin/perl
PackageArchitecture: all
ProcCmdline: /usr/bin/perl -w /usr/share/debconf/frontend /var/lib/dpkg/info/man-db.postinst triggered /usr/share/man
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=xterm
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: debconf
Stacktrace:
 #0 0xb708c69d in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
 No symbol table info available.
 #1 0xbfcbb744 in ?? ()
 No symbol table info available.
 Backtrace stopped: previous frame inner to this frame (corrupt stack?)
StacktraceTop:
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? ()
Title: frontend crashed with signal 5
UpgradeStatus: Upgraded to quantal on 2012-10-10 (0 days ago)
UserGroups:

[Apport retracing service (apport)]

Stacktrace:
 #0 0xb708c69d in ?? ()
 No symbol table info available.
 #1 0x093e9668 in ?? ()
 No symbol table info available.
 Backtrace stopped: previous frame inner to this frame (corrupt stack?)
StacktraceSource:
 #0 0xb708c69d in ?? ()
 #1 0x093e9668 in ?? ()
StacktraceTop:
 ?? ()
 ?? ()

[Apport retracing service (apport)]

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

outdated debug symbol package for libstdc++6: package version 4.7.2-2ubuntu1 dbgsym version 4.6.3-1ubuntu5
package liboverlay-scrollbar-0.2-0 does not exist, ignoring

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!