SUMMARY When I tried gdrive:/ in dolphin, I get the following error: qt.svg: Could not create image from "data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAMAAAADACAYAAABS3GwHAAAgAElEQVR42u29eXxU5fU/fs5z7+wz" 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. STEPS TO REPRODUCE 1. install kio_gdrive 2. add a google drive account to kde 3. open dolphin and write gdrive:/ in the location 4. select your account OBSERVED RESULT it shows Bad Request in dolphin and in the logs I have 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. EXPECTED RESULT Show the content of the google drive SOFTWARE/OS VERSIONS Linux/KDE Plasma: Tuxedo OS 3 (available in About System) KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.5.0-10036-tuxedo (64-bit) X11 ADDITIONAL INFORMATION
*** This bug has been marked as a duplicate of bug 480063 ***