Summary: | net-libs/signon-ui[qt6]: Clicking "google" in add "online accounts" (KDE settings) does nothing | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Luke A. Guest <laguest> |
Component: | Current packages | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | chris, flavio.cappelli, julien.dlq, optimusgd, sam |
Priority: | Normal | Keywords: | PATCH, PullRequest |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://discuss.kde.org/t/kf6-kcm-kaccounts-cant-add-google-account/10837 | ||
See Also: |
https://bugs.kde.org/show_bug.cgi?id=480779 https://github.com/gentoo/gentoo/pull/38881 |
||
Whiteboard: | fixed in net-libs/signon-ui-0.15_p20231016-r2 | ||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 940669 | ||
Attachments: |
Working ebuild
Patch to disable tests (slightly different from the original, inspired by Arch PKGBUILD) Replace the patch signon-ui-0.15_p20171022-fix-username-field-reading.patch This is the same one in Portage, it should still be required |
Description
Luke A. Guest
2024-09-09 08:29:02 UTC
Same here "google-gmail" Looking for plugin "" Starting auth session with "oauth2" Info: Id: 89 caption: "google-gmail" owner: "" userName: "" qt.dbus.integration: Could not disconnect "com.google.code.AccountsSSO.SingleSignOn.Identity" to "destroyed(QObject*)" : Pointers are not supported: QObject* "google" Looking for plugin "" Starting auth session with "oauth2" Info: Id: 90 caption: "google" owner: "" userName: "" qt.dbus.integration: Could not disconnect "com.google.code.AccountsSSO.SingleSignOn.Identity" to "destroyed(QObject*)" : Pointers are not supported: QObject* Maybe https://bugs.kde.org/show_bug.cgi?id=480779 unrelated, or partially related, because there is no "browser window" at all. Hi all, I managed to get Google Drive working again in PLASMA6: - emerge kdenetwork-meta to make sure all dependencies are installed - run systemsetting and remove the old Google account - emerge my modified signon-ui ebuild (see following attachments) - reboot - run systemsettings from konsole (just to see the error messages) - click on online accounts, click on add new account, select Google: NOTE: the errors reported in the previous msgs still appear in the terminal but now the Google browse window opens (with the original ebuild it didn't) - enlarge the window just enough to have the input field inside - select your language (I selected Italian) - enter email + password and follow the verification procedure That's it, the procedure should succeed and you should have the possibility to open gdrive from dolphin again (for me it worked). Hoping this helps Flavio Created attachment 904711 [details]
Working ebuild
Created attachment 904712 [details, diff]
Patch to disable tests (slightly different from the original, inspired by Arch PKGBUILD)
Created attachment 904717 [details, diff]
Replace the patch signon-ui-0.15_p20171022-fix-username-field-reading.patch
Note: The above patch keeps httpUserAgent from the Gentoo patch signon-ui-0.15_p20171022-fix-username-field-reading.patch (I tried with the httpUserAgent from the Arch patch, but Google told me that "the browser was not secure", so I tried with the Gentoo's httpUserAgent and it worked).
Created attachment 904718 [details, diff]
This is the same one in Portage, it should still be required
(In reply to Flavio Cappelli from comment #3) > That's it, the procedure should succeed and you should have the possibility > to open gdrive from dolphin again (for me it worked). Nice job ! Worked for me too. No need to reboot, not even to close the session. (In reply to Flavio Cappelli from comment #4) > Created attachment 904711 [details] > Working ebuild Since you didn't attach a unified diff I need to ask unfortunately - any other changes in there than changing signon-ui-0.15_p20171022-fix-username-field-reading.patch? Sorry, I'm not sure I fully understand your question, so I'll try to explain what I did. On KDE Bugs (if I remember well) I found an Arch user who claimed that the signon-ui package currently in Arch worked, so I went to see what patches Arch used and saw that compared to Gentoo, it only used one patch that modified the httpUserAgent. So I stripped the original ebuild down to the bare minimum by applying the same and only patch used by Arch (I even left the tests enabled at the beginning). The sign-in window appeared (whereas it didn't before) but the authentication procedure failed reporting that the browser was too old. I guessed that the user agent was considered obsolete and saw that Gentoo used a different one, so I tried with that and it worked. It's just a guess but I suppose that the patch "signon-ui-0.15_p20171022-fix-username-field-reading.patch" was created to solve some issues with qml in Qt5/PLASMA5 (because it adds some qml code); I know in the transition from Qt5 to Qt6 (and therefore from PLASMA5 to PLASMA6) some things in qml have changed and in fact it seems that such patch is not more required in PLASMA6 (or at least it breaks something); after all Debian/Ubuntu do not use it, I don't know why OpenSuse introduced such patch. As for the other patches, they are just small tweaks: I removed "signon-ui-0.15_p20171022-drop-fno-rtti.patch" because it seems to do nothing, while I left "signon-ui-0.15_p20171022-webengine-cachedir-path.patch" because it seems correct to me (QUrl::fromLocalFile() would put "file:" in front of the filename). Finally I adopted the same method as Arch to disable the tests (my patch "signon-ui-0.15_p20171022-disable-tests-r1.patch" acts on "signon-ui.pro" like Arch, where the patch "signon-ui-0.15_p20171022-disable-tests.patch" in portage acts on "tests/tests.pro". I didn't make any other changes other than those described. My solution does not pretend to be perfect, not even the right one: signon-ui, based on the "qt6" use flag, should be able to work both in PLASMA5 (for those who still use it) and PLASMA6, while my version probably only works on PLASMA6 (since I no longer have PLASMA5 installed I have no way of testing it). Hoping this helps. Thanks for the detailed remarks. I was only asking about the ebuild changes. When people attach whole ebuilds, we cannot tell from the outset what the changes are. That's why maintainers will often ask for a unified diff against the latest ebuild in ::gentoo (or the one that was used as base for your changes), so this can be reviewed in bugzilla already. No longer necessary, I've already fetched your ebuild and assessing the patch differences. The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=549f7778c65881e32c0b497002fd23e7d469aafe commit 549f7778c65881e32c0b497002fd23e7d469aafe Author: Andreas Sturmlechner <asturm@gentoo.org> AuthorDate: 2024-10-04 18:42:09 +0000 Commit: Andreas Sturmlechner <asturm@gentoo.org> CommitDate: 2024-10-04 21:03:15 +0000 net-libs/signon-ui: Drop IUSE qt6 and broken/obsolete patch Thanks-to: Flavio Cappelli Closes: https://bugs.gentoo.org/939365 Signed-off-by: Andreas Sturmlechner <asturm@gentoo.org> .../signon-ui/signon-ui-0.15_p20231016-r2.ebuild | 59 ++++++++++++++++++++++ 1 file changed, 59 insertions(+) |