| Summary: | access denied to google drive in dolphin | ||
|---|---|---|---|
| Product: | [Applications] dolphin | Reporter: | Zachariah Jackson <kde> |
| Component: | general | Assignee: | Dolphin Bug Assignee <dolphin-bugs-null> |
| Status: | CONFIRMED --- | ||
| Severity: | normal | CC: | bugs.kde.org, david, eholtz716, eifr0980, gilbert.drew, glizda, jpalecek, kde, kfm-devel, nate, pechagueb, pioner14 |
| Priority: | NOR | ||
| Version First Reported In: | 24.12.2 | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| See Also: | https://bugs.kde.org/show_bug.cgi?id=480779 | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Zachariah Jackson
2025-02-18 18:54:16 UTC
Unfortunately google blocked our access to Google Drive because we were unable to meet their requirements for re-certification. Someone needs to restart that process so Google Drive integration can work again. (In reply to Nate Graham from comment #1) > Unfortunately google blocked our access to Google Drive because we were > unable to meet their requirements for re-certification. > > Someone needs to restart that process so Google Drive integration can work > again. the bad part is I can link it. I think the bug is one the OS side because it isn't saying access blocked but just that the permissions locally haven't been set up. *** Bug 503780 has been marked as a duplicate of this bug. *** (In reply to Zachariah Jackson from comment #2) > (In reply to Nate Graham from comment #1) > > Unfortunately google blocked our access to Google Drive because we were > > unable to meet their requirements for re-certification. > > > > Someone needs to restart that process so Google Drive integration can work > > again. > > the bad part is I can link it. I think the bug is one the OS side because it > isn't saying access blocked but just that the permissions locally haven't > been set up. I have the same problem (in 6.3.4). During the process to add my Google account, I did not see the Drive permissions as part of the requested permissions. When I look in Google to see what permissions have been granted to KDE, Google Drive permissions are not listed. If I look at a similar app that does have access (e.g. GNOME), I do see Drive permissions. (In reply to Eric H from comment #4) > (In reply to Zachariah Jackson from comment #2) > > (In reply to Nate Graham from comment #1) > > > Unfortunately google blocked our access to Google Drive because we were > > > unable to meet their requirements for re-certification. > > > > > > Someone needs to restart that process so Google Drive integration can work > > > again. > > > > the bad part is I can link it. I think the bug is one the OS side because it > > isn't saying access blocked but just that the permissions locally haven't > > been set up. > > I have the same problem (in 6.3.4). During the process to add my Google > account, I did not see the Drive permissions as part of the requested > permissions. When I look in Google to see what permissions have been > granted to KDE, Google Drive permissions are not listed. If I look at a > similar app that does have access (e.g. GNOME), I do see Drive permissions. But... that's the crux of this issue (and has nothing to do with the OS). Basically Google's been locking KDE out of GDrive so KDE stopped requesting GDrive permissions so it gets at least the other ones. And there's some bureaucracy to be done on KDE's side, but I'm not sure if there is anyone to actually do it (and who). *** Bug 508751 has been marked as a duplicate of this bug. *** |