Bug 508150 - Google Drive access denied
Summary: Google Drive access denied
Status: RESOLVED DUPLICATE of bug 480779
Alias: None
Product: kio-gdrive
Classification: Frameworks and Libraries
Component: general (other bugs)
Version First Reported In: unspecified
Platform: EndeavourOS Linux
: NOR normal
Target Milestone: ---
Assignee: Elvis Angelaccio
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-08-12 07:35 UTC by Mulder
Modified: 2025-08-12 07:56 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mulder 2025-08-12 07:35:25 UTC
SUMMARY

STEPS TO REPRODUCE
1. Yesterday I freshly installed Endeavour (with KDE) and wanted to connect my Google Drives
2. I installed KIO as officially recommended by Endeavour, and seting up the accountts worked smoothly (KIO was allowed as an app within my Google accounts, they were showing up in Dolphin etc.)
3. BUT when I tried to access (open) the Google drive folders, an "access denied" error came up and no drive content loaded (while no further warning from Google Drive came up).

The problem seems known for long - when have you planned to fix it? Do we really need to do workarounds for such a basic (core) program?

Here some online discussions around the problem (top results at Google for the described problem):

https://discuss.kde.org/t/kde-online-accounts-not-signing-in/3411/38

You seem to have applied this solution here already (but obviously it's not solving the problem):

https://discuss.kde.org/t/google-blocks-access-from-dolphin-kio-gdrive/26007

I really like Endeavour after first trying it in VM and now having made the first install, but without a good access to Google Drive (where all of my private and professional files reside) it's hard to work with it (Google Drive via Browser is complicated in everyday work, logically).

Thanks and looking forward to any reply!
Comment 1 Antonio Rojas 2025-08-12 07:56:43 UTC

*** This bug has been marked as a duplicate of bug 480779 ***