Bug 414010 - Adding a google account results in an invalid (empty) and non-working entry
Summary: Adding a google account results in an invalid (empty) and non-working entry
Status: RESOLVED DUPLICATE of bug 414219
Alias: None
Product: KAccounts
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 19.08.0
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Telepathy Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-11-10 19:11 UTC by Hans-Peter Jansen
Modified: 2020-03-05 20:36 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
empty kaccount google item (6.62 KB, image/png)
2019-11-10 19:11 UTC, Hans-Peter Jansen
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Hans-Peter Jansen 2019-11-10 19:11:45 UTC
Created attachment 123826 [details]
empty kaccount google item

SUMMARY

Add a google account succeeds, but the result is unusable.


STEPS TO REPRODUCE
1. Create an google account

OBSERVED RESULT
The created account doesn't show a name, and accerssing google drive fails

EXPECTED RESULT
The account should be displayed correctly, and accessing google drive succeeds.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: openSUSE Tumbleweed 20191107
(available in About System)
KDE Plasma Version: 5.17.2
KDE Frameworks Version: 5.63.0
Qt Version: 5.13.1

ADDITIONAL INFORMATION

This used to work, but today, I've created my gmail account in KMail and failed (https://bugs.kde.org/show_bug.cgi?id=404990), but meanwhile, I remvoed my working google account in exchange for a now defective one.

Dophin shows a single "New Account" item in the Goggle Drive tree, and opening it opens the kaccounts manager again, that asks for selecting an account.
Clicking on the otherwise empty "g" shows, that the two services, Drive and YouTube are enabled, but dysfunctional.
Comment 1 Wolfgang Bauer 2020-01-26 12:40:24 UTC
This is basically the same as bug#414219.

Only difference: openSUSE uses a newer signon-ui based on QtWebEngine (with a downstream patch to retrieve the username), while Kubuntu has an older QtWebKit based version. (so I don't mark it as duplicate just yet)

The underlying problem is the same though AFAICT, it fails to retrieve the user name from the login (web) page, probably due to some change on Google's side.

A workaround to get the account working:
- Run "sqlite3 ~/.config/libaccounts-glib/accounts.db"
- Enter "select * from Accounts;" to get the id of the account
- Enter "update Accounts set name="username" where id=1;" to set a username and it should work. (replace 1 with the actual id, the username is actually irrelevant and can be anything, it's just used to display the account in the settings and kio-gdrive)
Comment 2 Hans-Peter Jansen 2020-01-26 13:50:56 UTC
Thanks, Wolfgang, much appreciated!

And thanks again for more insights into the whole topic.

Let me add, that you can make the select a bit more self explaining with running the command ".headers on" before.
Comment 3 Rober 2020-03-05 09:57:55 UTC
(In reply to Wolfgang Bauer from comment #1)
> This is basically the same as bug#414219.
> 
> Only difference: openSUSE uses a newer signon-ui based on QtWebEngine (with
> a downstream patch to retrieve the username), while Kubuntu has an older
> QtWebKit based version. (so I don't mark it as duplicate just yet)
> 
> The underlying problem is the same though AFAICT, it fails to retrieve the
> user name from the login (web) page, probably due to some change on Google's
> side.
> 
> A workaround to get the account working:
> - Run "sqlite3 ~/.config/libaccounts-glib/accounts.db"
> - Enter "select * from Accounts;" to get the id of the account
> - Enter "update Accounts set name="username" where id=1;" to set a username
> and it should work. (replace 1 with the actual id, the username is actually
> irrelevant and can be anything, it's just used to display the account in the
> settings and kio-gdrive)

I had the same problem in Arch Linux and I could solve it.
Thanks!!!
Comment 4 Wolfgang Bauer 2020-03-05 20:36:27 UTC

*** This bug has been marked as a duplicate of bug 414219 ***