Created attachment 128088 [details] Short video from Online Accounts < 1min. Problems in KDE-Plasma Online Accounts in Fedora 32 x86_64
Please don't add random people to the CC list, just because you believe they are maintaining KDE software in Fedora. If you want attention of Fedora maintainers, user their bug tracker.
(In reply to Christoph Feck from comment #1) > Please don't add random people to the CC list, just because you believe they > are maintaining KDE software in Fedora. > > If you want attention of Fedora maintainers, user their bug tracker. I'm sorry for this! I believed that by sending more people the problem would be solved faster. I read some articles and I already understand how it works. Best regards and I'm sorry. Hugo Lopes.
Seeing similar behavior in Arch Linux. Added my google account, completed 2FA. Clicking "go online" from telepathy system tray does nothing. Google account not available in kmail. On other account providers I see similar behavior as in the attached video.
I confirm that this bug is also present in openSUSE Tumbleweed, both in the previous Plasma 5.18.5 and now in Plasma 5.19. Clicking on any of the options under Add New Account reverts to Accounts rather than opening a window to enter username/password etc.
Confirmed on opensuse tumbleweed even with kio-gdrive installed
The problem in openSUSE Tumbleweed is due to signond crashing because of a change in Qt 5.15.0. See https://bugzilla.opensuse.org/show_bug.cgi?id=1172904 It works fine again here with the updated signon packages mentioned in that bug report. No idea if Arch or Fedora are hit by the same problem, but it's probably not a bug in kaccounts anyway I think.
For the record, here's an upstream merge request to fix signond with Qt 5.15: https://gitlab.com/accounts-sso/signond/-/merge_requests/27 Arch actually applied a similar fix 14 days ago, so it should work there again too meanwhile I suppose. https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/signond&id=7e7dfd81b12dbfc62588d1355f2f7c4928598a05
*** This bug has been marked as a duplicate of bug 426034 ***