SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** When I add a Google account under Settings -> Personalization -> Online accounts, after adding the e-mail address, the page just loads endlessly without going to the password entry page. STEPS TO REPRODUCE 1. Open the KDE settings 2. Go to Personalization -> Online accounts 3. Add a Google account, and enter a google email. Click next. OBSERVED RESULT Page just loads endlessly without going to password EXPECTED RESULT The password entry field should then show SOFTWARE/OS VERSIONS Operating System: Fedora Linux 39 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Kernel Version: 6.5.5-300.fc39.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 6800H with Radeon Graphics Memory: 30.3 GiB of RAM Graphics Processor: AMD Radeon Graphics
Not sure if it helps, but when I try to add an account, I see this message in the system logs: Oct 01 19:31:13 fedora-laptop signon-ui[96043]: QIODevice::read (QFile, "/home/farchord/.cache/signon-ui/cookies/6.jar"): device not open Oct 01 19:31:14 fedora-laptop signon-ui[96043]: browser-request.cpp 738 initializeField Couldn't find element: "input[name=Email]" Oct 01 19:31:14 fedora-laptop signon-ui[96043]: browser-request.cpp 738 initializeField Couldn't find element: "input[name=Passwd]" Oct 01 19:31:14 fedora-laptop signon-ui[96043]: browser-request.cpp 738 initializeField Couldn't find element: "input[name=Email]" Oct 01 19:31:14 fedora-laptop signon-ui[96043]: browser-request.cpp 738 initializeField Couldn't find element: "input[name=Passwd]" Oct 01 19:31:14 fedora-laptop signon-ui[96043]: browser-request.cpp 738 initializeField Couldn't find element: "input[name=Email]" Oct 01 19:31:14 fedora-laptop signon-ui[96043]: browser-request.cpp 738 initializeField Couldn't find element: "input[name=Passwd]"
*** This bug has been marked as a duplicate of bug 420280 ***