Bug 364111

I have the same issue here on Fedora 24.

Same problem on Kubuntu 17.04 with KDE 4.9.

same problem on Kubuntu 17.04
KDE-Plasma-Version: 5.9.4
KDE-Framework-Version: 5.31.0
QT-Version: 5.7.1

Same problem.

Kubuntu 17.04
KDE Plasma Version: 5.9.4
QT Version: 5.7.1

Exact same problem on Kubuntu 17.04
KDE-Plasma-Version: 5.9.4
KDE-Framework-Version: 5.31.0
QT-Version: 5.7.1

Problem persists after update to kapps 17.04, KF 5.33.0, Qt 5.9-beta

After clicking "OK" to the "userActionFInished error: 2" window, the following show up in ~/.xsession-errors:

QXcbConnection: XCB error: 3 (BadWindow), sequence: 56619, resource id: 41958187, major code: 19 (DeleteProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 56630, resource id: 41958187, major code: 19 (DeleteProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 56631, resource id: 41958187, major code: 18 (ChangeProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 56632, resource id: 41958187, major code: 19 (DeleteProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 56633, resource id: 41958187, major code: 19 (DeleteProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 56634, resource id: 41958187, major code: 19 (DeleteProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 56635, resource id: 41958187, major code: 7 (ReparentWindow), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 56636, resource id: 41958187, major code: 6 (ChangeSaveSet), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 56637, resource id: 41958187, major code: 2 (ChangeWindowAttributes), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 56638, resource id: 41958187, major code: 10 (UnmapWindow), minor code: 0

This comes up not just in telepathy, but also the new "Online Accounts" area of KDE System-settings on Kubuntu 17.04.

$ dpkg-query -s plasma-desktop
Package: plasma-desktop
Status: install ok installed
Priority: optional
Section: kde
Installed-Size: 8473
Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
Architecture: amd64
Version: 4:5.9.4-0ubuntu1

$ dpkg-query -s kde-telepathy
Package: kde-telepathy
Status: install ok installed
Priority: optional
Section: metapackages
Installed-Size: 8
Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
Architecture: all
Source: meta-kde-telepathy
Version: 15.08.3

*** Bug 379270 has been marked as a duplicate of this bug. ***

Same seen in kubuntu 17.04 with the KDE PPAs that bring plasma and the framework at the latest version.

Unclear if the issue depends on KDE Telepathy itself or on some other OS library used by KDE Telepathy.

May be the latter, since other failures occur in setting up accounts with telepathy and other providers and in this case more informative messages are provided. For instance:

- With Skype, the accunt cannot be set up, but the error message shows a complaint about the haze subsystem

- With Telegram, an error message complains about the morse subsystem

I suggest having more informative error messages, pointing out which libs are needed (and at what minimal version if relevant)

Please assure that the bug is confirmed, seems weird to have a bug with duplicates that is not confirmed.

I'm having the same issue as the first reported issue & some of the follow on reports also. It appears the online accounts section in settings is having servere issues.

Telepathy keeps being mentioned?

The same problem plasma 5.10.2

Sergio, you investigation does not show if the bug is indeed in KDE software, or in upstream code. As such, it does not make sense to change the bug status.

On a computer running Kubuntu 16.10, I am still able to configure a new Google account, on Kubuntu 17.04 this is no longer the case.

Seems to be a bug in the distro, rather than in KDE itself, then.

The distro, particularly when using the kubuntu PPA should be rather closely related to neon, though. I wonder if the thing works there.

Given at least 3 distros are affected (from the comments here, this has been seen on OpenMandriva, Fedora and (K)ubuntu), and those distros aren't based on each other and not even part of the same family, chances are accounts-kcm can't deal with a newer version of a system library all those distros have updated to (and this isn't detected -- build succeeds and runtime just errors out with cryptic errors).

It would be useful to see a list of related system library versions from someone for whom this is working.

It never worked here and the bug was reported a year ago, so chances are there's an unmarked dependency on a version of a system library that is more than a year old.

(In reply to Bernhard Rosenkränzer from comment #17)
> Given at least 3 distros are affected (from the comments here, this has been
> seen on OpenMandriva, Fedora and (K)ubuntu), and those distros aren't based
> on each other and not even part of the same family, chances are accounts-kcm
> can't deal with a newer version of a system library all those distros have
> updated to (and this isn't detected -- build succeeds and runtime just
> errors out with cryptic errors).
> 
> It would be useful to see a list of related system library versions from
> someone for whom this is working.

Adding google accounts works fine on archlinux.

Anyway this error comes from signond:

userActionFinished error: 2 ==> where 2 is the following enum value:


    QUERY_ERROR_NO_SIGNONUI,     /**< Cannot send request to signon-ui. */


so it seems the signon-ui plugin is not installed/working. 

Which means this issue should be reported to https://gitlab.com/accounts-sso/signon-ui

*** Bug 379405 has been marked as a duplicate of this bug. ***

(In reply to Elvis Angelaccio from comment #18)
> (In reply to Bernhard Rosenkränzer from comment #17)
> > Given at least 3 distros are affected (from the comments here, this has been
> > seen on OpenMandriva, Fedora and (K)ubuntu), and those distros aren't based
> > on each other and not even part of the same family, chances are accounts-kcm
> > can't deal with a newer version of a system library all those distros have
> > updated to (and this isn't detected -- build succeeds and runtime just
> > errors out with cryptic errors).
> > 
> > It would be useful to see a list of related system library versions from
> > someone for whom this is working.
> 
> Adding google accounts works fine on archlinux.

Forgot to add that I'm using the kcm from kaccounts-integration, I don't have any telepathy package installed.

Created attachment 107169 [details]
Apport log

Created attachment 107170 [details]
Stderr output

Created attachment 107171 [details]
Syslog output

Created attachment 107172 [details]
DBus output

Created attachment 107173 [details]
Kernel log

Created attachment 107174 [details]
Crash log

Those logs say that signon-ui crashes. Again, it should be reported here: https://gitlab.com/accounts-sso/signon-ui

Further along that same line, it says that signon-ui segfaulted in libQt5Gui.so.

     Aug  2 19:18:35 COMPNAME kernel: [  679.613938] signon-ui[5791]: segfault at 8 ip 00007f93da47ada0 sp 00007ffcf7375b28 error 4 in libQt5Gui.so.5.7.1[7f93da381000+51b000]

I've reported it to the signon-ui tracker, but I think it warrants investigation here too.

Updating to current (2017/08/10) git versions of signond and signon-ui fixed the problem for me.

Same issue on Kubuntu 17.10, with Plasma version 5.11.95, frameworks version 5.42.0, QT version 5.9.1

Same on openSUSE 42.3, plasma5-desktop 5.12.0-291.1

(In reply to Elvis Angelaccio from comment #18)
> (In reply to Bernhard Rosenkränzer from comment #17)
> > Given at least 3 distros are affected (from the comments here, this has been
> > seen on OpenMandriva, Fedora and (K)ubuntu), and those distros aren't based
> > on each other and not even part of the same family, chances are accounts-kcm
> > can't deal with a newer version of a system library all those distros have
> > updated to (and this isn't detected -- build succeeds and runtime just
> > errors out with cryptic errors).
> > 
> > It would be useful to see a list of related system library versions from
> > someone for whom this is working.
> 
> Adding google accounts works fine on archlinux.
> 
> Anyway this error comes from signond:
> 
> userActionFinished error: 2 ==> where 2 is the following enum value:
> 
> 
>     QUERY_ERROR_NO_SIGNONUI,     /**< Cannot send request to signon-ui. */
> 
> 
> so it seems the signon-ui plugin is not installed/working. 
> 
> Which means this issue should be reported to
> https://gitlab.com/accounts-sso/signon-ui

Some additional results in complement to Elvis's result:

I tried to add a google account to a fresh installed arch with plasma 5 (lots of things were not installed at that time), that works fine.
When trying to add the (same) account on my laptop (which has arch installed and updated for years), it fails with the reported error. (I tried both en_US.UTF-8 and zh_CN.UTF-8 as locales `LC_ALL=en_US.UTF-8 LANG=en_US.UTF-8 LANGUAGE=en_US`.)

As a result, this doesn't seem to be the problem of one single software (at least, this seems to involve some other software), though the core problem may be inside signon-ui.

Forgot to mention:

* The results are from these days (2018-2-21 - 2018-2-24). I tried `systemsettings` 5.12.1 and 5.12.2 on my laptop; it should be 5.12.2 for the fresh Arch (because the system was installed on 2018-2-21 and Arch's systemsettings 5.12.2 was compiled on 2018-2-20), though the version doesn't seem to make a difference.
* I tried removing telepathy-kde-meta (and its dependencies) from my laptop (but leaving a few telepathy [not directly related to kde or qt] packages on my laptop), and the problem is the same (though the telepathy thing really disappeared from systemsettings; rebooting also tried). (Not sure if relevant: I have one XMPP account configured and didn't remove it during the test.)
* That fresh Arch doesn't have telepathy installed.

Upstream issue is being tracked here: https://gitlab.com/accounts-sso/signon-ui/issues/1

I had a similar problem while trying to setup access to google drive via gdrive. Migrating from Oracle Java to OpenJDK did the trick.

Still a bug for me with latest kde.

(In reply to 32323 from comment #36)
> Still a bug for me with latest kde.

for me too, on Parabola GNU/Linux-libre (Arch-based)

The original issue has long since been fixed. People experiencing the same symptoms today are encountering something different, likely Bug 420280.