signon-ui crashed with SIGSEGV in QV4::ExecutionEngine::newStringObject()

[Amr Ibrahim]

I installed signon-ui from xenial-proposed LP: #1547647. I get this crash after I add my Google account in UOA. It could be a regression. The Google account is added fine.

Steps to reproduce:
1. Choose to add a Google account in UOA
2. After it's done, disable all accesses except the last one (Evolution Data Server Access your Google Calendar)

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: signon-ui-x11 0.17+16.04.20170116-0ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-58-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Tue Jul 11 12:57:31 2017
ExecutablePath: /usr/bin/signon-ui
InstallationDate: Installed on 2017-06-21 (19 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2)
ProcCmdline: /usr/bin/signon-ui
SegvAnalysis:
 Segfault happened at: 0x7f44373936d5: mov 0x0(%rbp),%eax
 PC (0x7f44373936d5) ok
 source "0x0(%rbp)" (0x00000004) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: signon-ui
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
 QV4::ExecutionEngine::newStringObject(QV4::Value const&) () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
 QV4::Runtime::getProperty(QV4::ExecutionEngine*, QV4::Value const&, int) () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
 ?? ()
 ?? ()
Title: signon-ui crashed with SIGSEGV in QV4::ExecutionEngine::newStringObject()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirtd 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 #1703088, 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.