[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1055855: marked as done (We need to switch to a version that uses Qt WebEngine)

Your message dated Sun, 01 Dec 2024 19:34:46 +0100
with message-id <2127945.3VsfAaAtOV@grummly>
and subject line Fixed in version debian/0.17+git20231016.eef943f-1
has caused the Debian Bug report #1055855,
regarding We need to switch to a version that uses Qt WebEngine
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1055855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055855
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
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

--- End Message ---
--- Begin Message --- 
control: fixed -1 debian/0.17+git20231016.eef943f-1

--- End Message ---
Reply to: