SUMMARY Get an error Invalid Protocol 'gdrive' after create a Google Account STEPS TO REPRODUCE 1. Install apt install kio-gdrive kaccounts-integration kaccounts6-integration kaccounts-providers 2. After that try to open up the gdrive via Dolphin -> Network -> Google Drive 3. Bump into error message OBSERVED RESULT Bump into error message Invalid Protocol 'gdrive' EXPECTED RESULT Navigate through gdrive folders and files using Dolphin SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 6.0.80 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.1 Kernel Version: 6.7.4-x64v4-xanmod1 (64-bit) Graphics Platform: X11 Processors: 4 × AMD A12-9720P RADEON R7, 12 COMPUTE CORES 4C+8G Memory: 15.1 GiB of RAM Graphics Processor: AMD Radeon R7 Graphics Manufacturer: Acer Product Name: Aspire A515-41G System Version: V1.09
Neon doesn't seem to build kio-gdrive for Qt6
Our qt 6 build of kio-gdrive got overwritten by a newer build of kio-gdrive-5, I've now renamed the qt 5 build so this can't happen but it won't be published until the repos are undivered which I hope to do today
(In reply to Jonathan Riddell from comment #2) > Our qt 6 build of kio-gdrive got overwritten by a newer build of > kio-gdrive-5, I've now renamed the qt 5 build so this can't happen but it > won't be published until the repos are undivered which I hope to do today Nice. Thanks for all your effort.
Now I get this new error: Feb 20 15:09:33 karis kioworker[6044]: 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" ' Feb 20 15:09:33 karis kioworker[6044]: kf.kio.core: UDSEntry for '.' not found, creating a default one. Please fix the "kio_gdrive" KIO worker.
is this still problematic, have been able to use locally with success
I have a similar error when I try to open gdrive via dolphin. 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" ' 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.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
I see this error too. Is there a known work-around? Maybe fresh install of the packages? My situation is as follows: $ ldd -d /usr/lib/x86_64-linux-gnu/signon/extensions/libkeyring-kwallet.so linux-vdso.so.1 (0x00007fff78b54000) libKF5Wallet.so.5 => /lib/x86_64-linux-gnu/libKF5Wallet.so.5 (0x00007f1ab899f000) libsignon-extension.so.1 => /lib/x86_64-linux-gnu/libsignon-extension.so.1 (0x00007f1ab8988000) libQt5Core.so.5 => /lib/x86_64-linux-gnu/libQt5Core.so.5 (0x00007f1ab8400000) libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f1ab8000000) libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f1ab8968000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f1ab7c00000) libKF5WindowSystem.so.5 => /lib/x86_64-linux-gnu/libKF5WindowSystem.so.5 (0x00007f1ab83aa000) libKF5ConfigCore.so.5 => /lib/x86_64-linux-gnu/libKF5ConfigCore.so.5 (0x00007f1ab833d000) libQt5DBus.so.5 => /lib/x86_64-linux-gnu/libQt5DBus.so.5 (0x00007f1ab82aa000) libQt6DBus.so.6 => /lib/x86_64-linux-gnu/libQt6DBus.so.6 (0x00007f1ab7f46000) libQt6Core.so.6 => /lib/x86_64-linux-gnu/libQt6Core.so.6 (0x00007f1ab7600000) libsystemd.so.0 => /lib/x86_64-linux-gnu/libsystemd.so.0 (0x00007f1ab7e7f000) libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f1ab828c000) libdouble-conversion.so.3 => /lib/x86_64-linux-gnu/libdouble-conversion.so.3 (0x00007f1ab8277000) libicui18n.so.70 => /lib/x86_64-linux-gnu/libicui18n.so.70 (0x00007f1ab7200000) libicuuc.so.70 => /lib/x86_64-linux-gnu/libicuuc.so.70 (0x00007f1ab7005000) libpcre2-16.so.0 => /lib/x86_64-linux-gnu/libpcre2-16.so.0 (0x00007f1ab7576000) libzstd.so.1 => /lib/x86_64-linux-gnu/libzstd.so.1 (0x00007f1ab6f36000) libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libglib-2.0.so.0 (0x00007f1ab6dfc000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f1ab6d15000) /lib64/ld-linux-x86-64.so.2 (0x00007f1ab89f1000) libX11.so.6 => /lib/x86_64-linux-gnu/libX11.so.6 (0x00007f1ab6bd5000) libxcb.so.1 => /lib/x86_64-linux-gnu/libxcb.so.1 (0x00007f1ab824b000) libxcb-keysyms.so.1 => /lib/x86_64-linux-gnu/libxcb-keysyms.so.1 (0x00007f1ab8244000) libQt5X11Extras.so.5 => /lib/x86_64-linux-gnu/libQt5X11Extras.so.5 (0x00007f1ab823d000) libQt5Widgets.so.5 => /lib/x86_64-linux-gnu/libQt5Widgets.so.5 (0x00007f1ab6400000) libQt5Gui.so.5 => /lib/x86_64-linux-gnu/libQt5Gui.so.5 (0x00007f1ab5c00000) libdbus-1.so.3 => /lib/x86_64-linux-gnu/libdbus-1.so.3 (0x00007f1ab7e31000) libb2.so.1 => /lib/x86_64-linux-gnu/libb2.so.1 (0x00007f1ab7be2000) liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x00007f1ab7bb7000) liblz4.so.1 => /lib/x86_64-linux-gnu/liblz4.so.1 (0x00007f1ab7556000) libcap.so.2 => /lib/x86_64-linux-gnu/libcap.so.2 (0x00007f1ab8230000) libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20 (0x00007f1ab5ac2000) libicudata.so.70 => /lib/x86_64-linux-gnu/libicudata.so.70 (0x00007f1ab3e00000) libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x00007f1ab6b5f000) libXau.so.6 => /lib/x86_64-linux-gnu/libXau.so.6 (0x00007f1ab7e2b000) libXdmcp.so.6 => /lib/x86_64-linux-gnu/libXdmcp.so.6 (0x00007f1ab7baf000) libGL.so.1 => /lib/x86_64-linux-gnu/libGL.so.1 (0x00007f1ab6ad8000) libpng16.so.16 => /lib/x86_64-linux-gnu/libpng16.so.16 (0x00007f1ab63c5000) libharfbuzz.so.0 => /lib/x86_64-linux-gnu/libharfbuzz.so.0 (0x00007f1ab62f6000) libmd4c.so.0 => /lib/x86_64-linux-gnu/libmd4c.so.0 (0x00007f1ab7544000) libgomp.so.1 => /lib/x86_64-linux-gnu/libgomp.so.1 (0x00007f1ab5a78000) libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 (0x00007f1ab5a52000) libbsd.so.0 => /lib/x86_64-linux-gnu/libbsd.so.0 (0x00007f1ab5a3a000) libGLdispatch.so.0 => /lib/x86_64-linux-gnu/libGLdispatch.so.0 (0x00007f1ab3d48000) libGLX.so.0 => /lib/x86_64-linux-gnu/libGLX.so.0 (0x00007f1ab3d14000) libfreetype.so.6 => /lib/x86_64-linux-gnu/libfreetype.so.6 (0x00007f1ab3c4c000) libgraphite2.so.3 => /lib/x86_64-linux-gnu/libgraphite2.so.3 (0x00007f1ab3c25000) libmd.so.0 => /lib/x86_64-linux-gnu/libmd.so.0 (0x00007f1ab7537000) libbrotlidec.so.1 => /lib/x86_64-linux-gnu/libbrotlidec.so.1 (0x00007f1ab6aca000) libbrotlicommon.so.1 => /lib/x86_64-linux-gnu/libbrotlicommon.so.1 (0x00007f1ab3c02000) But funny enough... $ dpkg -S /lib/x86_64-linux-gnu/libKF5Wallet.so.5.115 dpkg-query: no path found matching pattern /lib/x86_64-linux-gnu/libKF5Wallet.so.5.115 Do I see packaging problems?
How can I provide more info? I have the same issue with a fresh KDE neon install. `Invalid field selection` error in dolphin.
I am stil having trouble with that.
I am seeing this bug too. Creating a new GDrive connection now works with KDE 6, but using it is not possible: ``` 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. ``` Running KDE Neon 22.04 with KDE 6.2, Frameworks 6.7, kio-gdrive 24.05.0-build32 and all available updates applied.
Created attachment 172263 [details] Screenshot of error. How can we provide you more information please let us know because I'm also facing same issue with "bad request" error message.
(In reply to Gilberto Ferreira from comment #4) > Now I get this new error: > Feb 20 15:09:33 karis kioworker[6044]: kf.kio.core: UDSEntry for '.' not found, creating a default one. Please fix the "kio_gdrive" KIO worker. I don't *think* that error is specific to this issue, since `kde-cli-tools-6.2.5-1.fc41.x86_64` exhibits this from any `ls` invocation that adheres to its `--help` page's syntax. [^1] [^1]: https://discuss.kde.org/t/does-kf-kio-core-udsentry-for-not-found-creating-a-default-one-please-fix-the-kioworker-kio-worker-indicate-a-fault-in-how-im-calling-it/25380?u=rokejulianlockhart