unity-webapps-context-daemon crashed with SIGSEGV in g_utf8_validate()

[vnieto]

Usig ubuntu one

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: unity-webapps-service 2.4.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5
Uname: Linux 3.5.0-17-generic x86_64
ApportVersion: 2.6.1-0ubuntu1
Architecture: amd64
Date: Fri Oct 5 10:19:15 2012
ExecutablePath: /usr/lib/libunity-webapps/unity-webapps-context-daemon
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
ProcCmdline: /usr/lib/libunity-webapps/unity-webapps-context-daemon Ubuntu\ One\ Music one.ubuntu.com icon://ubuntuone-music [Invalid\ UTF-8] UbuntuOneMusiconeubuntucom.desktop
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANGUAGE=es_CO:es
 LANG=es_CO.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f503f0f07c8 <g_utf8_validate+456>: movzbl (%rdi),%r8d
 PC (0x7f503f0f07c8) ok
 source "(%rdi)" (0x00000051) not located in a known VMA region (needed readable region)!
 destination "%r8d" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: libunity-webapps
StacktraceTop:
 g_utf8_validate () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_variant_new_string () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_variant_new_strv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_settings_set_strv () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libunity.so.9
Title: unity-webapps-context-daemon crashed with SIGSEGV in g_utf8_validate()
UpgradeStatus: Upgraded to quantal on 2012-09-12 (22 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

[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 #1033374, 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.