dconf-service crashed with SIGSEGV in g_variant_builder_add_value()

Bug #1106519 reported by Kevin John Panzke
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
d-conf (Ubuntu)
New
Undecided
Unassigned

Bug Description

This error popped up right after Clean Installing 13.04, however it is DIFFERENT FROM BUG REPORT 1105102, because it was NOT a VM Installation and is Build 20130126 NOT 20130125, and the Installer was started by Booting to the DVD and Selecting Replace Raring Ragnal with 13.04, NOT a live session, and i did NOT select Manual Partitioning Either, it was all AUTOMATIC. Just FYI.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: dconf-service 0.15.2-0ubuntu4
ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4
Uname: Linux 3.8.0-1-generic x86_64
ApportVersion: 2.8-0ubuntu2
Architecture: amd64
Date: Sat Jan 26 19:50:23 2013
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/dconf/dconf-service
InstallationDate: Installed on 2013-01-27 (0 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130126)
MarkForUpload: True
ProcCmdline: /usr/lib/dconf/dconf-service
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7fe8b232e310: mov 0x20(%rdi),%eax
 PC (0x7fe8b232e310) ok
 source "0x20(%rdi)" (0x00000020) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: d-conf
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_variant_builder_add_value () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_variant_new_va () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_variant_new () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: dconf-service crashed with SIGSEGV in g_variant_builder_add_value()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Kevin John Panzke (kevpan815) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1105440, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

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.