dconf-service crashed with SIGSEGV in g_variant_builder_add_value()

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

Bug Description

Unsure.

Was on my account, then logged into a guest account, then logged out and back into my account.
Then it showed me the report dialog.

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: Fri Jan 25 13:03:39 2013
ExecutablePath: /usr/lib/dconf/dconf-service
InstallationDate: Installed on 2011-10-21 (461 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MarkForUpload: True
ProcCmdline: /usr/lib/dconf/dconf-service
SegvAnalysis:
 Segfault happened at: 0x7f8807b35520: mov 0x20(%rdi),%eax
 PC (0x7f8807b35520) 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: Upgraded to raring on 2013-01-20 (4 days ago)
UserGroups:

Revision history for this message
Fred (eldmannen+launchpad) wrote :
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 #1104883, 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.

information type: Private → Public
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.