dconf-service crashed with SIGSEGV in g_variant_builder_add_value()

[Para Siva]

Occured after the raring desktop amd64 installation on 20130125 on a VM based on qemu-kvm usign virt-manager

1. Boot a VM to raring desktop amd64 live session with the image of 20130125
2. Start the installer from the live session
3. Perform manual partition (with 3 ext4 partitions and a swap)
4. Reboot after the installation
5. This crash was observed after the first reboot

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:57:33 2013
ExecutablePath: /usr/lib/dconf/dconf-service
InstallationDate: Installed on 2013-01-25 (0 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130125)
MarkForUpload: True
ProcCmdline: /usr/lib/dconf/dconf-service
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANGUAGE=en_GB:en
 LANG=en_GB.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7fdfa0181520: mov 0x20(%rdi),%eax
 PC (0x7fdfa0181520) 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

[Apport retracing service (apport)]

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.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Ubuntu QA Website (ubuntuqa)]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1105102

[Cavsfan (cavsfan)]

I just installed the daily iso and was preparing to copy files and got this error.

[Launchpad Janitor (janitor)]

This bug was fixed in the package glib2.0 - 2.35.4-0ubuntu5

---------------
glib2.0 (2.35.4-0ubuntu5) raring; urgency=low

  * debian/patches/git_fix_gvariant_tuple_checking.patch:
    - should fix a dconf-service segfault issue (lp: #1105102)
 -- Sebastien Bacher <email address hidden> Fri, 25 Jan 2013 18:08:29 +0100

[jerrylamos (jerrylamos)]

As of 26 January daily build bug still occurs.

[cacula (cacula)]

As of 26 January daily build bug still occurs.

[Dave Gilbert (ubuntu-treblig)]

Bug 1106322 saying it still happens on the new release version.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Benjamin (nailartcenter)]

occured in a VirtualBox with daily build after start a live session.

[Para Siva (psivaa)]

The crash is occurring in a live system even where the installed version on libglib2.0-bin is 2.35.4-0ubuntu5. This was observed on 20130128 raring desktop images.

[Robert Bruce Park (robru)]

Just installed the latest raring image for the nexus7, and was confronted with this crash on first boot.

[Kevin John Panzke (kevpan815)]

I just installed 20130128 Ubuntu AMD64 and the bug occurred right after first boot for me as well, only this time it did NOT allow me to try to file a bug report on the issue stating that I have some outdated files, therefore either the file has been recently updated and/or the 20130128 Builds may NOT yet contain the fix to solve this problem yet.

[Para Siva (psivaa)]

The latest traces are attached from an installation with 20130129

[bwat47 (bwat47)]

observed on the 29th amd64 daily iso

[Launchpad Janitor (janitor)]

This bug was fixed in the package d-conf - 0.15.2-0ubuntu5

---------------
d-conf (0.15.2-0ubuntu5) raring; urgency=low

  * debian/patches/git_ignore_empty_changesets.patch:
    - should fix a segfault happening on new users login (lp: #1105102)
 -- Sebastien Bacher <email address hidden> Thu, 31 Jan 2013 09:49:59 +0100