Fix Google Account Authentication and Drive Integration Issues on KDE Plasma

A community-driven solution to resolve critical authentication issues between KDE Plasma desktop environments and Google services integration.

📌 Overview

This repository addresses two critical authentication issues affecting KDE users across multiple distributions:

1. "This browser or app is not secure" error during login
2. "This app is blocked" error when accessing Google Drive

The solution involves strategic configuration modifications validated across six major Linux distributions.

🚀 Quick Start

Prerequisites

• KDE Plasma 5.24+ environment
• kaccounts-integration package installed
• Active internet connection

Installation

curl -sSL https://raw.githubusercontent.com/Amm1rr/Fix-Google-Account-on-KDE/main/fix_kde_google_integration.sh | bash

Post-Installation

kquitapp6 kded6  # Restart KDE core services
systemctl --user restart plasma-kglobalaccel  # Refresh desktop services

🛠 Known Issues and Solutions

Issue 1: Untrusted Browser Error

Error Message:
"This browser or app is not secure"

Affected Systems:
Arch Linux and derivatives using signon-ui package

Root Cause:
The fake-user-agent.patch in signon-ui modifies browser headers in a way that triggers Google's security checks.

Solution:
Package rebuild without the problematic patch:

# Example for Arch-based systems
asp export signon-ui
cd signon-ui/trunk
sed -i '/fake-user-agent.patch/d' PKGBUILD
makepkg -si

Issue 2: Application Block Error

Error Message:
"This app is blocked"

Affected Systems:
All Linux distributions using KDE 5.24+

Root Cause:
Invalid OAuth Client ID in KDE's Google provider configuration:

317066460457-pkpkedrvt2ldq6g2hj1egfka2n7vpuoo.apps.googleusercontent.com

Solution:
Replace with GNOME's validated Client ID:

45471411055-ornt4svd2miog6dnopve7qtmh5mnu6id.apps.googleusercontent.com

🔍 Technical Implementation

The script performs the following critical modifications:

1. Configuration Replacement:

   /usr/share/accounts/providers/kde/google.provider

   • Replaces KDE's client ID with GNOME's validated credentials
   • Updates OAuth scopes for proper Drive integration

2. Scope Modifications:

   ; Before
   ServiceScopes=https://www.googleapis.com/auth/drive
   
   ; After
   ServiceScopes=https://www.googleapis.com/auth/drive.file

3. Safety Measures:

   # Create timestamped backups
   cp /usr/share/accounts/providers/kde/google.provider{,.bak_$(date +%s)}

🔄 Post-Update Considerations

After KDE framework updates, re-run the script to:

1. Check configuration integrity
2. Reapply necessary modifications
3. Validate service permissions

📚 Documentation

File Structure

/usr/share/accounts/providers/kde/
├── google.provider          # Main configuration
└── google-drive.provider    # Drive-specific settings

Critical Parameters

Parameter	Original Value	Modified Value
ClientId	KDE-specific OAuth ID	GNOME OAuth ID
ServiceScopes	Full Drive access	Restricted file-specific access
UserAgent	KDE-specific agent string	GNOME-compatible agent string

🚨 Troubleshooting

Common Issues

1. Permission Denied:

   sudo chmod +x /usr/share/accounts/providers/kde/google.provider

2. Partial Drive Access: Re-authenticate through KDE System Settings > Online Accounts

3. Post-Update Failures:

   sudo pacman -Syu kaccounts-integration
   curl -sSL https://raw.githubusercontent.com/Amm1rr/Fix-Google-Account-on-KDE/main/fix_kde_google_integration.sh | bash

📜 References

1. KDE Forum Discussion
2. Google OAuth API Documentation
3. GNOME Online Accounts Implementation

🙏 Credit

Special thanks to Bruno Gonçalves for initial problem diagnosis and solution prototype.