Trying to add a google account with the kubuntu online account manager
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
signon-ui (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
no account configured
fresh kubuntu 17.10 install or live usb.
Also seen on kubuntu 17.04
when trying to use the instant messenger embedded with kubuntu, icon on bottom right of the screen, I first need to add an existing google account.
In the "online accounts" tab, I click on "create", then select "google".
after a few seconds I get the following error:
Il y a une eu une erreur durant le traitement de la requête : userActionFinished error: 2
-> there has been an error while processing the request : userActionFinished error: 2
Adding an existing jabber account works fine.
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: signon-ui-x11 0.17+17.
ProcVersionSign
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: KDE
Date: Sat Oct 21 17:10:15 2017
ExecutablePath: /usr/bin/signon-ui
InstallationDate: Installed on 2017-09-23 (28 days ago)
InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: /usr/bin/signon-ui
ProcEnviron:
LANGUAGE=fr
PATH=(custom, no user)
XDG_RUNTIME_
LANG=fr_FR.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f50af6585a0 <_ZN7QWindow11s
PC (0x7f50af6585a0) ok
source "0x8(%rdi)" (0x00000008) not located in a known VMA region (needed readable region)!
destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: signon-ui
StacktraceTop:
QWindow:
?? ()
?? ()
?? ()
QMetaObject:
Title: signon-ui crashed with SIGSEGV in QWindow:
UpgradeStatus: Upgraded to artful on 2017-10-21 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
XsessionErrors:
(kerneloops-
(kerneloops-
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 #1723230, 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.