Bug#1054919: kaccounts-providers: google authentication hang after username entry

[Alexis Murzeau <amubtdx@gmail.com>]

Hi,

Thanks for your reply!

On 29/10/2023 18:30, Nicholas D Steeves wrote:
> > The webpage issue is maybe caused by the use of Qt webkit, using an older
> > UserAgent probably causes Google to offer an older login page that works with
> > Qt webkit.
>
> That sounds plausible to me.  If that's the case then it seems like it
> may be better to patch Qt webkit.  I wonder if this is a case where
> whatever UserAgent Qt webkit validated is the one the package declares
> (where it shouldn't be overridden for the general case), or if everybody
> involved just forgot to update it?
>
> > As the UserAgent is required to make the login work, can it be added to the
> > package ?
>
> Agreed, either Qt webkit should be fixed, or else kaccount-providers
> should begin overriding UserAgent.  It's nice to see a Google issue that
> we can fix on our side!
>
> Best,
> Nicholas


I'm not sure how Qt webkit works, but I guess it behaves like a old
chrome browser. I don't know if it uses a different user agent, but
maybe Google doesn't recognize that it doesn't support newer web stuff.

Qt 6 doesn't seem to have Qt webkit anymore, but QtWebEngine instead.
I guess signon-ui should move to QtWebEngine instead but sadly upstream
seems rather dead :(, the previous signon-ui release was more than 5
years ago.

That's in fact why I've opened a report on this package, it seemed to be
the more feasible and realistic solution.
It is a chance that google signon can still work :)

--
Alexis Murzeau
PGP: B7E6 0EBB 9293 7B06 BDBC  2787 E7BD 1904 F480 937F                 |