dconf-service crashed with SIGSEGV in g_variant_builder_add_value()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
d-conf (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
This Bug Report is almost similar to the Bug Report that I filed last night but is Slightly Different as this was an I386 Install instead of an AMD64 Installation, and is COMPLETELY DIFFERENT FROM BUG REPORT #1105102 as this was NOT a VM Installation, it was a Clean Install, (In other words, I did NOT Upgrade from a Live File System), and I did NOT use Manual File System Partitioning, it was all Automatic.
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: dconf-service 0.15.2-0ubuntu4
ProcVersionSign
Uname: Linux 3.8.0-1-generic i686
ApportVersion: 2.8-0ubuntu2
Architecture: i386
Date: Sun Jan 27 14:31:44 2013
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2013-01-27 (0 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130126)
MarkForUpload: True
ProcCmdline: /usr/lib/
ProcEnviron:
SHELL=/bin/bash
XDG_RUNTIME_
PATH=(custom, no user)
LANG=en_US.UTF-8
SegvAnalysis:
Segfault happened at: 0xb74f3ff4: mov 0x10(%eax),%eax
PC (0xb74f3ff4) ok
source "0x10(%eax)" (0x00000010) 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/i386-
g_variant_
?? () from /lib/i386-
g_variant_new_va () from /lib/i386-
g_variant_new () from /lib/i386-
Title: dconf-service crashed with SIGSEGV in g_variant_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
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.