frontend crashed with signal 5 in g_settings_get_value()

Bug #1058461 reported by Dave
66
This bug affects 15 people
Affects Status Importance Assigned to Milestone
debconf (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Crashes on every reboot, but nothing seems affected. I can use my sstem normally.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: debconf 1.5.46ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-16.24-generic 3.5.4
Uname: Linux 3.5.0-16-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.5.3-0ubuntu1
Architecture: amd64
Date: Fri Sep 28 22:15:57 2012
ExecutablePath: /usr/share/debconf/frontend
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
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:
 TERM=xterm
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: debconf
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_settings_get_value () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_settings_get_boolean () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? ()
Title: frontend crashed with signal 5 in g_settings_get_value()
UpgradeStatus: Upgraded to quantal on 2012-09-29 (0 days ago)
UserGroups:

Revision history for this message
Dave (kn8aw) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceSource:
 #0 0x00007f62160d2c7f in ?? ()
 #1 0x00000000021c49d0 in ?? ()
 #2 0x0000000000000000 in ?? ()
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in debconf (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

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!

tags: removed: need-amd64-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.