SUMMARY When trying to add a Google account to the system, it just brings me back to the accounts overview. This happens when I click on "Google" on the "Add new account" page. The console reports an error: "google" Looking for plugin "" Starting auth session with "oauth2" 5 "org.freedesktop.DBus.Error.NoReply" "Message recipient disconnected from message bus without replying" 5 "org.freedesktop.DBus.Error.NoReply" "Message recipient disconnected from message bus without replying" Error: "Message recipient disconnected from message bus without replying" STEPS TO REPRODUCE 1. Launch the kaccounts kcm, `kcmshell5 kcm_kaccounts` 2. Click the Google entry on the "Add new accounts" page OBSERVED RESULT It brings me back to the account overview page EXPECTED RESULT A new dialog or page to allow me to enter my Google account details SOFTWARE/OS VERSIONS Linux/KDE Plasma: Alpine Linux edge (available in About System) KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.73.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION This is an Alpine Linux system meaning it uses Musl. It compiles fine with it, but maybe it causes some issues?
I'm having this same results described on KDE neon. Linux/KDE Plasma: KDE neon 5.20 KDE Plasma Version: 5.20.0 KDE Framework Version: 5.75.0 Qt Version: 5.15.0 Kernel Version: 5.4.0-51-generic
The same for me on KDE Neon SOFTWARE/OS VERSIONS KDE Neon: 5.20 Plasma: 5.20.0 KDE Frameworks: 5.75.0 kaccounts-integration: 4.20.08.2-0xneon+20.04+focal+build13 kaccounts-providers: 4.20.08.2-0xneon+20.04+focal+build9
signond needs to be built with CONFIG+=rtti https://gitlab.com/accounts-sso/signond/-/merge_requests/27
*** This bug has been marked as a duplicate of bug 420280 ***
*** Bug 428247 has been marked as a duplicate of this bug. ***
*** Bug 427184 has been marked as a duplicate of this bug. ***
*** Bug 427063 has been marked as a duplicate of this bug. ***
Building signond with CONFIG+=rtti did not make a difference for me. Note that this happens on multiple distros, including KDE Neon which I assume has that configured already too.
Humm. I can't reproduce this problem on Arch Linux running Plasma 5.20.1.
(In reply to Bart Ribbers from comment #8) > Building signond with CONFIG+=rtti did not make a difference for me. Note > that this happens on multiple distros, including KDE Neon which I assume has > that configured already too. which multiple distros? All duplicates are from Neon
Well I reported this for an Alpine Linux system, so it happens at least on Alpine and KDE Neon (which is multiple ;))
(In reply to Antonio Rojas from comment #10) > (In reply to Bart Ribbers from comment #8) > > Building signond with CONFIG+=rtti did not make a difference for me. Note > > that this happens on multiple distros, including KDE Neon which I assume has > > that configured already too. > > which multiple distros? All duplicates are from Neon this happens on Kubuntu, Neon User and Testing, and Debian sid with KDE. I haveNeon testing on one laptop and user on another laptop same result on both. Earlier in the week, i installed Debian testing then updated to sid... same thing... i tried Kubuntu for about 3 days before settling on Neon... same result... It appears this has been going on since April?? I opened a bug report yesterday and it was closed as duplicate: https://bugs.kde.org/show_bug.cgi?id=428247 Here is another bug: https://bugs.kde.org/show_bug.cgi?id=420280 seems as an ongoing issue across a number of base distros effecting hundreds or more users over the course of many months...
So with kubuntu (I just booted into live usb i still had from earlier) it pops up the login window for Google but its blank. If you right click and reload that window it brings up the Google login. I did not actually login but I can confirm it does provide the window to login after reloading the window. This window simply does not pop up within Neon.
I'd like to add some info I found when I was troubleshooting this bug. This seems to be a KDE Neon bug (packaging?), and may or may not be present elsewhere, but i imagine that to be out of scope if we already can confirm it is not a Plasma bug. It was a bug in OpenSuse TW as well [1], and was fixed a couple of months back. At least for TW, rebuilding signond with a patch (since merged) for this MR [2] solved this problem. So while it's an upstream bug vis-a-vis Plasma, it should not be closed because a bug to resolve this in KDE Neon is still valid. [1] https://bugzilla.opensuse.org/show_bug.cgi?id=1172904 [2] https://gitlab.com/accounts-sso/signond/-/merge_requests/27
The bug was open for hours in my browser before I got back to it and I forced through my comment when the conflict warning showed, because I was banging it out quickly between tasks and needed to get back to work... I realize now that most of what I wrote as rationale to reopen is kind of out of place now that it actually has been reopened and classified under neon Sorry for the noise :(
on neon, signond package comes from ubuntu repositories. Therefore, if it does not contain the bug fix, this issue must be reported in ubuntu bug tracker.
Thanks Patrick for that clarification. I opened an upstream bug: https://bugs.launchpad.net/ubuntu/+source/signon/+bug/1901609 Looks like it hasn't really been updated since ~Bionic, nothing but repackaging since then. Hopefully they'll feel motivated to address this.
it looks like this bug is confirmed on OpenSuse, Alpine Linux (as indicated on this ticket), Debian sid (but this could be caused by other issues on Debian), and KDE Neon. Submitting a bug report for Ubuntu is a good idea but (while i cannot be sure) it doesn't look like an Ubuntu issue.. its strange tho that it has been going on for several months and its a major part of the KDE system or any other system for that matter... 3rd party account integration is IMO one of the top features of a desktop environment.
I tested current signond master on Neon and it fixed the issue.
*** Bug 420878 has been marked as a duplicate of this bug. ***
How do I apply this fix?
If someone could simply let us/me know where the code can he downloaded from that would be great.
To answer the question as you asked: Source is available at gitlab for signond [1]. You'll also need to use signon-plugin-oauth2 [2] - thanks to Nicolas Fella for uncovering that. [1] https://gitlab.com/accounts-sso/signond [2] https://gitlab.com/accounts-sso/signon-plugin-oauth2 However, to answer your initial question, this is _not_ a "fix" - I don't recommend running it on your daily driver. You have to break your package system, which means spending even more time trying work around that problem. If you're still interested, be prepared to do a bunch of troubleshooting build failures, as well as resolving the (many) broken packages (which you're on your own for btw). Email me and I'll share as much as I can of what i did - I didn't track/document all of the troubleshooting I did to make it work. It is way out of scope to have that laid out here.
*** Bug 428935 has been marked as a duplicate of this bug. ***
I have simply concluded this will never be fixed and telepathy should simply be removed from KDE entirely. Its currently useless and has had the same or similar issues going back to 2015. Further no one wants to assume responsibility for fixing it. There are dozens or more bug reports from here, to reddit, to debian forums to manjaro forums to arch forums to ubuntu forums and on and on. Its never been fixed and now these bugs are closed as fixed in upstream. Which honestly may never actually reach end users. This issue is effecting almost all services including Lync, Google, telegram, Skype, etc. etc. Its also the same in all aur, deb, and rpm based distros.
This particual issue literally has been fixed. I can't magically place a fixed binary on your harddrive though
Nicholas, this is great news! I will gladly build from source if I had the link to the necessary code and some basic instructions to compile. I have several VM's as well as test beds i can do this on and once I get it compiled and working I will gladly create a binary for each distro and share it here. I can follow instructions and can build from source as long as I don't get tied up in dependency hell. I can also make work through errors and dependency issues so as long as its not rebuilding an entire system I can get'er working. Just point me in the right direction. I would love to get this working and would gladly share my results, write instructions and share binaries.
I don't have a rpm based system running right now so I will spin up a full system with CentOS and get it working there and create a .rpm and write instructions. This way I'll be able to do .deb, .rpm and I have a Manjaro system also so ill create pkgbuild also though I have never created one before. It might take me a few days or so to get it working. I'll do the work for all 3 main distros as long as it can be done with a reasonable amount of work. I'll do whatever I can to get this working for myself and others. Someone to contact when I get really stuck and google doesn't provide a resolution might be helpful.
Did you read comment 23? It has the links to the source code.
I certainly did which it clearly states its not a fix... and it will lead to a broken package system and further dependency hell. Thus my previous post that its not fixed and by the looks of things never will be... there is no current way to get this fixed signond package into current or near future systems. Thus its not fixed... if someone figured out a way to hand jamb some code into a system and get it to work while breaking just about everything e else (while I am not a package or distro maintainer) I would not call this a fix... how long before "current upstream" packages get included in a release or at least work in a release without significant breakage? 2 years, maybe never? I want to point out, while my tone sounds frustrated I am a firm supporter of open source and the GNU project and I know that this is mostly a voluntary effort with some pay and some fame. I am frustrated 8ndeed with the fact that this has been ongoing for 5 or more years in one form or another with no light at the end of the tunnel .. just silly.
When new versions of packages are released by distributions is decided by the distribution maintainers. Some release very quickly, with only days or weeks between an upstream fix and the fix rolling out to users, while others need years, if they have the manpower at all. For example, bug 420878 comment 7 states that Arch applied the patch in early June. I suggest to vent your frustration in a forum of your distribution; nothing can be done by KDE developers with your situation; adding more comments here will not help. I don't understand your 5 years figure, though. The issue reported here was an incompatibility with signon and Qt 5.15.0, which cannot be older than that Qt version.
I have posted on debian bug reports and manjaro and arch. Manjaro didn't respond even when I followed up, arch did the same thing simply not responding even with multiple posts and follow ups and debian pointed me to kde bug forums thats why I posted my initial bug report here... seems everyone is passing the buck. Also, the patch in arch did not fix the issue. It is improved as it allows for the Google account to be added but does not allow for messages to be sent, it never connects it says connecting... and never actually connects. The patch also fixed kio-gdrive but didn't fix Skype but I think thats a different package something about "haze". So unless telepathy was actually tried completely one may assume its fixed because the fixed signond allows for a google account to be added and appears at first glance to be working but actual messaging does not work and other accounts still can't be added. So if someone tried it and went as far as to add a Google account and then called it a day without actually trying to send messages and also trying other accounts like Skype and lync and telegram and then after adding the accounts actually sending messages it may appear to that person as fixed but in truth is only slightly improved...
The issues you are mentioning are unrelated to this particular bug report, so nobody claims they are all fixed (or even present). The only issue that was discussed and declared fixed is "When trying to add a Google account to the system, it just brings me back to the accounts overview". I personally haven't tried anything telepathy-related since I don't maintain it and have no interest in doing so. I only maintain the generic KAccount parts that are independant from telepathy.
If I understand you correctly, you are looking at a wrong bug report. This ticket is about login to Google services, not about messaging systems. I don't know which one you are using, but Google changes them every time, and it is possible that the software you are using doesn't support the new messaging services.
In Comment #17 , I linked to where I opened a bug against the upstream signond package in ubuntu. Your frustrations are valid. Your energy should be posted in that bug however. As we learned here (or at least I did), this package is sourced from ubuntu so they need to take action. The KDE team has been nothing if not responsive concerning this. Unfortunately the package maintainers have shown less enthusiasm.
To be clear, regarding my last comment, this is because it's a Neon package bug, which has correctly been designated an upstream bug. If you are using any other distro and you do not have the updated signond package, open a bug with said distro It's not a Plasma bug.
As a note, I reported this issue originally for Alpine Linux (not KDE Neon). It was a bug in signond that has been fixed already, but that package didn't get a new release since 2 years ago. In the case of Alpine Linux I made sure the fix is available in our signond package and it indeed resolves the issue. KDE Neon will have to do the same, although I guess this package is taken from Ubuntu for them in which case it has to happen there. Preferably signond just releases a new version but ok :/
Signond does fix the authentication issue for Google but the messaging itself doesn't work. Further its only for Google, not all the other services of which very few work.
Read the thread and comments here: https://bugs.kde.org/show_bug.cgi?id=426034
You're confused though, this issue IS NOT ABOUT MESSAGING. It's literally just about adding a Google account to the "Online accounts" section in the system settings. Anything else is out of the scope of this issue. You linked to this issue so I'm assuming that's a mistake and you meant to link to some other issue, e.g. https://bugs.kde.org/show_bug.cgi?id=420280. I see you talk about messaging issues there as well but that issue too IS NOT ABOUT MESSAGING. If you have an issue with the Telepathy components of KDE, file an issue for that, but don't bother unrelated issues with your complaints.
I know. Others have told me the same thing. The signind fix in arch does fix the auth issue. I just don't feel like filing 500 different bug reports with different services and different forums and 275 different people blah blah blah (obvious exaggeration). Telepathy is broke in so many ways its ridiculous and like I said in the other post should simple be pulled in its entirety from KDE. Every auth service is broke ('cept for Google now) messaging doesn't work, file transfers don't work. Etc. Etc. They haven't for several years. Its just silly to have such a broken system. I'll stop posting here, I just wanted to let the new comers to this/these bug(s) that its not worth the effort to try to get it to work because there are so many broken parts. As a user your like wahoo its fixed only to find out that its really not because something else is broken and its quite a let down considering how awesome telepathy could be if it did indeed work. KDE us awesome, GNU/Linux is awesome, and I will always support it both financially and many other ways. I just get frustrated at some of the ways things work. For example telepathy and all the different packages maintained by so many different people/orgs and one doesn't really communicate with the other... Que sera sera.
*** Bug 429446 has been marked as a duplicate of this bug. ***
*** Bug 429410 has been marked as a duplicate of this bug. ***
Hopefully the Ubuntu teams does something about this issue soon, because it means no Neon/Kubuntu 20.04 users can currently profit from kio-gdrive (that is, without making a bigger effort).
The problem is finally fixed with the new signond packages from focal-proposed. Many thanks to anyone who has contributed.
Just tried to add Google account, and the login window opened - which I guess is a huge success! However, after entering all credentials and confirming the login on mobile device, I get an empty 'Web authentification for google' window, and basically nothing happens... Closing this empty window brings error 'Access grant not present' on previous settings screen Versions: KDE Neon 5.20 KDE Plasma 5.20.5 Kde frameworks 5.78 QT 5.15.2
(In reply to Max from comment #46) > Just tried to add Google account, and the login window opened - which I > guess is a huge success! > However, after entering all credentials and confirming the login on mobile > device, I get an empty 'Web authentification for google' window, and > basically nothing happens... > Closing this empty window brings error 'Access grant not present' on > previous settings screen > > > Versions: > > KDE Neon 5.20 > KDE Plasma 5.20.5 > Kde frameworks 5.78 > QT 5.15.2 Similar error, but I got that message ("Access grant not present") just after click on "Google" or "OpenDesktop" in "Accounts w/o connection". The other accounts (ownCloud and NextCloud) shows me correctly a new window form. Operating System: openSUSE Leap 15.2 KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 Kernel Version: 5.3.18-lp152.72-default OS Type: 64-bit Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-9700K CPU @ 3.60GHz Memory: 15.4 GiB of RAM Graphics Processor: GeForce RTX 2060/PCIe/SSE2
April 9, 2023 Operating System: Ubuntu KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.2.0-10005-tuxedo (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i7-6600U CPU @ 2.60GHz Memory: 7.5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 520 Manufacturer: Dell Inc. Product Name: Latitude E7470 - Bug still exists