Bug 420280

Created attachment 127675 [details]
Empty web google authentication window

Possibly a duplicate of: https://bugs.kde.org/show_bug.cgi?id=415089

Hello, I had the same problem with a fresh Kubuntu 20.04 install. I managed to get around it by right-clicking on the empty window and pressing refresh (sometimes it takes a couple of tries). I was then able to finish the process and add Google Drive to Dolphin.

I have this problem.

STEPS TO REPRODUCE
1. Start Systemsettings5
2. Select Account on line
3: Add new account
4. Choose Google
5: Reappears entry form of point 3

In the journal i get this error (coredump) :

PID: 2062 (signond)
           UID: 1000 ()
           GID: 1000 ()
        Signal: 11 (SEGV)
     Timestamp: Thu 2020-06-04 17:13:51 CEST (1min 59s ago)
  Command Line: /usr/bin/signond
    Executable: /usr/bin/signond
 Control Group: /user.slice/user-1000.slice/user@1000.service/dbus.service
          Unit: user@1000.service
     User Unit: dbus.service
         Slice: user-1000.slice
     Owner UID: 1000 ()
       Boot ID: 271377a2609d41aa886e15bbebed5f1e
    Machine ID: 0feba72f41174a1497de6f6f4885718a
      Hostname: Arch
       Storage: /var/lib/systemd/coredump/core.signond.1000.271377a2609d41aa886e15bbebed5f1e.2062.1591283631000000000000.lz4
       Message: Process 2062 (signond) of user 1000 dumped core.
                
                Stack trace of thread 2062:
                #0  0x00007f18d46f5b2e n/a (libQt5Core.so.5 + 0x229b2e)
                #1  0x00005639d380973b n/a (signond + 0x4a73b)
                #2  0x00005639d37ea598 n/a (signond + 0x2b598)
                #3  0x00005639d37f3c4c n/a (signond + 0x34c4c)
                #4  0x00005639d37f9117 n/a (signond + 0x3a117)
                #5  0x00005639d380d82f n/a (signond + 0x4e82f)
                #6  0x00005639d3804116 n/a (signond + 0x45116)
                #7  0x00005639d38199a7 n/a (signond + 0x5a9a7)
                #8  0x00005639d3819b31 n/a (signond + 0x5ab31)
                #9  0x00007f18d4a3dfd6 n/a (libQt5DBus.so.5 + 0x20fd6)
                #10 0x00007f18d4a415cb n/a (libQt5DBus.so.5 + 0x245cb)
                #11 0x00007f18d4a41eba n/a (libQt5DBus.so.5 + 0x24eba)
                #12 0x00007f18d4a44388 n/a (libQt5DBus.so.5 + 0x27388)
                #13 0x00007f18d47ab0b2 _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2df0b2)
                #14 0x00007f18d477e670 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2b2670)
                #15 0x00007f18d4781183 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt5Core.so.5 + 0x2b5183)
                #16 0x00007f18d47d7bd4 n/a (libQt5Core.so.5 + 0x30bbd4)
                #17 0x00007f18d38bb43c g_main_context_dispatch (libglib-2.0.so.0 + 0x5243c)
                #18 0x00007f18d3908fa9 n/a (libglib-2.0.so.0 + 0x9ffa9)
                #19 0x00007f18d38ba221 g_main_context_iteration (libglib-2.0.so.0 + 0x51221)
                #20 0x00007f18d47d7211 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x30b211)
                #21 0x00007f18d477d01c _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b101c)
                #22 0x00007f18d47854a4 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2b94a4)
                #23 0x00005639d37cc521 n/a (signond + 0xd521)
                #24 0x00007f18d412b002 __libc_start_main (libc.so.6 + 0x27002)
                #25 0x00005639d37cc5ee n/a (signond + 0xd5ee)
                
                Stack trace of thread 2063:
                #0  0x00007f18d41f905f __poll (libc.so.6 + 0xf505f)
                #1  0x00007f18d3908f38 n/a (libglib-2.0.so.0 + 0x9ff38)
                #2  0x00007f18d38ba221 g_main_context_iteration (libglib-2.0.so.0 + 0x51221)
                #3  0x00007f18d47d7211 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x30b211)
                #4  0x00007f18d477d01c _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b101c)
                #5  0x00007f18d4598c32 _ZN7QThread4execEv (libQt5Core.so.5 + 0xccc32)
                #6  0x00007f18d4a34098 n/a (libQt5DBus.so.5 + 0x17098)
                #7  0x00007f18d4599e0f n/a (libQt5Core.so.5 + 0xcde0f)
                #8  0x00007f18d44b3422 start_thread (libpthread.so.0 + 0x9422)
                #9  0x00007f18d4203bf3 __clone (libc.so.6 + 0xffbf3)

Arch Linux 
KDE Plasma: 5.18.5
KDE Frameworks: 5.70.0
Qt: 5.15.0
Kernel: 5.6.15-arch1-1
64-bit

now i receive the signond (8.60-3) update.
fixes the problem for me.
Now i can add google account.

