Bug 493567 - Unable to add google account due to unsecure browser environment.
Summary: Unable to add google account due to unsecure browser environment.
Status: RESOLVED UPSTREAM
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_kaccounts (other bugs)
Version First Reported In: 6.1.5
Platform: Arch Linux Linux
: NOR grave
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-09-24 08:06 UTC by Benedek Szabó
Modified: 2025-10-10 16:51 UTC (History)
3 users (show)

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


Attachments
Account adding window, showing error message about unsecure browser (29.00 KB, image/png)
2024-09-24 08:06 UTC, Benedek Szabó
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Benedek Szabó 2024-09-24 08:06:07 UTC
Created attachment 174017 [details]
Account adding window, showing error message about unsecure browser

SUMMARY
Unable to add google account due to unsecure browser environment.


STEPS TO REPRODUCE
1. Open system settings and navigate to online accounts
2. Add a new account and select google
3. Try to add account with email and password
4. 

OBSERVED RESULT
Fail to add an account, google thinks this is an unsecure environment.


EXPECTED RESULT
Add account successfully

SOFTWARE/OS VERSIONS
Linux: Arch kernel: 6.10.10
KDE Plasma Version: Plasma 6.1.5
KDE Frameworks Version: 6.6.0
Qt Version: 6.7.2

ADDITIONAL INFORMATION
Comment 1 Benedek Szabó 2024-09-24 08:08:36 UTC
Maybe opening the default browser would be the best approach to fixing it.
Comment 2 Akseli Lahtinen 2024-09-24 08:45:47 UTC
Couldnt reproduce on my system

Operating System: Fedora Linux 40
KDE Plasma Version: 6.1.90
KDE Frameworks Version: 6.7.0
Qt Version: 6.7.2
Kernel Version: 6.10.10-200.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 3600 6-Core Processor
Memory: 15,5 GiB of RAM
Graphics Processor: AMD Radeon RX 6600
Comment 3 Nate Graham 2025-10-10 16:51:16 UTC
Likely fixed with a Qt update to move to a newer version of QtWebEngine.