Ubuntu
d-conf package

dconf-service crashed with SIGSEGV in g_variant_builder_add_value()

Bug #1108890 reported by NeoSting on 2013-01-29

This bug report is a duplicate of: Bug #1105440: dconf-service crashed with SIGSEGV in g_variant_is_trusted(). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	d-conf (Ubuntu)	New	Undecided	Unassigned

Bug Description

Bug appears after launching the LIVE USB 01.29 ISO and opening Firefox. Nothing else was open/done...

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: dconf-service 0.15.2-0ubuntu4
ProcVersionSignature: Ubuntu 3.8.0-2.6-generic 3.8.0-rc4
Uname: Linux 3.8.0-2-generic x86_64
ApportVersion: 2.8-0ubuntu2
Architecture: amd64
CasperVersion: 1.330
Date: Tue Jan 29 13:31:19 2013
ExecutablePath: /usr/lib/dconf/dconf-service
LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130129)
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: 0x7fc98e419310: mov 0x20(%rdi),%eax
PC (0x7fc98e419310) 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

Tags:

Revision history for this message

NeoSting (neosting-web) wrote on 2013-01-29:

Dependencies.txt Edit (933 bytes, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2013-01-29: 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.