Version: 4:22.12.3-1 Control: tag -1 upstream confirmed Hi, Thank you for reporting this bug. Alexis Murzeau <amubtdx@gmail.com> writes: > To fix this, I've put this line in /etc/signon-ui/webkit- > options.d/accounts.google.com.conf: > UserAgent = Mozilla/5.0 (X11; Linux x86_64; rv:57.0) Gecko/20100101 > Firefox/77.0 I've tested this proposal, and it fixes Google signon for me. This will transitively fix things like kio-gdrive that are broken in bookworm; For users of Google things, Bookworm's KDE is a poor user experience, or "bad story", compared to GNOME. > 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
Attachment:
signature.asc
Description: PGP signature