I can also confirm that I tested this on Solus and it has resolved the issue.
Thank you.
Just tested this on Fedora 41 with KDE Plasma and it works fine 
there also.
1 Like
I did try the pared down Scope URIs with the KDE ClientID, but as I kind of expected based on your troubleshooting that did not work.
However, your pared down Scope URIs plus the Gnome ClientID and ClientSecret worked just fine.
FWIW, I did also try an App Password, but the password page never took the app password, so your method appears to be the only functioning workaround for the time being.
Thanks for working this out!
1 Like
Thanks a lot. Very smart people here with a lot more skills in this area then I.
1 Like
I’ve done this and it works and that’s cool. However, my understanding of how oauth works is that if an update replaces that underlying file the connections are likely to break when its time for a token refresh, so we should all probably prepare for that.
1 Like
I’ve just come across this too - excuse my ignorance.
I am using Opensuse KDE tumbleweed - I tried swapping the ClientId and ClientSecret for the ones above but I still get the same error. Is the ClientId specific to my particular installation? Where do I find it, if so?
Thank you
Hi - there are also some differences in included URLs and in the parameters between the files - it may be easier to simply back-up the existing /usr/share/accounts/providers/kde/google.provider file, and replace it with the version that @Bruno_Goncalves suggested above.
If you’d rather edit manually, you might need to make each adjustment?
2 Likes
Thank you, the configuration file shared by @Bruno_Goncalves worked flawlessly in Debian 12 with KDE!
2 Likes
Thank you very much Bruno,
Now I can access both my GDrives again.
1 Like
Well, this solution definitely won’t work on Bazzite - since it’s a RO filesystem. I would love to see an upstream fix.
It might be worth adding your experience to the bug report - 480779 – Can not add Google to Online Accounts anymore using a recent version of signon-ui
2 Likes
Instead of editing a package-owned file in /usr, you can instead copy it to ~/.local/share/accounts/providers/google.provider, and edit the ClientId/ClientSecret there. It will override the one from /usr. This should work on immutable distros. It also won’t break next time the package in question is updated and overwrites things in /usr.
You can also create your own ClientId/ClientSecret, instead of hijacking the Gnome one. Unfortunately it’s a bit involved, but the Rclone developers have a step-by-step guide.
Unfortunately, it looks like discussion here is spread across Discuss, Invent and Bugs. I suspect Bugs is the right place for this to go, as oswald_c suggested.
9 Likes
you just changed client id and secret or replaced all file content ? because it is not working for me (i replaced client id and secret).
Replace the whole thing.
Then it should work.
Thank you, it worked!
2 Likes
This The Solution to this problem. Thank you.
1 Like
Its also possible to create your own client ID on https://console.cloud.google.com/apis/
Replace the newly generated client ID and Client Secret with the old Client ID and Client Secret in the existing /usr/share/accounts/providers/kde/google.provider file
4 Likes
Rapaz, você é um gênio. Resolveu um problema que está há anos dando dor de cabeça para muita gente. Resolveu o meu problema no Mageia 9.
Parabéns pela sua força de vontade em resolver este problema e pela sua genialidade.
1 Like
Been trying the trick of using the gnome version of the file. Added it to my .local area to keep it separate from the package supplied version. Goes through the process of requesting the Gmail address, password and a 2FA. In the end it says the app is blocked. Did Google tighten up the access even further? BTW, a new version of the kaccounts-provider package has removed the URL line that specifies the Google drive, so that’s not even an option anymore.
So I copied the contents of /usr/share/accounts/providers/kde/google.provider as provided above over the old one
This did allow me to sign in with no blocking message.
However I have no google drive link in dolphin.
Whats my next step please?
I did try clicking the Google drive shortcut under Network but it just hangs Loading
This all broke when I updated to 24.04
Hi! To recap the commit description linked in the bug report above (480779 – Can not add Google to Online Accounts anymore using a recent version of signon-ui), Google blocked KDE from the API to access Google Drive, and is requiring KDE as an organization to request permission to use that API again in a way that Google deems is “justified”.
Accessing Google Drive through KDE Online Accounts will depend on that situation changing at some point.