Source: signon-ui Version: 0.17+16.04.20151125-1 Severity: important Control: tag -1 trixie
Continuing from Dmitry Shachnev (mitya57)'s message at the kaccounts-providers bug that is affected by this one: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054919#51 We need to switch to a signon-ui release that uses Qt WebEngine rather than the dead Qt WebKit, and we need to do this before trixie. Honestly, the sooner the better... When I was searching for a living upstream for signon-ui, I found that SUSE appears to use a version that has already switched to WebEngine: https://packagehub.suse.com/packages/signon-ui/0_17+20171022-bp155_3_16/ I didn't investigate more than that, but it looks like there is already a resolution. It might just be a question of switch to a more alive upstream, and/or replicating a SUSE patch series (I didn't check). Also, it might be a good idea import the changes as patches (whether from upstream, new upstream, and/or SUSE) so that we can backport them more easily to bookworm, because Google is not totally unreasonable to experimented with blacklisting a web browser user agent string that dates to 2016! Regards, Nicholas