KDE Online Accounts not working in Plasma - at all - for Google

While this is similar to a post from 2023, it’s not the same.

The issue is KDE Plasma Online Accounts. adding a Google account, to configure KIO GD.

  1. Login screen appear; user enters Google account email

  2. Click Next button: text bos for email gets “mangled” - the prompt and the email get munged. But no “next” happens

  3. If I click enter, I get “bad request” from Google, and a 400

In the 2023 post, the blame was put on Google. No blame needed. I think this is something that can be addressed by KDE developers

Question: how do I make sure my Plasma desktop is up to date (in case that solves the issue)?

Question: Are there any Linux alternatives to KIO?

Just tested this on Plasma 6.5 Beta 2, and it doesn’t work here either. I could create the account, but when I access gdrive:/ in Dolphin it says “Access denied to .” I selected access to Contact and calendar systems. So an upgrade of Plasma probably won’t fix it for you.

Didn’t even realize Plasma had this feature and I reckon support for it is bad because many here try to get away from Big Tech overall and moving to FOSS alternatives like Nextcloud etc.

One alternative to KIO probably would be to use contacts and such via Thunderbird (I used this for years).

Having said that, there might be something wrong with my KDE PIM installation, maybe that’s why. What do you want to achieve with this? Is it just about access to Gdrive?

I abandoned the whole KDE path when I discovered something called ExpanDrive. It just works - well, still having issues with one of my gmail accounts. But Gnome just failed, so, no time to cry

1 Like

That solved my problem.

Thanks for the revelation

:slight_smile:

Reviving this thread: (newbie here - first post)

I’m seeing the same issue for an out-of-the-box install. I’m trying to access my Google Calendar (so am using Gnome Calendar because that’s what the UI suggested) and went to Online Accounts.

As per the OP, I get a dialog but nothing works (as described above).

But, in syslog I see this:

com.nokia.singlesignonui[9953]: browser-request.cpp 754 initializeField Couldn’t find element: “input[name=Email]”
com.nokia.singlesignonui[9953]: browser-request.cpp 754 initializeField Couldn’t find element: “input[name=Passwd]”

Is this because Google changed some field names recently (maybe not so recently - when they move to two-factor authentiction)? Or something else? The signon-ui “embedded” browser doesn’t give me an option to view source or anything like that…

Alternately: Is there a way to do the auth via the CLI (and I am aware that OAuth2 requires user interaction) or some other method that triggers the default system browser?