(In reply to kdedom from comment #6)
> now i receive the signond (8.60-3) update.
> fixes the problem for me.
> Now i can add google account.

That fixed signond crashing with Qt 5.15.0:
https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/signond&id=7e7dfd81b12dbfc62588d1355f2f7c4928598a05

Unrelated to the original report here though, which is probably a KUbuntu downstream issue IMHO or a "bug" in signon-ui.
It works fine here in openSUSE as well.

*** Bug 427184 has been marked as a duplicate of this bug. ***

*** Bug 426688 has been marked as a duplicate of this bug. ***

Created attachment 132431 [details]
gdrive

Got the same here :(

*** Bug 426034 has been marked as a duplicate of this bug. ***

*** Bug 427063 has been marked as a duplicate of this bug. ***

*** Bug 428247 has been marked as a duplicate of this bug. ***

related or possibly duplicates:
bug 426381
bug 420610
bug 420981
bug 423888

Git commit 619f6102318abe82a27eed399ebf9e3d66f407d0 by Nicolas Fella.
Committed on 26/10/2020 at 14:14.
Pushed by nicolasfella into branch 'master'.

[kcm] Show account creation error in the UI

Display the error message we get from the account creation job in the UI instead of silently failing.

M  +16   -1    src/kcm/package/contents/ui/AvailableAccounts.qml

https://invent.kde.org/network/kaccounts-integration/commit/619f6102318abe82a27eed399ebf9e3d66f407d0

Git commit afa18ab77a33a9237115f22a0b8eb6ecd37167cc by Nicolas Fella.
Committed on 26/10/2020 at 14:17.
Pushed by nicolasfella into branch 'release/20.08'.

[kcm] Show account creation error in the UI

Display the error message we get from the account creation job in the UI instead of silently failing.
(cherry picked from commit 619f6102318abe82a27eed399ebf9e3d66f407d0)

M  +16   -1    src/kcm/package/contents/ui/AvailableAccounts.qml

https://invent.kde.org/network/kaccounts-integration/commit/afa18ab77a33a9237115f22a0b8eb6ecd37167cc

*** Bug 426381 has been marked as a duplicate of this bug. ***

I added some proper error reporting to the UI. That won't magically fix it but hopefully gives some clues about what is happening

*** Bug 428247 has been marked as a duplicate of this bug. ***

i read the message by Domenico Panella and ran in the terminal signond
 and it just sat at the cursor.  So i then tried to add an online account after i left signond sit and kde system tray gave this message pop-up in the bottom right corner above the clock.

Message from syslogd@kde-neon-vaio at Oct 26 11:17:45 ... signond[8383]: SignonDaemon requires to register daemon's service Broadcast message from systemd-journald@kde-neon-vaio (Mon 2020-10-26 11:17:45 EDT): signond[8383]: SignonDaemon requires to register daemon's service 

then i went back to the terminal and got this message:

Broadcast message from systemd-journald@kde-neon-vaio (Mon 2020-10-26 11:21:16 EDT):

signond[8696]: SignonDaemon requires to register daemon's service

Aborted

and it dropped me back to the prompt.

kde-neon-vaio is my computer name.  I dunno of any of this helps but i figured it cant hurt...

Authentication and kio-gdrive work correctly in the Manjaro distribution so I switched to that.  Surprised it doesn't work in KDE Neon.

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

*** Bug 468828 has been marked as a duplicate of this bug. ***

*** Bug 422928 has been marked as a duplicate of this bug. ***

Can anyone reproduce this on a system that isn't Ubuntu based?

At least ubuntu appears to have a horribly outdated signon-ui that is defective in a number of ways.

Can't reproduce on Arch (signond 8.61-1) but on Tuxedo OS (Ubuntu based, signond 8.59). After entering the e-mail address it just keeps loading; when I cancel the error is "There was an error while trying to process the request: Access grant not present". So what Harald suspects about signond being outdated seems likely.

Can't reproduce on Alpine Linux with 8.61-r1 either. Even better, it works with a hardware key for 2FA which I didn't expect at all. So this definitely seems like an Ubuntu-only problem.

On Fedora Rawhide (pre-release of Fedora 39), I don't get a blank window as in the original bug report, but the Google authentication process gets stuck after submitting the email address, before the password prompt. The busy animation keeps playing forever.

If I close the window, the following message appears on stdout:

```
Error:
         "Access grant not present"
```

Versions:
 - libaccounts-qt5-1.16-8.fc39.x86_64
 - kaccounts-providers-23.04.3-2.fc39.x86_64
 - accounts-qml-module-0.7-10.fc39.x86_64
 - plasma-systemsettings-5.27.6-2.fc39.x86_64
 - signon-ui-0.15-20.fc39.x86_64
 - signon-8.60-13.fc39.x86_64

signon-ui 0.15 is even more ancient than ubuntu's.

I think it's safe to say that this is an issue with outdated signond stacks.

(In reply to Harald Sitter from comment #37)
> Can anyone reproduce this on a system that isn't Ubuntu based?
> 
> At least ubuntu appears to have a horribly outdated signon-ui that is
> defective in a number of ways.

I am seeing this on my Fedora Kinoite system,  as well as on my Neon ones that didn't already have this set up previously.

(In reply to Harald Sitter from comment #41)
> signon-ui 0.15 is even more ancient than ubuntu's.

Upstream seems dead:
https://launchpad.net/signon-ui

Arch has signon-ui 0.17, released on August 2015 from a fork on GitLab:
https://gitlab.com/accounts-sso/signon-ui/-/commits/master?ref_type=heads

Time for KDE to consider switching to GOA?
https://wiki.gnome.org/Projects/GnomeOnlineAccounts/Providers

Yep. From what I can tell gitlab is where it's at. To resolve this bug I expect we should do some poking to get new releases and distros to actually pick them up.

Notably https://gitlab.com/accounts-sso/signond/-/commits/master has recent work, so it doesn't seem dead.

I've emailed distro packagers about this: https://mail.kde.org/pipermail/distributions/2023-August/001397.html

So let's close it as a downstream issue. Hopefully distros will be shipping newer versions ASAP. To the extent that they don't, I'd encourage people to engage directly with their distro's packagers.

Not sure if you see something different Nate, bu https://gitlab.com/accounts-sso/signon-ui/-/commits/master?ref_type=heads only lists commits from 5 years ago. That doesn't seem "recent" to me. It is the commit I've been packaging in Alpine Linux but I really rather see something more maintained...

Ah I now see you were talking about signond in that case. Still, signon-ui is also important in this stack and yes, last commit was 5 years ago and the last tag was 8(!) years ago. That does seem dead to me, even if signond isn't.

Yeah the UI repo doesn't seem very active, but I guess that stuff doesn't change very often. The business logic repos seem to be alive enough.

I filed this Fedora bug to request upgrading signon-ui: https://bugzilla.redhat.com/show_bug.cgi?id=2230099

*** Bug 472654 has been marked as a duplicate of this bug. ***

September 14, 2023
- Bug still exists

Operating System: Kubuntu 22.04
KDE Plasma Version: 5.24.7
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3
Kernel Version: 6.2.0-32-generic (64-bit)
Graphics Platform: X11
Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor
Memory: 31.2 GB of RAM
Graphics Processor: AMD Radeon RX 6650 XT

Yes,, because it's still a downstream issue. There is nothing we (KDE) can do to fix it at this point unfortunately, Ubuntu needs to get their packages up to date.  That's why it's been marked as "resolved", because here is not where the problem is.

Indeed. If this is unclear, please see https://community.kde.org/Get_Involved/Issue_Reporting#Understand_what_the_resolution_statuses_mean.

(In reply to Natalie Clarius from comment #53)
> Yes,, because it's still a downstream issue. There is nothing we (KDE) can
> do to fix it at this point unfortunately, Ubuntu needs to get their packages
> up to date.  That's why it's been marked as "resolved", because here is not
> where the problem is.

So why is there no problem to connect google account with Gnome's app "Online Accounts" on the same system?

> So why is there no problem to connect google account with Gnome's app "Online Accounts" on the same system?

Good question. So you're saying is on the same Ubuntu version in a Gnome session that it's working? Maybe they are using a different account setup tool; I'll take a look.

(In reply to Neutrina from comment #55)

> 
> So why is there no problem to connect google account with Gnome's app
> "Online Accounts" on the same system?

(In reply to Natalie Clarius from comment #56)
> > So why is there no problem to connect google account with Gnome's app "Online Accounts" on the same system?
> 
> Good question. So you're saying is on the same Ubuntu version in a Gnome
> session that it's working? Maybe they are using a different account setup
> tool; I'll take a look.

Gnome is using their own system,  gnome-online-accounts, not signon-ui.

(In reply to Natalie Clarius from comment #56)
> Good question. So you're saying is on the same Ubuntu version in a Gnome
> session that it's working? Maybe they are using a different account setup
> tool; I'll take a look.

On the same Ubuntu version in a Gnome  session. That's right.

(In reply to Clay Weber from comment #57)
> (In reply to Neutrina from comment #55)
> Gnome is using their own system,  gnome-online-accounts, not signon-ui.

Ok. But Gnome's system does'n need updates from Ubuntu. It's working now. And how can we then suppose that the problem is in Ubuntu?

The problem in Ubuntu is that they ship an old and broken version of the thing that KDE uses to handle accounts (signon-ui). If Gnome does not use that but their own system, then they are not affected by the bug, even on the same system. It might be possible to do something similar as Gnome does in KDE, but that will take some time. It would still be preferable if Ubuntu decided to ship the version of signon-ui in which the problem is already fixed.

(In reply to Natalie Clarius from comment #59)
> The problem in Ubuntu is that they ship an old and broken version of the
> thing that KDE uses to handle accounts (signon-ui). If Gnome does not use
> that but their own system, then they are not affected by the bug, even on
> the same system. It might be possible to do something similar as Gnome does
> in KDE, but that will take some time. It would still be preferable if Ubuntu
> decided to ship the version of signon-ui in which the problem is already
> fixed.

More or less understandable... I would just like to see my Google Drive mounted in the file system. This is important for my work. So I'll try to find another way. After all, I like KDE more than Gnome.)

Yes, I can understand that. I'll look into how feasible it is for us to switch to a different method, while we wait for distributions to hopefully pick up our suggestion to update the packages.

(In reply to Neutrina from comment #55)
> (In reply to Natalie Clarius from comment #53)
> > Yes,, because it's still a downstream issue. There i
> So why is there no problem to connect google account with Gnome's app
> "Online Accounts" on the same system? 

The Gnome software code which deals with this is up to date with googles ever changing API's. 
The KDE software code which deals with this is _YEARS OUT OF DATE_ with googles API. 

This is not Ubuntu's problem. 

Until someone capable of updating the KDE code comes along and updates tge code, it will not work.

That's not quite true; the code KDE uses works just fine with more up to date distros such as Arch.

(In reply to Natalie Clarius from comment #63)
> That's not quite true; the code KDE uses works just fine with more up to
> date distros such as Arch.

I recently did a clean install of Manjaro (im not going to labour through a from svratch Arch install) - bug still exists for me.

Interesting. What is the version of signond and signon-ui there?

Re-closing as RESOLVED DOWNSTREAM again in the absence of new evidence of a KDE bug here. It's reasonable to expect distros to ship relatively recent software that our software depends on.

(In reply to techgo from comment #64)
> (In reply to Natalie Clarius from comment #63)
> > That's not quite true; the code KDE uses works just fine with more up to
> > date distros such as Arch.
> 
> I recently did a clean install of Manjaro (im not going to labour through a
> from svratch Arch install) - bug still exists for me.

Please file a separate report. Chances are that there is a different cause

(In reply to Neutrina from comment #58)
> 
> (In reply to Clay Weber from comment #57)
> > (In reply to Neutrina from comment #55)
> > Gnome is using their own system,  gnome-online-accounts, not signon-ui.
> 
> Ok. But Gnome's system does'n need updates from Ubuntu. It's working now.
> And how can we then suppose that the problem is in Ubuntu?

Because the signon-ui  in question is provided by Ubuntu, even if they aren't using it themselves any longer.

FWIW, I had signon-8.60-12.fc38.x86_64, signon-ui-0.15-19.fc38.x86_64 on this FC38 box and had the same issue reported here.

I have just installed the build of signon-ui mentioned in comment #50 from the COPR mentioned in that RHBZ and it fixes the problem for me. So I would guess it is Downstream.

https://bugzilla.redhat.com/show_bug.cgi?id=2230099

I've got signon-ui 0.17 and I'm still having this problem. The full version is 0.17+18.04.20171027+really20160406-0ubuntu3. After clicking around a few of the links shared here, I don't see any mentions of any newer versions of signon-ui than this. When I try to login to google from kde settings, I enter my email and the captcha and then it hangs. I'm using a new install of KDE Neon.

(In reply to aaronkplus2 from comment #70)
> I've got signon-ui 0.17 and I'm still having this problem. The full version
> is 0.17+18.04.20171027+really20160406-0ubuntu3. After clicking around a few
> of the links shared here, I don't see any mentions of any newer versions of
> signon-ui than this. When I try to login to google from kde settings, I
> enter my email and the captcha and then it hangs. I'm using a new install of
> KDE Neon.

If you read the RHBZ https://bugzilla.redhat.com/show_bug.cgi?id=2230099 and especially comment five https://bugzilla.redhat.com/show_bug.cgi?id=2230099#c5  the author posted that signon-ui 0.17 did not work. In comment Six he had fixed it. The fixes are in his github repo mentioned in same comment.

The fixes work for me, I'm just trying to help here.

I did not see that. But now that I see it, I'm not sure what to do with those fixes. I guess I'd have to build from source to be able to use those patches. I tried to build from source but had some trouble. It seemed like maybe I was missing some dependencies for signon-ui, but there weren't any instructions on how to install dependencies. It also said `NOTE: Remember to add your API headers into `headers.files' for installation!` so it sounds like maybe I need some more specialized knowledge to be able to build this myself.

I tested signon-ui-0.17+15.10.20150810-1.20171022git4368bb7.fc40.x86_64 from the Fedora COPR repo "hazel-bunny/ports".

I confirm it fixes this particular bug: the authentication window renders and you can type your login and password.

I still couldn't log into my Google account because it has 2FA enabled and the webengine doesn't seem to support USB security keys :-(
It seems KDE would be better off switching to gnome-online-accounts or other actively developed framework.

I can confirm that the  signon-ui from hazel-bunny:ports fixes the issue of not getting to the password prompt after entering the email address for gmail but as @Bernie Innocenti mentioned it still wont let you complete the setup if 2FA is enabled on the account. It just hangs and waits on the waiting to use your pass key step but the prompt or option to choose what pass key or what other 2FA method to use is never displayed. A temp workaround is to disable 2FA for the time being of setting up the account in KDE and re-enabling straight after!

(In reply to Bernie Innocenti from comment #73)
> I tested signon-ui-0.17+15.10.20150810-1.20171022git4368bb7.fc40.x86_64 from
> the Fedora COPR repo "hazel-bunny/ports".
> 
> I confirm it fixes this particular bug: the authentication window renders
> and you can type your login and password.

Thank you, this finally fixed the issue for me! For anyone else trying to solve this problem, here's the link to the rpm https://copr.fedorainfracloud.org/coprs/hazel-bunny/ports/package/signon-ui/ (click on the build ID to get to the downloads), and then you can convert the rpm to a deb (or anything else) using alien. I had to uninstall signon-ui-x11 and signon-ui-service before I could install this new package.

(In reply to aaronkplus2 from comment #75)
>For anyone else trying to solve this problem...
And thank you for describing in detail the actions for Debian (Ubuntu).

(In reply to aaronkplus2 from comment #75)
> (In reply to Bernie Innocenti from comment #73)
> > I tested signon-ui-0.17+15.10.20150810-1.20171022git4368bb7.fc40.x86_64 from
> > the Fedora COPR repo "hazel-bunny/ports".
> > 
> > I confirm it fixes this particular bug: the authentication window renders
> > and you can type your login and password.
> 
> Thank you, this finally fixed the issue for me! For anyone else trying to
> solve this problem, here's the link to the rpm
> https://copr.fedorainfracloud.org/coprs/hazel-bunny/ports/package/signon-ui/
> (click on the build ID to get to the downloads), and then you can convert
> the rpm to a deb (or anything else) using alien. I had to uninstall
> signon-ui-x11 and signon-ui-service before I could install this new package.

I'm the maintainer of that copr. As it helped so many people, I can cook up 2 PKGBUILDs when I'm free. One for Arch, one for debian & ubuntu (using makedeb). This is a downstream issue and I don't think upstream KDE bugzilla is suitable for this discussion.

(In reply to Dipta Biswas from comment #77)
> (In reply to aaronkplus2 from comment #75)
> > (In reply to Bernie Innocenti from comment #73)
> > > I tested signon-ui-0.17+15.10.20150810-1.20171022git4368bb7.fc40.x86_64 from
> > > the Fedora COPR repo "hazel-bunny/ports".
> > > 
> > > I confirm it fixes this particular bug: the authentication window renders
> > > and you can type your login and password.
> > 
> > Thank you, this finally fixed the issue for me! For anyone else trying to
> > solve this problem, here's the link to the rpm
> > https://copr.fedorainfracloud.org/coprs/hazel-bunny/ports/package/signon-ui/
> > (click on the build ID to get to the downloads), and then you can convert
> > the rpm to a deb (or anything else) using alien. I had to uninstall
> > signon-ui-x11 and signon-ui-service before I could install this new package.
> 
> I'm the maintainer of that copr. As it helped so many people, I can cook up
> 2 PKGBUILDs when I'm free. One for Arch, one for debian & ubuntu (using
> makedeb). This is a downstream issue and I don't think upstream KDE bugzilla
> is suitable for this discussion.

Yes, please.

(In reply to Bernie Innocenti from comment #73)
> I tested signon-ui-0.17+15.10.20150810-1.20171022git4368bb7.fc40.x86_64 from
> the Fedora COPR repo "hazel-bunny/ports".
> 
> I confirm it fixes this particular bug: the authentication window renders
> and you can type your login and password.
> 
> I still couldn't log into my Google account because it has 2FA enabled and
> the webengine doesn't seem to support USB security keys :-(
> It seems KDE would be better off switching to gnome-online-accounts or other
> actively developed framework.

Tried it recently. Now it is stuck on reading the drive after login. :(

*** Bug 475119 has been marked as a duplicate of this bug. ***

*** Bug 475361 has been marked as a duplicate of this bug. ***

*** Bug 475159 has been marked as a duplicate of this bug. ***

*** Bug 475710 has been marked as a duplicate of this bug. ***

Hi there!
I am using 
dpkg -l | grep signon-ui
ii  signon-ui-service                                        0.17+18.04.20171027+really20160406-0ubuntu3         all          D-Bus service file for signon-ui
ii  signon-ui-x11                                            0.17+18.04.20171027+really20160406-0ubuntu3         amd64        Single Sign-on UI
With Kubuntu Mantic everything up to date.
kcm_accounts get stuck in Web Authentication Google.
Just insert the email but after click next, nothing happens.

Take a look at comment #71 and the following comments.

ok! but that seems to me RPM based distro.
I am using deb based.
Where can I get a git clone?

You need to irritate the packagers and maintainers of your chosen distro until they fix the issue.

Oh! I was not aware about this detail! Let's rock!

But the question is, I already tried this in:
VoidLinux
Debian
Devuan
And now, Kubuntu
It's a lot of people to get irritate!

That's correct!

(In reply to Gilberto Ferreira from comment #89)
> But the question is, I already tried this in:
> VoidLinux
> Debian
> Devuan
> And now, Kubuntu
> It's a lot of people to get irritate!

Aren't they all Debian based? So the upstream at the top would just be Debian.

Well well well...
I wonder why it's works pretty well in Gnome, Xfce and Cinnamon.
Right now I am using Ubuntu Cinnamon and signon-ui-whatever works as expected.
It's seems only in KDE Plasma doesn't work.
Sadly!

(In reply to Gilberto Ferreira from comment #92)
> Well well well...
> I wonder why it's works pretty well in Gnome, Xfce and Cinnamon.
> Right now I am using Ubuntu Cinnamon and signon-ui-whatever works as
> expected.
> It's seems only in KDE Plasma doesn't work.
> Sadly!

GNOME & Cinnamon use gnome-online-accounts, not signon-ui

(In reply to Dipta Biswas from comment #93)
> (In reply to Gilberto Ferreira from comment #92)
> > Well well well...
> > I wonder why it's works pretty well in Gnome, Xfce and Cinnamon.
> > Right now I am using Ubuntu Cinnamon and signon-ui-whatever works as
> > expected.
> > It's seems only in KDE Plasma doesn't work.
> > Sadly!
> 
> GNOME & Cinnamon use gnome-online-accounts, not signon-ui

Ok! Did know that.
But, anyway, the question remain!

The question was already answered: connecting to online accounts in GNOME works because the GNOME code does not depend on a recent version of the signon-ui library.

(In reply to aaronkplus2 from comment #75)
> (In reply to Bernie Innocenti from comment #73)
> > I tested signon-ui-0.17+15.10.20150810-1.20171022git4368bb7.fc40.x86_64 from
> > the Fedora COPR repo "hazel-bunny/ports".
> > 
> > I confirm it fixes this particular bug: the authentication window renders
> > and you can type your login and password.
> 
> Thank you, this finally fixed the issue for me! For anyone else trying to
> solve this problem, here's the link to the rpm
> https://copr.fedorainfracloud.org/coprs/hazel-bunny/ports/package/signon-ui/
> (click on the build ID to get to the downloads), and then you can convert
> the rpm to a deb (or anything else) using alien. I had to uninstall
> signon-ui-x11 and signon-ui-service before I could install this new package.

I tried what you lined out there and uninstalling signon-ui-x11 and signon-ui-service, then installing the converted RPM caused all Online Accounts features to vanish. Did I miss something?

(In reply to kampelmuehler from comment #96)
> (In reply to aaronkplus2 from comment #75)
> > (In reply to Bernie Innocenti from comment #73)
> > > I tested signon-ui-0.17+15.10.20150810-1.20171022git4368bb7.fc40.x86_64 from
> > > the Fedora COPR repo "hazel-bunny/ports".
> > > 
> > > I confirm it fixes this particular bug: the authentication window renders
> > > and you can type your login and password.
> > 
> > Thank you, this finally fixed the issue for me! For anyone else trying to
> > solve this problem, here's the link to the rpm
> > https://copr.fedorainfracloud.org/coprs/hazel-bunny/ports/package/signon-ui/
> > (click on the build ID to get to the downloads), and then you can convert
> > the rpm to a deb (or anything else) using alien. I had to uninstall
> > signon-ui-x11 and signon-ui-service before I could install this new package.
> 
> I tried what you lined out there and uninstalling signon-ui-x11 and
> signon-ui-service, then installing the converted RPM caused all Online
> Accounts features to vanish. Did I miss something?

It's happens the same with me here!

All this issue is weird!
This week I tried Alpine Linux with KDE Plasma installed and shazam! KDE accounts works as suppose to do. Gmail and driver works nicely.
It's a shame Alpine Linux is musl based. Otherwise I could keep it, but many things simple doesn't work.

Unable to help if you're on a debian based distro. Debian has weird dependency names compared to fedora & arch. You can try adopting the PKGBUILD for arch to build with makedeb. Also advising against converting my rpm as your distro may have a different glibc version. Please ask your distro maintainer to fix the issue. If needed, my spec file is publicly available in both copr and github.

It's not weird at all that it works fine on Alpine Linux. The issue is known, an old version of signon-ui. Alpine Linux ships a newer version that _does_ work. Problem solved. (and Musl really shouldn't be an issue for 99% of the users, there is Flatpak for things like Steam anyway. Offtopic though)

I'm not sure why people are still going on about this issue, the cause is known (it's literally in the title) and the solution is also known. Distros just have to update their signon-ui package.

(In reply to Dipta Biswas from comment #77)
> (In reply to aaronkplus2 from comment #75)
> > (In reply to Bernie Innocenti from comment #73)
> > > I tested signon-ui-0.17+15.10.20150810-1.20171022git4368bb7.fc40.x86_64 from
> > > the Fedora COPR repo "hazel-bunny/ports".
> > > 
> > > I confirm it fixes this particular bug: the authentication window renders
> > > and you can type your login and password.
> > 
> > Thank you, this finally fixed the issue for me! For anyone else trying to
> > solve this problem, here's the link to the rpm
> > https://copr.fedorainfracloud.org/coprs/hazel-bunny/ports/package/signon-ui/
> > (click on the build ID to get to the downloads), and then you can convert
> > the rpm to a deb (or anything else) using alien. I had to uninstall
> > signon-ui-x11 and signon-ui-service before I could install this new package.
> 
> I'm the maintainer of that copr. As it helped so many people, I can cook up
> 2 PKGBUILDs when I'm free. One for Arch, one for debian & ubuntu (using
> makedeb). This is a downstream issue and I don't think upstream KDE bugzilla
> is suitable for this discussion.

Oh! Finally. It's work! It's freaking work!
I do this in Debian SID/TRIXIE:
1 - I downloaded the signon-ui-0.17+15.10.20150810-1.20171022git4368bb7.fc37.x86_64.rpm
2 - Used alien:
sudo alien signon-ui-0.17+15.10.20150810-1.20171022git4368bb7.fc37.x86_64.rpm
3 - then tried to install: sudo apt install ./signon-ui_0.17+15.10.20150810-2.20171022_amd64.deb
But apt complain about previously package installed blah blah
So I do:
sudo dpkg --force-all -i signon-ui_0.17+15.10.20150810-2.20171022_amd64.deb
And works fine to me!
Thanks a lot.

(In reply to Gilberto Ferreira from comment #101)
> (In reply to Dipta Biswas from comment #77)
> > (In reply to aaronkplus2 from comment #75)
> > > (In reply to Bernie Innocenti from comment #73)
> > > > I tested signon-ui-0.17+15.10.20150810-1.20171022git4368bb7.fc40.x86_64 from
> > > > the Fedora COPR repo "hazel-bunny/ports".
> > > > 
> > > > I confirm it fixes this particular bug: the authentication window renders
> > > > and you can type your login and password.
> > > 
> > > Thank you, this finally fixed the issue for me! For anyone else trying to
> > > solve this problem, here's the link to the rpm
> > > https://copr.fedorainfracloud.org/coprs/hazel-bunny/ports/package/signon-ui/
> > > (click on the build ID to get to the downloads), and then you can convert
> > > the rpm to a deb (or anything else) using alien. I had to uninstall
> > > signon-ui-x11 and signon-ui-service before I could install this new package.
> > 
> > I'm the maintainer of that copr. As it helped so many people, I can cook up
> > 2 PKGBUILDs when I'm free. One for Arch, one for debian & ubuntu (using
> > makedeb). This is a downstream issue and I don't think upstream KDE bugzilla
> > is suitable for this discussion.
> 
> Oh! Finally. It's work! It's freaking work!
> I do this in Debian SID/TRIXIE:
> 1 - I downloaded the
> signon-ui-0.17+15.10.20150810-1.20171022git4368bb7.fc37.x86_64.rpm
> 2 - Used alien:
> sudo alien signon-ui-0.17+15.10.20150810-1.20171022git4368bb7.fc37.x86_64.rpm
> 3 - then tried to install: sudo apt install
> ./signon-ui_0.17+15.10.20150810-2.20171022_amd64.deb
> But apt complain about previously package installed blah blah
> So I do:
> sudo dpkg --force-all -i signon-ui_0.17+15.10.20150810-2.20171022_amd64.deb
> And works fine to me!
> Thanks a lot.

Just an update.
After reboot, I got this error:
Expired or missing access token for google account
So then I tried the signon-ui-0.17+15.10.20150810-1.20171022git4368bb7.fc40.x86_64.rpm for Fedora 40.
After do an alien convertion and installed it with apt install signon-ui_0.17+15.10.20150810-2.20171022_amd64.deb, it's works as a charm.

(In reply to Gilberto Ferreira from comment #101)
> (In reply to Dipta Biswas from comment #77)
> > (In reply to aaronkplus2 from comment #75)
> > > (In reply to Bernie Innocenti from comment #73)
> > > > I tested signon-ui-0.17+15.10.20150810-1.20171022git4368bb7.fc40.x86_64 from
> > > > the Fedora COPR repo "hazel-bunny/ports".
> > > > 
> > > > I confirm it fixes this particular bug: the authentication window renders
> > > > and you can type your login and password.
> > > 
> > > Thank you, this finally fixed the issue for me! For anyone else trying to
> > > solve this problem, here's the link to the rpm
> > > https://copr.fedorainfracloud.org/coprs/hazel-bunny/ports/package/signon-ui/
> > > (click on the build ID to get to the downloads), and then you can convert
> > > the rpm to a deb (or anything else) using alien. I had to uninstall
> > > signon-ui-x11 and signon-ui-service before I could install this new package.
> > 
> > I'm the maintainer of that copr. As it helped so many people, I can cook up
> > 2 PKGBUILDs when I'm free. One for Arch, one for debian & ubuntu (using
> > makedeb). This is a downstream issue and I don't think upstream KDE bugzilla
> > is suitable for this discussion.
> 
> Oh! Finally. It's work! It's freaking work!
> I do this in Debian SID/TRIXIE:
> 1 - I downloaded the
> signon-ui-0.17+15.10.20150810-1.20171022git4368bb7.fc37.x86_64.rpm
> 2 - Used alien:
> sudo alien signon-ui-0.17+15.10.20150810-1.20171022git4368bb7.fc37.x86_64.rpm
> 3 - then tried to install: sudo apt install
> ./signon-ui_0.17+15.10.20150810-2.20171022_amd64.deb
> But apt complain about previously package installed blah blah
> So I do:
> sudo dpkg --force-all -i signon-ui_0.17+15.10.20150810-2.20171022_amd64.deb
> And works fine to me!
> Thanks a lot.

Dirty - but works :)

Reported downstream https://bugs.launchpad.net/ubuntu/+source/signon-ui/+bug/2055195

I'm still dealing with this bug on Arch Linux, even tho the signon-ui package version is quite new, 0.17+20231016-2.1. When running systemsettings from the terminal and trying to login to my account, I get this errors on the terminal:

file:///usr/lib/qt6/qml/org/kde/kirigami/Dialog.qml:334:18: QML ScrollView: Binding loop detected for property "calculatedImplicitHeight"
file:///usr/lib/qt6/qml/org/kde/kirigami/Dialog.qml:386:33: QML Binding: Binding loop detected for property "value"
"google"
Looking for plugin ""
Starting auth session with "oauth2"
Info:
        Id: 3
        caption: "google"
        owner: ""
        userName: ""
qt.dbus.integration: Could not disconnect "com.google.code.AccountsSSO.SingleSignOn.Identity" to "destroyed(QObject*)" : Pointers are not supported: QObject*
Error:
         "Access grant not present"

I'm using Wayland and nvidia drivers. I was able to login once in the Xorg session, but it doesn't always work, and even when I get to login successfully, the google drive integration in Dolphin randomly stops working when accessing folders.

In Solus has been solved 1 year ago. I tested it and it's working. Apparently the "involuntary" fix was change from qt5-webengine to q5-webkit in that case

https://discuss.kde.org/t/kde-online-accounts-not-signing-in/3411/7

In Solus has been solved 1 year ago. I tested it and it's working. Apparently the "involuntary" fix was change from qt5-webengine to q5-webkit in that case

https://discuss.kde.org/t/kde-online-accounts-not-signing-in/3411/7(In reply to javi.fd from comment #106)
> In Solus has been solved 1 year ago. I tested it and it's working.
> Apparently the "involuntary" fix was change from qt5-webengine to q5-webkit
> in that case
> 
> https://discuss.kde.org/t/kde-online-accounts-not-signing-in/3411/7

(In reply to javi.fd from comment #106)
> In Solus has been solved 1 year ago. I tested it and it's working.
> Apparently the "involuntary" fix was change from qt5-webengine to q5-webkit
> in that case
> 
> https://discuss.kde.org/t/kde-online-accounts-not-signing-in/3411/7

Sorry, i wrote it wrong, from q5-webkit to qt5-webengine

1 There is a problem that has been reported by users of Arch and derived distributions. Before entering the password, the user goes to a screen that says: This browser or app is not secure.

This problem is in a patch called fake-user-agent.patch in the signon-ui package. It is not a Plasma problem, but I had not found information about the cause of the error anywhere. Repackaging without the patch makes this error disappear.

2 - The second error probably occurs in all distributions. In the last 2 days I tested the following distributions: BigLinux, Manjaro, Fedora, KDE Neon, OpenSuse and Solus. The error occurred in all of them.
The error occurs after entering the password: This app is blocked

The problem is in parts of the file: /usr/share/accounts/providers/kde/google.provider

If you remove the line with the content:
'https://www.googleapis.com/auth/drive',

The problem does not occur, the account is added, but there is no way to access or send files to Google Drive, if you replace it with this other line, then it is possible to send files, but not access the files that were already in Google Drive:
'https://www.googleapis.com/auth/drive.file',

I did hundreds of tests and modifications until I got to the point where I went to see how it was being done in Gnome, so I adapted the google.provider file to use the data used in Gnome and it worked, Google Drive became fully functional.
The real problem seems to be in the ClientID used in kaccounts-providers: 317066460457-pkpkedrvt2ldq6g2hj1egfka2n7vpuoo.apps.googleusercontent.com


The Google Provider file using the Gnome ClientID ( /usr/share/accounts/providers/kde/google.provider ) and working fine:

<?xml version="1.0" encoding="UTF-8"?>
<provider id="google">
  <name>Google</name>
  
  <description>GNOME-ID, Google Drive and YouTube</description>
  <icon>im-google</icon>
  <translations>kaccounts-providers</translations>
  <domains>.*google\.com</domains>

  <template>
    <group name="auth">
      <setting name="method">oauth2</setting>
      <setting name="mechanism">web_server</setting>
      <group name="oauth2">
        <group name="web_server">
          <setting name="Host">accounts.google.com</setting>
          <setting name="AuthPath">o/oauth2/auth?access_type=offline</setting>
          <setting name="TokenPath">o/oauth2/token</setting>
          <setting name="RedirectUri">http://localhost/oauth2callback</setting>
          
          <setting name="ResponseType">code</setting>
          <setting type="as" name="Scope">[
              'https://www.googleapis.com/auth/userinfo.email',
              'https://www.googleapis.com/auth/userinfo.profile',
              'https://www.googleapis.com/auth/calendar',
              'https://www.googleapis.com/auth/tasks',
              'https://www.googleapis.com/auth/drive'
          ]</setting>
          <setting type="as" name="AllowedSchemes">['https']</setting>
          <setting name="ClientId">44438659992-7kgjeitenc16ssihbtdjbgguch7ju55s.apps.googleusercontent.com</setting>
          <setting name="ClientSecret">-gMLuQyDiI0XrQS_vx_mhuYF</setting>
          <setting type="b" name="ForceClientAuthViaRequestBody">true</setting>
        </group>
      </group>
    </group>
  </template>
</provider>