online-accounts-ui crashed with SIGSEGV

[Michael Blennerhassett]

Happened for no reason I can see

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: ubuntu-system-settings-online-accounts 0.4+14.10.20140612-0ubuntu1
ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0
Uname: Linux 3.15.0-6-generic x86_64
ApportVersion: 2.14.3-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Jun 26 21:51:39 2014
ExecutablePath: /usr/bin/online-accounts-ui
InstallationDate: Installed on 2013-06-22 (369 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130621)
ProcCmdline: /usr/bin/online-accounts-ui --desktop_file_hint=/usr/share/applications/online-accounts-ui.desktop
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x41f4e2: mov 0x10(%rdi),%rbp
 PC (0x0041f4e2) ok
 source "0x10(%rdi)" (0x00000010) not located in a known VMA region (needed readable region)!
 destination "%rbp" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: ubuntu-system-settings-online-accounts
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: online-accounts-ui crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 OnlineAccountsUi::Request::windowId (this=this@entry=0x0) at request.cpp:204
 OnlineAccountsUi::RequestManagerPrivate::enqueue (this=0x230bf30, request=request@entry=0x0) at request-manager.cpp:83
 OnlineAccountsUi::RequestManager::enqueue (this=<optimized out>, request=request@entry=0x0) at request-manager.cpp:161
 SignOnUi::Service::queryDialog (this=0x2310830, parameters=...) at signonui-service.cpp:159
 SignOnUi::Service::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=0x7fff834fae40) at moc_signonui-service.cpp:90

[Alberto Mardegan (mardy)]

The code has been heavily changed during the summer. I believe that this crash is no longer happening (if it is, please file a new bug).