SUMMARY GDrive not working in since KDE 6 STEPS TO REPRODUCE 1. Create a Google online account 2. Try to enter in Google Drive network share OBSERVED RESULT Dolphin shows a "bad request" error message Console output: bluedevil.kio_bluetooth: Setting host: "" bluedevil.kio_bluetooth: Stat: QUrl("bluetooth:/") org.kde.kgapi: Bad request, Google replied ' "{\n \"error\": {\n \"code\": 400,\n \"message\": \"Invalid field selection etag,kind,nextLink,nextPageToken,selfLink,items(,,,,,,,,labels,exportLinks,lastViewedByMeDate,alternateLink,kind)\",\n \"errors\": [\n {\n \"message\": \"Invalid field selection etag,kind,nextLink,nextPageToken,selfLink,items(,,,,,,,,labels,exportLinks,lastViewedByMeDate,alternateLink,kind)\",\n \"domain\": \"global\",\n \"reason\": \"invalidParameter\",\n \"location\": \"fields\",\n \"locationType\": \"parameter\"\n }\n ]\n }\n}\n" ' kf.kio.core: UDSEntry for '.' not found, creating a default one. Please fix the "kio_gdrive" KIO worker. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: from 6.0.0 to 6.1.2 KDE Frameworks Version: from 6.0.0 to 6.3.0 Qt Version: from 6.0.0 to 6.7.0
I have just tried with a fresh install of Neon User edition in virtualbox and I cannot even add a google account from system settings (which is probably bug #480779). Since everything is working fine with other distributions (Fedora, Opensuse, Arch Linux), I'd assume there is still something missing in the signon stack as shipped by Neon...
(In reply to Elvis Angelaccio from comment #1) > I have just tried with a fresh install of Neon User edition in virtualbox > and I cannot even add a google account from system settings (which is > probably bug #480779). > > Since everything is working fine with other distributions (Fedora, Opensuse, > Arch Linux), I'd assume there is still something missing in the signon stack > as shipped by Neon... Hi Elvis, if you try to switch to another language during google oauth authentication, and if you try more than once, eventually you'll be able to add an account. after which the "Bad request" bug appears. Thanks
This is actually #480063 Fixed in 24.08.2 *** This bug has been marked as a duplicate of bug 480063 ***