kde-telepathy, impossible to connect to gmail accounts

[Pedro]

Im running ubuntu 12.10 quantal and i have installed kde, when running kde-telepathy i have added a gmail account, and after entering the password it has revealed impossible to connect to it, it always says that the password is wrong when that is false.

When using empathy, i have removed the gmail account and have added it again, now appears a XMLL window asking ubuntu permission to conenct to it, and now i was able to conenct to the gmail account.

[numerone (numerone)]

I had the same problem.
I tried to start empathy from kde and it asked me the autorization. I clicked on the button and it gave me the google login page and then asked me to connect telepathy to google account.

After that telepathy kde was able to connect without problems.

I think that kde implementation of telepathy misses the code for connect accounts to the system.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Diane Trout (diane-trout)]

I'm currently connecting to a google talk with the debian version and I'm only getting a certificate warning.

The interesting advanced settings for the google talk account are:

Server Settings:
server address: talk.google.com
server port: 5223

Security Settings:
[X] Require encrypted connection.
[ ] Ignore SSL errors
[X] Use old-style SSL (greyed out)

I was curious what the settings for people who were having trouble are.

[Kirill (kirill-gribovskiy)]

The same thing for me. May be it is because of proxy. Kopete works fine.

[Valorie Zimmerman (valorie-zimmerman)]

I tried to do this tonight in Zesty. I get an Configure -- Plasma box, which says:

Unable to finish -- Plasma
There was an error while trying to process the request: userActionFinished error: 2

I get the same error every time I try to add Google to my Ktp accounts.

[JP Zen (zendejaskids)]

I get this error also on Kubuntu 17.04 beta 2.
There was an error while trying to process the request: userActionFinished error: 2

[wmccarty (wdmlist)]

I also get this error on Kubuntu 17.04 non-beta full release.

[wmccarty (wdmlist)]

And while connecting to a Google account

[lnxusr (bjwest)]

I get this as well trying to create a Google account from System Settings -> Online Accounts. Dialog title for me is 'Unable to finish -- System Settings' though, not Plasma. Latest Kubuntu 17.04 with all updates.

This is also reported over on KDE bugtracking: https://bugs.kde.org/show_bug.cgi?id=379270.

[Dennis Marttinen (technowelho)]

I'm experiencing this bug too, up-to-date Kubuntu 17.04 with KDE Neon Dev-stable ppa (Plasma 5.10.0). For me the title is: Unable to finish -- System Settings Module. The error is the same: userActionFinished error: 2

[Danilo Silva (danilocsilva)]

Same here.
Kubuntu 17.04
"Ocorreu um erro ao tentar processar a solicitação: userActionFinished error: 2"

[Brandon Bell (brandonbell)]

This only started affecting me recently, but I rarely reboot or log out so it could have just been waiting around.

I am running Kubuntu 17.04 with latest updates.

I've attached a number of log files. I don't know if it's the cause or even related, but this sticks out to me:

    Aug 2 19:18:34 COMPNAME com.nokia.singlesignonui[1506]: QIODevice::read (QFile, "/home/USERNAME/.cache/signon-ui/cookies/66.jar"): device not open

That file doesn't exist, and I setup an inotifywait on the .cache/signon-ui/cookies folder while trying to create the Google account and there were no changes to the folder at all during that time.

[Brandon Bell (brandonbell)]

This is the dbus-monitor output for com.nokia.singlesignonui

[Alberto Mardegan (mardy)]

Hi Brandon (and everyone else experiencing the signin-ui crash), in order to fix this bug I need to get the exact backtrace of the signon-ui program.

Could you please run

    apport-bug /var/crash/...[pick the signon-ui crash file]

from a terminal, so that launchpad can analyze the crash?

[Brandon Bell (brandonbell)]

I ran the command, but not sure if the report came through or not.

[Daniel Rodríguez Padilla (rodriguezpadillad)]

I ran the apport-bug command as well, but I'm not sure if it sent it or not, so I went ahead and attached it here.

[wens (alex-volegov)]

signond and signon-ui bug:
QIODevice::read (QFile, "/home/wens/.cache/signon-ui/cookies/7.jar"): device not open
signon: browser-request.cpp 754 initializeField Couldn't find element: "input[name=Passwd]"
signon-ui[3337]: segfault at 8 ip 00007f9a0daced90 sp 00007ffea5f43058 error 4 in libQt5Gui.so.5.7.1[7f9a0d9d5000+51a000]
QObject::disconnect: Unexpected null parameter

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Rik Mills (rikmills)]

Rebuilding the version for Xenial, 0.17+16.04.20151125-0ubuntu1, for artful 17.10 seems to produce a working signon via KDE's systemsetting

See test rebuild in: https://launchpad.net/~rikmills/+archive/ubuntu/kio-grive

Rebuilding any later ubuntu published versions fails to produce a working version.

[Rik Mills (rikmills)]

Correction.

0.17+17.10.20170606-0ubuntu1 works ok

[MarcoPau (marcopau)]

Hi, I have artful and I have build kio-gdrive-1.1.80.

Don't know if kio-gdrive is related with the userActionFinished error: 2 while trying to add the Google account. I am stuck there.

Do you have any hint?

Thanks!

@Rik Mills, your link does not work any more.

[Rik Mills (rikmills)]

On 20/12/17 09:15, MarcoPau wrote:
> Hi, I have artful and I have build kio-gdrive-1.1.80.
>
> Don't know if kio-gdrive is related with the userActionFinished error: 2
> while trying to add the Google account. I am stuck there.
>
> Do you have any hint?
>
> Thanks!
>
> @Rik Mills, your link does not work any more.
>

A working signon-ui can be found in our updates PPA

https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/ppa?field.series_filter=artful

It is also in our backports PPA, along with kio-gdrive 1.2.1 prebuilt .deb

https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/backports/+packages?field.name_filter=kio-gdrive

[Florian Fainelli (f-fainelli)]

I can confirm that signon-ui-service (0.17+17.10.20171027+really20160406-0ubuntu1~ppa1) and signon-ui-x11 (0.17+17.10.20171027+really20160406-0ubuntu1~ppa1) allow me to get past the Google account error. The account shows up, but going online does not quite work yet (which I have seen before).

[Jan Martinec (o-launchpad-piskvor-org)]

Was working in Ubuntu 17.04, broken after upgrade to 17.10, installing signon-ui from the PPA (0.17+17.10.20171027+really20160406-0ubuntu1~ppa1) resolved this for me.

[Andy Pieters (aethalides)]

I have discovered the cause for this.

You are using a proxy with an autoconfiguration URL (PAC script) which has got a syntax error in it (as far as WebKit is concerned)

When you run the add account it calls signon-ui and it segfaults because of this.

If you use konqueror you may also experience problems. In my case, it takes a very long time to load pages, like almost a minute long.

If you can, temporarily disable your proxy, or if you cannot connect without proxy, try manually setting the address of the proxy (not the PAC stript), for the duration of adding the account.

Once the account has been added, signon-ui isn't needed, and the proxy settings can be re-instated.

[Andy Pieters (aethalides)]

ok scratch the part about the syntax error as I have fixed my PAC file.

which leaves...

you can encounter this problem if you have a proxy server configured.

[Brandon Bell (brandonbell)]

In my case, I am not using a proxy server of any sort.