Bug#1002182: qutebrowser: FTBFS: AttributeError: 'NoneType' object has no attribute 'split'

[Florian Bruhin]

Hi,

On Tue, Dec 21, 2021 at 07:12:26PM +0100, Axel Beckert wrote:
> > That seems like a false-positive: The dataclasses backport is only
> > required for Python 3.6, but Debian sets "Depends: python3 (>= 3.7)"
> > already. 
> […]
> > That smells like a bug in dh-python.
> 
> I tried downgrading dh-python until it no more FTBFS. It doesn't FTBFS
> with dh-python 5.2024 and the first version it FTBFS is 5.20211213.
> 
> The changelog entry of 5.20211213 contains these potential causes, at
> least from my point of view:
> 
>* Handle dist-info extra sections the same way we do for requirements.txt.
>  (closes: 998374)

That seems to be related to the "flit" integration, a build system which
qutebrowser does not use: https://flit.readthedocs.io/

>* Add new pep517 plugin that uses python3-build + python3-installer to 
> build
>  Python modules as wheels and then unpack the wheel. This is the new
>  interface used by modern Python packaging tools. (Closes: #984824)

Could be, but it't not :)

> Full entry (in cases something didn't look suspicious to me) at
> https://packages.qa.debian.org/d/dh-python/news/20211214T010008Z.html
> 
> Florian: Any idea which of these might have broken this?

It's "Add support for environment markers.". Environment markers are
basically conditional dependencies, e.g. for a given Python version or
OS only.

The crash happens here:
https://salsa.debian.org/python-team/tools/dh-python/-/blob/5.20211217/dhpython/pydist.py#L522
because "dependency" is None.

That's coming from here:
https://salsa.debian.org/python-team/tools/dh-python/-/blob/5.20211217/dhpython/pydist.py#L516
i.e. is the return value of "guess_deps".

Looking at that, we spot our error message about dataclasses:
https://salsa.debian.org/python-team/tools/dh-python/-/blob/5.20211217/dhpython/pydist.py#L313-317

...but also a strange commented out "return pname" which has been around
for 7 years:
https://salsa.debian.org/python-team/tools/dh-python/-/commit/de7db9bd0021cee65e477f11cd69cfd93350bd2e

Due to the commented out return, the function ends and implicitly
returns None.

The code which crashes due to that None value is very recent:
https://salsa.debian.org/python-team/tools/dh-python/-/commit/832f01c9c7da22a1d00887d8ce0e6be9893bdf3e

So I suppose it would be good if someone could forward this do
dh-python, I use the Debian bugtracker too seldom to know what the best
way to do this would be (but if preferable, I can open a new bug).

> And is the suggestion to add "dataclasses python3-dataclasses" line to
> debian/py3dist-overrides something we should simply do or is this an
> issue which we should make the dh-python maintainers aware of? I must
> admit, I still don't understand what this is dh-python argues about.
> Maybe someone has some more Python insight for a non-pythonista?

Perhaps both. So what dh-python seems to be doing here is to look at
the dependencies declared in a "requirements.txt" (a somewhat common
way to specify dependencies for Python projects) and check whether the
Debian packaging mirrors those requirements as well. Here is the line in
question:

https://github.com/qutebrowser/qutebrowser/blob/v2.4.0/requirements.txt#L5

So this declares that qutebrowser needs the "dataclasses" backport for
Python versions older than 3.7 (it still supports Python 3.6, though
that will change as soon as 3.0.0 is finished:
https://github.com/qutebrowser/qutebrowser/issues/6905).

However, the Debian package for qutebrowser declares
"Depends: python3 (>= 3.7)", so that dependency actually is irrelevant
for Debian.

Should dh-python handle that case? Well, maybe, but it sure shouldn't
crash.

Florian

-- 
m...@the-compiler.org | https://www.qutebrowser.org 
   https://bruhin.software/ | https://github.com/sponsors/The-Compiler/
   GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
 I love long mails! | https://email.is-not-s.ms/


signature.asc
Description: PGP signature

Bug#1002182: qutebrowser: FTBFS: AttributeError: 'NoneType' object has no attribute 'split'

[Florian Bruhin]

Hi,

On Tue, Dec 21, 2021 at 05:15:47PM +0100, Lucas Nussbaum wrote:
> > I: dh_python3 pydist:313: Cannot find package that provides dataclasses. 
> > Please add package that provides it to Build-Depends or add "dataclasses 
> > python3-dataclasses" line to debian/py3dist-overrides or add proper 
> > dependency to Depends by hand and ignore this info.

That seems like a false-positive: The dataclasses backport is only
required for Python 3.6, but Debian sets "Depends: python3 (>= 3.7)"
already. 

> > Traceback (most recent call last):
> >   File "/usr/bin/dh_python3", line 280, in 
> > main()
> >   File "/usr/bin/dh_python3", line 201, in main
> > dependencies.parse(stats, options)
> >   File "/usr/share/dh-python/dhpython/depends.py", line 242, in parse
> > deps = parse_pydep(self.impl, fn, bdep=self.bdep, **section_options)
> >   File "/usr/share/dh-python/dhpython/pydist.py", line 522, in parse_pydep
> > for part in dependency.split(','))
> > AttributeError: 'NoneType' object has no attribute 'split'

That smells like a bug in dh-python.

Florian (upstream maintainer)

-- 
m...@the-compiler.org | https://www.qutebrowser.org 
   https://bruhin.software/ | https://github.com/sponsors/The-Compiler/
   GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
 I love long mails! | https://email.is-not-s.ms/


signature.asc
Description: PGP signature

Bug#991319: unblock: qutebrowser/2.0.2-2

[Florian Bruhin]

Hi,

I'm the upstream for qutebrowser. Thanks Axel for taking care of this!

On Thu, Jul 15, 2021 at 03:24:12AM +0200, Axel Beckert wrote:
> The upload adds a patch which updates the pointers to qutebrowser's
> IRC channel which — like many other projects — recently had to change
> from Freenode to Libera.Chat due to a hostile takeover of the prject's
> IRC channel on Freenode.

Indeed - for more context:
https://blog.qutebrowser.org/qutebrowser-moving-to-libera-chat.html

> According to upstream, from time to time people still join the
> project's old channel on Freenode. It is suspected that outdated links
> in packaged versions of qutebrowser are one source for this.

At least that's what people told me when I asked them how they found the
old channel. I do not know how many of them are using Debian stable,
compared to Ubuntu or other distributions not shipping the latest
upstream release.

Still, at some point I'd like to leave the old channel without having to
redirect people to the proper place (I can't set the topic, because I
lost my admin access to the old channel as part of Freenode's actions).

> Author: Axel Beckert 
> Description: Update IRC links to Libera Chat
>  Based on a patch by Florian Bruhin 
> Forwarded: not-needed

For context, I suggested a patch which only patches the asciidoc files,
while the release tarballs ship HTML files.

I've taken a quick look at the diff, looks good to me.

Florian

-- 
m...@the-compiler.org | https://www.qutebrowser.org 
   https://bruhin.software/ | https://github.com/sponsors/The-Compiler/
   GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
 I love long mails! | https://email.is-not-s.ms/


signature.asc
Description: PGP signature

Bug#970478: ERROR: Renderer process crashed when using qtwebengine backend.

[Florian Bruhin]

Hi Dmitry,

On Tue, Sep 22, 2020 at 03:56:15PM +0300, Dmitry Shachnev wrote:
> Hi Florian!
> 
> On Tue, Sep 22, 2020 at 01:48:17PM +0200, Florian Bruhin wrote:
> > reassign -1 libqt5webenginecore5 5.14.2+dfsg1-5
> > thanks
> >
> > Hey,
> >
> > Since you can reproduce this with Falkon, it definitely isn't an issue
> > in qutebrowser. Reassigning this to QtWebEngine. Let's hope it works,
> > I'm not too experienced with using Debian's BTS - whoever is on the
> > receiving end, please let me know if I messed up something :)
> 
> I see you ended up sending a mail to cont...@bugs.debian.org. Another way is
> sending a mail to the bug itself but prefixing the commands with "Control: ".

Ah, thanks! I guess with that, the "-1" would've worked properly as
well. I ended up getting an error and trying again with explicitly
specifying the bug number.

> > Thanks! For reference, here's a demangled version of the relevant stack
> > trace:
> >
> > #0  0x7f6842b6928f 
> > blink::CompositedLayerMapping::ComputeBoundsOfOwningLayer(blink::PaintLayer 
> > const*, blink::IntRect&, blink::IntRect&, blink::PhysicalOffset&, 
> > blink::IntPoint&) (libQt5WebEngineCore.so.5   0x462928f)
> > #1  0x7f6842b74054 
> > blink::CompositedLayerMapping::UpdateGraphicsLayerGeometry(blink::PaintLayer
> >  const*, blink::PaintLayer const*, WTF::Vector > WTF::PartitionAllocator>&, blink::GraphicsLayerUpdater::UpdateContext&) 
> > (libQt5WebEngineCore.so.5   0x4634054)
> > #2  0x7f6842b76561 
> > blink::GraphicsLayerUpdater::UpdateRecursive(blink::PaintLayer&, 
> > blink::GraphicsLayerUpdater::UpdateType, 
> > blink::GraphicsLayerUpdater::UpdateContext&, 
> > WTF::Vector&) 
> > (libQt5WebEngineCore.so.5   0x4636561)
> > #3  0x7f6842b764ca 
> > blink::GraphicsLayerUpdater::UpdateRecursive(blink::PaintLayer&, 
> > blink::GraphicsLayerUpdater::UpdateType, 
> > blink::GraphicsLayerUpdater::UpdateContext&, 
> > WTF::Vector&) 
> > (libQt5WebEngineCore.so.5   0x46364ca)
> > #4  0x7f6842b764ca 
> > blink::GraphicsLayerUpdater::UpdateRecursive(blink::PaintLayer&, 
> > blink::GraphicsLayerUpdater::UpdateType, 
> > blink::GraphicsLayerUpdater::UpdateContext&, 
> > WTF::Vector&) 
> > (libQt5WebEngineCore.so.5   0x46364ca)
> > #5  0x7f6842b764ca 
> > blink::GraphicsLayerUpdater::UpdateRecursive(blink::PaintLayer&, 
> > blink::GraphicsLayerUpdater::UpdateType, 
> > blink::GraphicsLayerUpdater::UpdateContext&, 
> > WTF::Vector&) 
> > (libQt5WebEngineCore.so.5   0x46364ca)
> > [...]
> >
> > From a quick search in QtWebEngine's and Chromium's bugtracker I
> > couldn't find anything relevant... I also don't remember seeing this
> > stacktrace before.
> 
> I also have no clue about this. Unfortunately we build Qt WebEngine without
> any debugging information so it is impossible to get the line numbers.
> But I see the ComputeBoundsOfOwningLayer method changed between Qt 5.14 and
> 5.15, so let's see if upgrading to Qt 5.15 helps here (I am working on it).

Let me note that QtWebEngine 5.15.1 has another bug causing frequent
renderer process crashes: https://bugreports.qt.io/browse/QTBUG-86752

I'm currently trying to bisect it because it seems to work in the
current 5.15 branch - but I suppose it might be the Chromium update
between 5.15.1 and 5.15(.2) fixing this again.

Thus, I'd recommend either staying with 5.15.0, or using the current
5.15 HEAD (or waiting for 5.15.2).

Florian

-- 
m...@the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org 
   https://bruhin.software/ | https://github.com/sponsors/The-Compiler/
   GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
 I love long mails! | https://email.is-not-s.ms/


signature.asc
Description: PGP signature

Bug#970478: ERROR: Renderer process crashed when using qtwebengine backend.

[Florian Bruhin]

reassign -1 libqt5webenginecore5 5.14.2+dfsg1-5
thanks

Hey,

Since you can reproduce this with Falkon, it definitely isn't an issue
in qutebrowser. Reassigning this to QtWebEngine. Let's hope it works,
I'm not too experienced with using Debian's BTS - whoever is on the
receiving end, please let me know if I messed up something :)

On Mon, Sep 21, 2020 at 05:57:03PM -0300, felipe wrote:
> Attaching 'coredump info temp-basedir with dbgsym.txt'
> and 'coredump info qt-flag single-process with dbgsym'.

Thanks! For reference, here's a demangled version of the relevant stack
trace:

#0  0x7f6842b6928f 
blink::CompositedLayerMapping::ComputeBoundsOfOwningLayer(blink::PaintLayer 
const*, blink::IntRect&, blink::IntRect&, blink::PhysicalOffset&, 
blink::IntPoint&) (libQt5WebEngineCore.so.5   0x462928f)
#1  0x7f6842b74054 
blink::CompositedLayerMapping::UpdateGraphicsLayerGeometry(blink::PaintLayer 
const*, blink::PaintLayer const*, WTF::Vector&, blink::GraphicsLayerUpdater::UpdateContext&) 
(libQt5WebEngineCore.so.5   0x4634054)
#2  0x7f6842b76561 
blink::GraphicsLayerUpdater::UpdateRecursive(blink::PaintLayer&, 
blink::GraphicsLayerUpdater::UpdateType, 
blink::GraphicsLayerUpdater::UpdateContext&, WTF::Vector&) (libQt5WebEngineCore.so.5   0x4636561)
#3  0x7f6842b764ca 
blink::GraphicsLayerUpdater::UpdateRecursive(blink::PaintLayer&, 
blink::GraphicsLayerUpdater::UpdateType, 
blink::GraphicsLayerUpdater::UpdateContext&, WTF::Vector&) (libQt5WebEngineCore.so.5   0x46364ca)
#4  0x7f6842b764ca 
blink::GraphicsLayerUpdater::UpdateRecursive(blink::PaintLayer&, 
blink::GraphicsLayerUpdater::UpdateType, 
blink::GraphicsLayerUpdater::UpdateContext&, WTF::Vector&) (libQt5WebEngineCore.so.5   0x46364ca)
#5  0x7f6842b764ca 
blink::GraphicsLayerUpdater::UpdateRecursive(blink::PaintLayer&, 
blink::GraphicsLayerUpdater::UpdateType, 
blink::GraphicsLayerUpdater::UpdateContext&, WTF::Vector&) (libQt5WebEngineCore.so.5   0x46364ca)
#6  0x7f6842b764ca 
blink::GraphicsLayerUpdater::UpdateRecursive(blink::PaintLayer&, 
blink::GraphicsLayerUpdater::UpdateType, 
blink::GraphicsLayerUpdater::UpdateContext&, WTF::Vector&) (libQt5WebEngineCore.so.5   0x46364ca)
#7  0x7f6842b766bd 
blink::GraphicsLayerUpdater::Update(blink::PaintLayer&, 
WTF::Vector&) 
(libQt5WebEngineCore.so.5   0x46366bd)
#8  0x7f6842b76b3d 
blink::PaintLayerCompositor::UpdateIfNeeded(blink::DocumentLifecycle::LifecycleState,
 blink::CompositingReasonsStats&) (libQt5WebEngineCore.so.5   0x4636b3d)
#9  0x7f6842b780d0 
blink::PaintLayerCompositor::UpdateIfNeededRecursiveInternal(blink::DocumentLifecycle::LifecycleState,
 blink::CompositingReasonsStats&) (libQt5WebEngineCore.so.5   0x46380d0)
#10 0x7f6842b78409 
blink::PaintLayerCompositor::UpdateIfNeededRecursive(blink::DocumentLifecycle::LifecycleState)
 (libQt5WebEngineCore.so.5   0x4638409)
#11 0x7f6842579377 
blink::LocalFrameView::RunCompositingLifecyclePhase(blink::DocumentLifecycle::LifecycleState)
 (libQt5WebEngineCore.so.5   0x4039377)
#12 0x7f68425839d9 
blink::LocalFrameView::UpdateLifecyclePhasesInternal(blink::DocumentLifecycle::LifecycleState).part.0
 (libQt5WebEngineCore.so.5   0x40439d9)
#13 0x7f6842583e14 
blink::LocalFrameView::UpdateLifecyclePhases(blink::DocumentLifecycle::LifecycleState,
 blink::DocumentLifecycle::LifecycleUpdateReason) (libQt5WebEngineCore.so.5   
0x4043e14)
#14 0x7f6842b11564 
blink::PageAnimator::UpdateAllLifecyclePhases(blink::LocalFrame&, 
blink::DocumentLifecycle::LifecycleUpdateReason) (libQt5WebEngineCore.so.5   
0x45d1564)
#15 0x7f68424cf16c 
blink::WebViewImpl::UpdateLifecycle(blink::WebWidget::LifecycleUpdate, 
blink::WebWidget::LifecycleUpdateReason) (libQt5WebEngineCore.so.5   0x3f8f16c)
#16 0x7f684332cafa content::RenderWidget::UpdateVisualState() 
(libQt5WebEngineCore.so.5   0x4decafa)
#17 0x7f68416a92c6 
cc::ProxyMain::BeginMainFrame(std::unique_ptr >) 
(libQt5WebEngineCore.so.5   0x31692c6)
#18 0x7f68416a1633 
base::internal::Invoker >), 
base::WeakPtr, std::unique_ptr > >, void 
()>::RunOnce(base::internal::BindStateBase*) (libQt5WebEngineCore.so.5   
0x3161633)
#19 0x7f6840b043a4 base::TaskAnnotator::RunTask(char const*, 
base::PendingTask*) (libQt5WebEngineCore.so.5   0x25c43a4)
#20 0x7f6840b17337 
base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoWorkImpl(base::sequence_manager::LazyNow*,
 bool*) (libQt5WebEngineCore.so.5   0x25d7337)
#21 0x7f6840b177b8 
base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoSomeWork()
 (libQt5WebEngineCore.so.5   0x25d77b8)
#22 0x7f6840acdba6 
base::MessagePumpDefault::Run(base::MessagePump::Delegate*) 
(libQt5WebEngineCore.so.5   0x258dba6)
#23 0x7f6840b14cdf 
base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::Run(bool,
 base::TimeDelta) (libQt5WebEngineCore.so.5   0x25d4cdf)

Bug#970478: ERROR: Renderer process crashed when using qtwebengine backend.

[Florian Bruhin]

Hey again,

On Mon, Sep 21, 2020 at 12:17:57PM -0300, felipe wrote:
> Hey,
> 
> > For 1), do you see those QtWebEngineProcess crashes when you run
> > "coredumpctl list"? If so, can you please show "coredumpctl info PID"
> > with the PID from the list? If not, can you check whether you can
> > reproduce them (making the entire browser crash) when you run with
> > "--qt-flag single-process"?
> 
> I have attached  coredumpctl info when it crashes using --temp-basedir.
> 
> Running with:
>   $ qutebrowser --qt-flag single-process
>   [1]5850 illegal hardware instruction (core dumped)  qutebrowser 
> --qt-flag single-process
> The browser starts with a blank page and when I try to open any webpage, it 
> crashes.
> 
> I have also attached coredumpctl of this crash.
> 
> 
> > For 2), it looks like there's no libqt5webengine5-dbg{,sym} package in
> > the debian archives. Could you check if you find them if you run e.g.
> > find-dbgsym-packages on /usr/lib/x86_64-linux-gnu/libQt5WebEngine.so.5.14.2
> > https://wiki.debian.org/HowToGetABacktrace#Installing_the_debugging_symbols
> 
> After adding deb 'http://deb.debian.org/debian-debug/ unstable-debug
> main' to my '/etc/apt/sources.list' and installing
> 'libfile-slurper-perl' and 'libfile-which-perl', I find some debug
> symbols available:
> 
>   $ find-dbgsym-packages 
> /usr/lib/x86_64-linux-gnu/libQt5WebEngine.so.5.14.2
> 
> I have attached the file 'find-dbgsym-packages.txt'

You will need at lesat libqt5webengine5-dbgsym and perhaps
libqt5webenginecore5-dbgsym as well.

From what I see in the attached coredumpctl outputs, those happened
before you installed the symbols, right? Can you try again, so that
you'd hopefully get a stacktrace which says more than just "n/a" for the
entries? :)

> > If getting more info via coredumpctl didn't work, but you can reproduce
> > with --qt-flag single-process, can you please do something like:
> > 
> >gdb -ex r --args /usr/bin/python3 -m qutebrowser --temp-basedir 
> > --qt-flag single-process
> 
>   $ sudo gdb -ex r --args /usr/bin/python3 -m qutebrowser --temp-basedir 
> --qt-flag single-process

Please don't run with 'sudo'. This can cause various other issues (since
Chromium's sandboxing doesn't work properly as root) and running a
browser as root is a bad idea in general ;)

> [...]
> 
> 
> Thread 40 "Chrome_InProcRe" received signal SIGILL, Illegal instruction.
> [Switching to Thread 0x7fff58a89700 (LWP 12375)]
> 0x7fffea1b128f in 
> blink::CompositedLayerMapping::ComputeBoundsOfOwningLayer(blink::PaintLayer 
> const*,
> blink::IntRect&, blink::IntRect&, blink::PhysicalOffset&, blink::IntPoint&) 
> () from
> /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
> 
> (gdb) bt
> #0  0x7fffea1b128f in 
> blink::CompositedLayerMapping::ComputeBoundsOfOwningLayer(blink::PaintLayer 
> const*,
> blink::IntRect&, blink::IntRect&, blink::PhysicalOffset&, blink::IntPoint&) 
> () at
> /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
> #1  0x7fffea1bc054 in 
> blink::CompositedLayerMapping::UpdateGraphicsLayerGeometry(blink::PaintLayer 
> const*,
> blink::PaintLayep

Looks like your output/mail was cut off here, so it's difficult to say
what's happening exactly - but from what I can tell so far, this most
like is indeed an issue in QtWebEngine and not qutebrowser.

Can you check if you get the same crashes with another QtWebEngine-based
browser such as falkon?

If so, this report should probably be moved to libqt5webengine5, though
having the full stack traces would still be useful for the maintainers
of that package :)

Thanks,
Florian

-- 
m...@the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org 
   https://bruhin.software/ | https://github.com/sponsors/The-Compiler/
   GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
 I love long mails! | https://email.is-not-s.ms/


signature.asc
Description: PGP signature

Bug#970478: ERROR: Renderer process crashed when using qtwebengine backend.

[Florian Bruhin]

Hey,

On Mon, Sep 21, 2020 at 10:00:50AM -0300, felipe wrote:
> And dmesg shows this line for each time i refresh or try to open any website:
>traps: QtWebEngineProc[4369] trap invalid opcode ip:7f322fa7128f 
> sp:7ffd1d00c600 error:0 in
> libQt5WebEngineCore.so.5.14.2[7f322bd14000+5a63000]

I think I'll need a C++ stacktrace to say more about what's happening.

However, I'm not sure about how things look in Debian exactly:

1) Whether coredumpctl is in use
2) How to get debug symbols for the libqt5webengine5 package

For 1), do you see those QtWebEngineProcess crashes when you run
"coredumpctl list"? If so, can you please show "coredumpctl info PID"
with the PID from the list? If not, can you check whether you can
reproduce them (making the entire browser crash) when you run with
"--qt-flag single-process"?

For 2), it looks like there's no libqt5webengine5-dbg{,sym} package in
the debian archives. Could you check if you find them if you run e.g.
find-dbgsym-packages on /usr/lib/x86_64-linux-gnu/libQt5WebEngine.so.5.14.2
https://wiki.debian.org/HowToGetABacktrace#Installing_the_debugging_symbols

(If there are no debug symbols available at all, I wonder if a bug should
be opened against libqt5webengine5a - Axel/Fritz, if you have an opinion
on that, I'd like to hear more)

If getting more info via coredumpctl didn't work, but you can reproduce
with --qt-flag single-process, can you please do something like:

   gdb -ex r --args /usr/bin/python3 -m qutebrowser --temp-basedir --qt-flag 
single-process

And then use "bt" when you get the (gdb) prompt? Let's hope it says
something useful even without debugging symbols...

Florian

-- 
m...@the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org 
   https://bruhin.software/ | https://github.com/sponsors/The-Compiler/
   GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
 I love long mails! | https://email.is-not-s.ms/


signature.asc
Description: PGP signature

Bug#970478: ERROR: Renderer process crashed when using qtwebengine backend.

[Florian Bruhin]

Hey,

Upstream maintainer here - not sure what's going on exactly, but let's
try to find out :)

On Wed, Sep 16, 2020 at 09:12:19PM -0300, zeden wrote:
> Trying to open sites using qtwebengine backend results in:
> "ERROR: Renderer process crashed". 

I assume you're seeing this on any webpage you open?

If you start qutebrowser in a terminal and with --temp-basedir, does it
happen as well? If so, do you see anything interesting in the output
there?

Florian

-- 
m...@the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org 
   https://bruhin.software/ | https://github.com/sponsors/The-Compiler/
   GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
 I love long mails! | https://email.is-not-s.ms/


signature.asc
Description: PGP signature

Bug#960384: qutebrowser fails to start with critical qt message: Could not initialize GLX

[Florian Bruhin]

Hey,

Upstream here - no idea what's happening there I'm afraid. I'm guessing you'll
have similar issues with other Qt/QtWebEngine applications as well though, I
doubt this is qutebrowser-specific. Can you try with e.g. Falkon as well?

Florian

-- 
m...@the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org 
   https://bruhin.software/ | https://github.com/sponsors/The-Compiler/
   GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
 I love long mails! | https://email.is-not-s.ms/


signature.asc
Description: PGP signature

Bug#943173: Not in testing yet?

[Florian Bruhin]

Hey Dmitry,

On Thu, Feb 06, 2020 at 01:04:35PM +0300, Dmitry Shachnev wrote:
> Hi Florian!
> 
> On Thu, Feb 06, 2020 at 10:36:22AM +0100, Florian Bruhin wrote:
> > Hey,
> >
> > It looks like 5.14.0-2 with the fix isn't in testing yet? See
> > https://tracker.debian.org/pkg/pyqt5webengine
> > https://qa.debian.org/excuses.php?package=pyqt5webengine
> >
> > I don't really understand why - can someone elaborate on what's going on?
> 
> That is because the Python 3 version of calibre failed to build on two
> architectures (arm64, mipsel), so calibre in testing still uses Python 2,
> so some packages which dropped Python 2 support (like pyqt5webengine)
> cannot migrate to testing.

Thanks a lot for the explanation! Out of curiosity, is there a way I could've
found out myself? https://qa.debian.org/excuses.php?package=pyqt5webengine
doesn't seem to say much about this situation.

> I think on February 16th calibre will be auto-removed from testing, and
> after that all those packages will be able to migrate.

FWIW it looks like there has been some activity for calibre:
https://tracker.debian.org/news/1099652/accepted-calibre-4994dfsgreally4100py3-1-source-into-unstable/
https://tracker.debian.org/news/1099754/accepted-calibre-4994dfsgreally4100py3-2-source-into-unstable/

> In the worst case, they will be removed for a short time but then will
> migrate anyway (but now that we have some activity on this bug, I don't think
> that will be the case for pyqt5webengine).

I was a bit worried about the exact timeline when this happens, since 27th is
the feature freeze for Ubuntu 20.04, and I'd really like qutebrowser v1.10.0 be
in there (given that it fixes various issues and will be supported by Ubuntu
for five years).

But indeed, it looks like the autoremoval date shown now is March 7th:
https://tracker.debian.org/pkg/qutebrowser

Florian

-- 
m...@the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org 
   https://bruhin.software/ | https://github.com/sponsors/The-Compiler/
   GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
 I love long mails! | https://email.is-not-s.ms/


signature.asc
Description: PGP signature

Bug#943173: Not in testing yet?

[Florian Bruhin]

Hey,

It looks like 5.14.0-2 with the fix isn't in testing yet? See
https://tracker.debian.org/pkg/pyqt5webengine
https://qa.debian.org/excuses.php?package=pyqt5webengine

I don't really understand why - can someone elaborate on what's going on?

It looks like dependent packages (like qutebrowser, which I'm the upstream of)
are getting mails like this:

Date: Thu, 06 Feb 2020 04:39:10 +
From: Debian testing autoremoval watch 
To: qutebrow...@packages.debian.org
Subject: qutebrowser is marked for autoremoval from testing

qutebrowser 1.9.0-1 is marked for autoremoval from testing on 2020-02-16

It (build-)depends on packages with these RC bugs:
943173: pyqt5webengine: Python2 removal in sid/bullseye

Florian

-- 
m...@the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org 
   https://bruhin.software/ | https://github.com/sponsors/The-Compiler/
   GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
 I love long mails! | https://email.is-not-s.ms/


signature.asc
Description: PGP signature

Bug#948112: python3-pyqt5: Unstable python3-pyqt5 Is Not Installable With libqt5qui5-gles Installed

[Florian Bruhin]

Hey,

On Sun, Jan 05, 2020 at 12:33:41PM +0300, Dmitry Shachnev wrote:
> 2) Disable the PyQt_Desktop_OpenGL feature in the main build. With this
> option the classes like QOpenGLTimerQuery, QOpenGLTimeMonitor,
> QOpenGLFunctions_x_y will be no longer available.
> 
> So far I have not found any packages using these PyQt5 APIs, so maybe
> this option is possible. But I will need to investigate further.

Note that QOpenGLFunctions_x_y is implicitly imported when using
.versionFunctions() on a QOpenGLContext.

qutebrowser uses that in qutebrowser/utils/version.py (in opengl_vendor()).

Florian

-- 
m...@the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org 
   https://bruhin.software/ | https://github.com/sponsors/The-Compiler/
   GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
 I love long mails! | https://email.is-not-s.ms/


signature.asc
Description: PGP signature

Bug#882805: Some investigation

[Florian Bruhin]

On Fri, Nov 22, 2019 at 06:19:17PM -0300, Lisandro Damián Nicanor Pérez Meyer 
wrote:
> Hi Florian!
> 
> El vie., 22 nov. 2019 14:57, Florian Bruhin  escribió:
> 
> > Hey,
> >
> > qutebrowser upstream here - I recently looked into this a bit, and
> > partially
> > found out what's going on.
> >
> > Turns out when supposed to display an error page, "jstProcess is not
> > defined"
> > gets logged instead.
> >
> > When I look at the source of the error page on my Archlinux machine, that
> > JavaScript function is properly defined, like it is upstream here:
> >
> > https://cs.chromium.org/chromium/src/third_party/jstemplate/jstemplate_compiled.js?q=jstemplate_com=package:chromium=0
> >
> > However, on Debian, the related code is simply missing from the error page.
> >
> > I'm guessing this is somehow related to how Debian regenerates that file
> > from
> > sources:
> >
> > https://salsa.debian.org/qt-kde-team/qt/qtwebengine/blob/debian/5.12.5+dfsg-3/debian/rules#L135-141
> >
> > Maybe there's something going wrong there, and the generated file is
> > actually
> > empty or something?
> 
> 
> Can you attach the related files? I'm this way we can compare them and see
> if this is the case.

Those only exist as part of the build process - I assume Archlinux uses the
compiled one shipped by Chromium (which I linked above).

I don't think I've ever built a Debian package from sources (I'm not a Debian
user, except on a server) and QtWebEngine isn't exactly easy to build, so I
won't be able to check how Debian's rebuilt file looks.

Florian

-- 
https://www.qutebrowser.org | m...@the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
 I love long mails! | https://email.is-not-s.ms/


signature.asc
Description: PGP signature

Bug#882805: Some investigation

[Florian Bruhin]

Hey,

qutebrowser upstream here - I recently looked into this a bit, and partially
found out what's going on.

Turns out when supposed to display an error page, "jstProcess is not defined"
gets logged instead.

When I look at the source of the error page on my Archlinux machine, that
JavaScript function is properly defined, like it is upstream here:
https://cs.chromium.org/chromium/src/third_party/jstemplate/jstemplate_compiled.js?q=jstemplate_com=package:chromium=0

However, on Debian, the related code is simply missing from the error page.

I'm guessing this is somehow related to how Debian regenerates that file from
sources:
https://salsa.debian.org/qt-kde-team/qt/qtwebengine/blob/debian/5.12.5+dfsg-3/debian/rules#L135-141

Maybe there's something going wrong there, and the generated file is actually
empty or something?

FWIW, for now I added a workaround for this to qutebrowser,
which will be part of its v1.8.2 release:
https://github.com/qutebrowser/qutebrowser/commit/300b88fcbfe395988591cedcccdb63a199a9d355

Florian

-- 
https://www.qutebrowser.org | m...@the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
 I love long mails! | https://email.is-not-s.ms/


signature.asc
Description: PGP signature

Bug#925194: Changes not in v1.6.1

[Florian Bruhin]

Hi!

Upstream here - I think what's interesting to look at is what changes
remain when applying the patches considered for a 1.6.0-2 as proposed by
Axel.

I attached a diff from what would be 1.6.0-2, to what I released
upstream as 1.6.1. Looking at it in detail, only the following changes
remain (shortened where contents are irrelevant, for readability):

* Updating the upstream changelog. Not really relevant for Debian.

diff --git a/doc/changelog.asciidoc b/doc/changelog.asciidoc
index 46b9a12ab..076fa0032 100644
--- a/doc/changelog.asciidoc
+++ b/doc/changelog.asciidoc
@@ -15,6 +15,26 @@ breaking changes (such as renamed commands) can happen 
in minor releases.
 // `Fixed` for any bug fixes.
 // `Security` to invite users to upgrade in case of vulnerabilities.

+v1.6.1
+--
+
+[...]
+
 v1.6.0
 --

* Updating PyQt versions a requirements file.
  This is only used for macOS/Windows releases I do, thus not really
  relevant for Debian.

diff --git a/misc/requirements/requirements-pyqt.txt 
b/misc/requirements/requirements-pyqt.txt
index 63722a679..5e2880ce2 100644
--- a/misc/requirements/requirements-pyqt.txt
+++ b/misc/requirements/requirements-pyqt.txt
@@ -1,5 +1,5 @@
 # This file is automatically generated by 
scripts/dev/recompile_requirements.py

-PyQt5==5.12
-PyQt5-sip==4.19.14
-PyQtWebEngine==5.12
+PyQt5==5.12.1
+PyQt5-sip==4.19.15
+PyQtWebEngine==5.12.1

* Updating the version number. Makes my life a lot easier because in
  upstream bug reports I clearly see it's in fact v1.6.1, not
  v1.6.0-but-almost-v1.6.1.

diff --git a/qutebrowser/__init__.py b/qutebrowser/__init__.py
index 713575646..43e9d0a86 100644
--- a/qutebrowser/__init__.py
+++ b/qutebrowser/__init__.py
@@ -26,7 +26,7 @@ __copyright__ = "Copyright 2014-2019 Florian Bruhin (The 
Compiler)"
 __license__ = "GPL"
 __maintainer__ = __author__
 __email__ = "m...@qutebrowser.org"
-__version_info__ = (1, 6, 0)
+__version_info__ = (1, 6, 1)
 __version__ = '.'.join(str(e) for e in __version_info__)
 __description__ = "A keyboard-driven, vim-like browser based on PyQt5."

* An assertion being added - however, with Qt 5.11 in buster it doesn't
  run at all, because of the guard above (QWebEngineUrlScheme was added
  in Qt 5.12).

diff --git a/qutebrowser/browser/webengine/webenginequtescheme.py 
b/qutebrowser/browser/webengine/webenginequtescheme.py
index 132005878..f622ee57b 100644
--- a/qutebrowser/browser/webengine/webenginequtescheme.py
+++ b/qutebrowser/browser/webengine/webenginequtescheme.py
@@ -163,6 +163,7 @@ def init():
 classes.
 """
 if QWebEngineUrlScheme is not None:
+assert not QWebEngineUrlScheme.schemeByName(b'qute').name()
 scheme = QWebEngineUrlScheme(b'qute')
 scheme.setFlags(QWebEngineUrlScheme.LocalScheme |
 QWebEngineUrlScheme.LocalAccessAllowed)

* A configuration change for the ESlint JavaScript linter used during
  development - not relevant for Debian:

diff --git a/qutebrowser/javascript/.eslintrc.yaml 
b/qutebrowser/javascript/.eslintrc.yaml
index cb1bb1fcb..f4af6914b 100644
--- a/qutebrowser/javascript/.eslintrc.yaml
+++ b/qutebrowser/javascript/.eslintrc.yaml
@@ -60,3 +60,4 @@ rules:
  max-lines-per-function: "off"
  require-unicode-regexp: "off"
  max-params: "off"
+ prefer-named-capture-group: "off"

* Changes to tests which are not run by Debian (because they need an X
  server and some other dependencies):

diff --git a/tests/helpers/fixtures.py b/tests/helpers/fixtures.py
index f51f221a3..e50220c51 100644
--- a/tests/helpers/fixtures.py
+++ b/tests/helpers/fixtures.py
@@ -415,7 +415,7 @@ def qnam(qapp):


 @pytest.fixture
-def webengineview(qtbot, monkeypatch):
+def webengineview(qtbot, monkeypatch, web_tab_setup):
 """Get a QWebEngineView if QtWebEngine is available."""
 QtWebEngineWidgets = pytest.importorskip('PyQt5.QtWebEngineWidgets')
 monkeypatch.setattr(objects, 'backend', usertypes.Backend.QtWebEngine)
diff --git a/tests/unit/browser/webengine/test_webenginesettings.py 
b/tests/unit/browser/webengine/test_webenginesettings.py
index 7eea8ffa7..5746586e7 100644
--- a/tests/unit/browser/webengine/test_webenginesettings.py
+++ b/tests/unit/browser/webengine/test_webenginesettings.py
@@ -30,7 +30,9 @@ from qutebrowser.misc import objects


 @pytest.fixture(autouse=True)
-def init(qapp, config_stub, cache_tmpdir, data_tmpdir):
+def init(qapp, config_stub, cache_tmpdir, data_tmpdir, monkeypatch):
+monkeypatch.setattr(webenginesettings.webenginequtescheme, '

Bug#908729: qutebrowser: adblock-update produces error "error while setting the maximum protocol version"

[Florian Bruhin]

On Thu, Sep 13, 2018 at 10:35:31AM +0200, Florian Bruhin wrote:
> Like I've told you in IRC already, this is already fixed (it's a bug in
> QtCore), but you didn't seem to try upgrading like I suggested (or your
> mirror is outdated) ;-)

My bad - this was fixed in libqt5core5a 5.11.1+dfsg-8 but that didn't
make it to testing yet:

https://packages.debian.org/search?keywords=libqt5core5a
https://sources.debian.org/src/qtbase-opensource-src/5.11.1+dfsg-8/debian/patches/ssl_max_version.diff/

Either way, not an issue with the qutebrowser package :)

Florian

-- 
https://www.qutebrowser.org | m...@the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
 I love long mails! | https://email.is-not-s.ms/


signature.asc
Description: PGP signature

Bug#908729: qutebrowser: adblock-update produces error "error while setting the maximum protocol version"

[Florian Bruhin]

Like I've told you in IRC already, this is already fixed (it's a bug in
QtCore), but you didn't seem to try upgrading like I suggested (or your
mirror is outdated) ;-)

On Thu, Sep 13, 2018 at 09:51:25AM +0200, ralphe wrote:
> ii  libqt5core5a 5.11.1+dfsg-7

See https://bugs.debian.org/908557

Florian

-- 
https://www.qutebrowser.org | m...@the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
 I love long mails! | https://email.is-not-s.ms/


signature.asc
Description: PGP signature

Bug#882345: Short description continues into long description

[Florian Bruhin]

Upstream here - it'd probably be best to just drop the "and QtWebKit" part, as
that's not really true anymore either way (it can use either QtWebKit and
QtWebEngine, and uses QtWebEngine by default with 1.0.x).

FWIW, what I usually use myself is this:
"A keyboard-driven, vim-like browser based on PyQt5."

Florian

-- 
https://www.qutebrowser.org  | m...@the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072  | https://the-compiler.org/pubkey.asc
 I love long mails!  | https://email.is-not-s.ms/


signature.asc
Description: PGP signature

Bug#862452: Update to newer QtWebKit

[Florian Bruhin]

Hey Dmitry,

On Fri, Jul 07, 2017 at 02:28:25PM +0300, Dmitry Shachnev wrote:
> Control: severity -1 important
> 
> Hi Florian!
> 
> On Fri, Jul 07, 2017 at 12:59:09PM +0200, Florian Bruhin wrote:
> > I'll have to disagree with this being a "wishlist" bug - Security wise,
> > the old QtWebKit is worse than WebKitGTK 2.4, which gets dropped from
> > buster[4] - we're talking about ~3 years of delta from upstream WebKit,
> > including all security fixes in that timespan, which are missing from
> > the current QtWebKit package. Even if Debian doesn't intend to provide
> > security support[5] for QtWebKit, there are various packages depending
> > on it which deal with untrusted input.
> 
> I absolutely agree. Bumping the bug severity to important.
> 
> However as I said, we need to focus on Qt 5.7.1 → 5.9.1 transition now,
> which still has some blockers. After the transition is done, we will be
> able to do some other Qt tasks not directly related to upgrade, i.e.
> updating QtWebKit or building QtBase with GL ES support on AArch64.
> 
> I hope we will do the transition within a couple of weeks, but it depends
> on my time and amount of other tasks.

Sure, I agree keeping Qt up to date is also important - hope everything
goes well with that. Thank you! :)

Florian

-- 
https://www.qutebrowser.org  | m...@the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072  | https://the-compiler.org/pubkey.asc
 I love long mails!  | https://email.is-not-s.ms/


signature.asc
Description: PGP signature

Bug#862452: Update to newer QtWebKit

[Florian Bruhin]

Hi,

FWIW, Fedora also updated their packages[1], and Archlinux had a
qt5-webkit-ng package[2] since January, which recently got merged[3]
back into the main qt5-webkit package.

I'll have to disagree with this being a "wishlist" bug - Security wise,
the old QtWebKit is worse than WebKitGTK 2.4, which gets dropped from
buster[4] - we're talking about ~3 years of delta from upstream WebKit,
including all security fixes in that timespan, which are missing from
the current QtWebKit package. Even if Debian doesn't intend to provide
security support[5] for QtWebKit, there are various packages depending
on it which deal with untrusted input.

There's also a lot of other bugfixes; a lot of websites break or
segfault with the legacy QtWebKit package.

Florian

[1] 
http://lupinix.blogspot.ch/2017/06/improving-qtwebkit-security-for-fedora.html
[2] 
https://lists.archlinux.org/pipermail/arch-dev-public/2017-January/028656.html
[3] https://lists.archlinux.org/pipermail/arch-dev-public/2017-June/028895.html
[4] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866671
[5] 
https://www.debian.org/releases/stretch/amd64/release-notes/ch-information.en.html#browser-security

-- 
https://www.qutebrowser.org  | m...@the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072  | https://the-compiler.org/pubkey.asc
 I love long mails!  | https://email.is-not-s.ms/


signature.asc
Description: PGP signature

Bug#790207: Upstream luakit based on webkit2gtk

[Florian Bruhin]

Note that upstream recently merged a fork with a major update based on
webkit2: https://luakit.github.io/luakit/

-- 
https://www.qutebrowser.org  | m...@the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072  | https://the-compiler.org/pubkey.asc
 I love long mails!  | https://email.is-not-s.ms/

Bug#864941: release-notes: webkit2gtk not mentioned in https://www.debian.org/releases/stretch/amd64/release-notes/ch-information.en.html#browser-security

[Florian Bruhin]

Hi,

On Sat, Jun 17, 2017 at 08:42:16PM +0200, Axel Beckert wrote:
> Hi Julien,
> 
> Julien Cristau wrote:
> > > And obviously, since "qtwebkit" and "webkit" are both mentioned
> > > already, the mentioning of "webkit" does not imply any webkit fork as
> > > otherwise "qtwebkit" wouldn't be in there.
> >
> > OK.  I didn't think that list is intended as a list of source
> > packages.
> 
> Ah, ok, I read it that way as qtwebkit and khtml are current source
> package names.

If it's not a list of source packages, then qtwebkit shouldn't be listed
either, no? After all, that's a WebKit fork as well.

> > It does talk about browser engines instead, I believe on purpose, so it
> > doesn't have to be that specific about source package names (which
> > wouldn't be much help to most users anyway).  Maybe we could make that
> > clearer.
> 
> Yes, please.
> 
> Basically this was a question during my talk "What's new in Stretch?"
> today after having copied this list from the release notes on one of
> my slides.
> 
> The question came from a developer of a webkit-based web browser (Cc'ed).

That'd be me ;-)

> > Or indeed update it to actual current source packages.
> 
> Then webkit should be removed from the list. I just noticed now that
> it's no current source package name anymore. it has been removed from
> unstable in 2013.

As Axel mentioned earlier, I think QtWebEngine should be added as well
as I don't expect Qt to be upgraded during the Stretch release.
That's based on Chromium, which is somewhat related to WebKit, but still
probably distinct enough.

Florian

-- 
https://www.qutebrowser.org  | m...@the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072  | https://the-compiler.org/pubkey.asc
 I love long mails!  | https://email.is-not-s.ms/


signature.asc
Description: PGP signature

Bug#861201: python3: Incoherent "for" behaviour with different iterables

[Florian Bruhin]

On Tue, Apr 25, 2017 at 09:55:01PM +0200, Dominik George wrote:
> Hi,
> 
> > Python should raise a RuntimeError exception with a list as with a set.
> 
> It *does*, for a list.
> 
> But in Python 3, with [], you do not get a list, but an iterator with a 
> list-like API ;). It wraps a list which you add to, but __next__ will yield 
> the next item if there is one.

That's not true:

Python 3.6.1 (default, Mar 27 2017, 00:27:06)
[GCC 6.3.1 20170306] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> list()
[]
>>> type(list())

>>> type([])


If you want an iterator, you need to explicitly ask for it:

>>> iter([])


Calling next() on a list won't work:

>>> next([])
Traceback (most recent call last):
  File "", line 1, in 
TypeError: 'list' object is not an iterator

Florian

-- 
https://www.qutebrowser.org  | m...@the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072  | https://the-compiler.org/pubkey.asc
 I love long mails!  | https://email.is-not-s.ms/


signature.asc
Description: PGP signature

Bug#835991: python3-pyqt5: Slot decorators no longer work

[Florian Bruhin]

* Salvo Tomaselli  [2016-08-29 22:49:55 +0200]:
> Package: python3-pyqt5
> Version: 5.7+dfsg-2
> Severity: important
> 
> Dear Maintainer,
> 
> Slots used to be decorated with things like
> 
> @QtCore.pyqtSlot(object)
> 
> Now having these causes a crash.

Note that's only the case when pyqtSlot is used incorrectly (with the
wrong types, or on something which is not a QObject), which was
silently ignored in earlier versions.

> As a result qweborf is completely unusable now.
> 
> It seems that the last version of pyqt was a major release with
> incompatibilities that perhaps needed a mass bug filling.

That'd indeed be a qweborf bug then. But yeah, when I noticed the
change I already wondered how much will be impacted... my own project
certainly was ;)

Florian

-- 
http://www.the-compiler.org | m...@the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
 I love long mails! | http://email.is-not-s.ms/


signature.asc
Description: PGP signature

Bug#832159: Processed: block 832159 with 832420

[Florian Bruhin]

* Debian Bug Tracking System  [2016-07-25 11:03:05 
+]:
> Processing commands for cont...@bugs.debian.org:
> 
> > block 832159 with 832420

I don't think this should be blocked by QtWebEngine. In fact,
QtWebEngine support is still in heavy development, and most (if not
all) users are using it with QtWebKit.

If this was unclear in Fritz' original mail - qutebrowser works with
either QtWebKit or - in the near future - QtWebEngine.

Florian

-- 
http://www.the-compiler.org | m...@the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
 I love long mails! | http://email.is-not-s.ms/


signature.asc
Description: PGP signature

Bug#832159: upstream

[Florian Bruhin]

Hi,

I'm the upstream maintainer - I worked together with Fritz for this
package, and we both think it's ready at this point. A Debian
developer I know (Axel Beckert, Cc'ed here) also took a look at the
package and would be willing to sponsor it.

> But unlike dwb and other vim-like Browsers it does not rely on
> webkitgtk as the backend but on the newer QtWebKit and QtWebEngine
> (Chromium engine)

Let me point out that WebKit2GTK is probably newer than QtWebKit -
however none of the existing WebKitGTK browsers got ported to WebKit2
so far ;)

I am also aware that QtWebKit is unmaintained upstream - however I
still hope someone will package QtWebEngine for Debian at some point,
and there are also efforts for a maintained QtWebKit successor (with
which qutebrowser already mostly works):

https://github.com/annulen/webkit/wiki

Florian

-- 
http://www.the-compiler.org | m...@the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
 I love long mails! | http://email.is-not-s.ms/


signature.asc
Description: PGP signature

Bug#824611: Nagstamon bug

[Florian Bruhin]

This is actually a bug in Nagstamon, discovered by PyQt getting
stricter about correct @pyqtSlot signatures.

I'm guessing you don't see this with other platforms because you're
running Qt 5.6 but not PyQt 5.6 there, which is where this behaviour
was added:

https://www.riverbankcomputing.com/static/Downloads/PyQt5/ChangeLog
(d58baf1a1473, "Connecting to a decorated method will now fail without
a compatible signature.")

Nagstamon has a slot decorated with @pyqtSlot(str, bool) and connects
it to a str/QString signal:

https://github.com/HenriWahl/Nagstamon/blob/master/Nagstamon/QUI/__init__.py#L3925
https://github.com/HenriWahl/Nagstamon/blob/master/Nagstamon/QUI/__init__.py#L3904-L3905

This was silently ignored in PyQt < 5.6 and is an error with 5.6.

Nagstamon's authors should add a @pyqtSlot(str) decoration to that
slot and also fix other slots with the same issue as necessary.

Florian

-- 
http://www.the-compiler.org | m...@the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
 I love long mails! | http://email.is-not-s.ms/


signature.asc
Description: Digital signature

Bug#686709: Archlinux

[Florian Bruhin]

For what it's worth, I just experienced the same on an Archlinux
machine with Audacity 2.1.2.

-- 
http://www.the-compiler.org | m...@the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
 I love long mails! | http://email.is-not-s.ms/


signature.asc
Description: Digital signature

Bug#805265: libqt5network5: Sporadic segfault on exit in QNetworkConfigurationManagerPrivate::pollEngines()

[Florian Bruhin]

Package: libqt5network5
Version: 5.3.2+dfsg-4+deb8u1
Severity: normal
Tags: upstream patch

Dear Maintainer,

I'm running a (Py)Qt5 application as part of a CI, and once all few days I get
a segfault on exit here:


.../libQt5Network.so.5(QNetworkConfigurationManagerPrivate::pollEngines() 
0xe4)[0x7f262566b9b4]
.../libQt5Network.so.5( 0x10f20d)[0x7f26256db20d]
.../libQt5Core.so.5(QMetaObject::activate(QObject*, int, int, void**) 
0x77d)[0x7f262eb0ffdd]
.../libQt5Core.so.5(QTimer::timerEvent(QTimerEvent*) 
0x28)[0x7f262eb1da58]
.../libQt5Core.so.5(QObject::event(QEvent*) 0xb3)[0x7f262eb10e93]
.../libQt5Widgets.so.5(QApplicationPrivate::notify_helper(QObject*, 
QEvent*) 0x8c)[0x7f262758b12c]
.../libQt5Widgets.so.5(QApplication::notify(QObject*, QEvent*) 
0x3a0)[0x7f2627590600]
.../QtWidgets.cpython-34m-x86_64-linux-gnu.so( 0x15f5b6)[0x7f26267d25b6]
.../libQt5Core.so.5(QCoreApplication::notifyInternal(QObject*, QEvent*) 
0xdb)[0x7f262eae0dcb]
.../libQt5Core.so.5(QTimerInfoList::activateTimers() 
0x595)[0x7f262eb38045]
.../libQt5Core.so.5( 0x3314c1)[0x7f262eb384c1]
.../libglib-2.0.so.0(g_main_context_dispatch 0x24d)[0x7f262daa6c5d]
.../libglib-2.0.so.0( 0x49f48)[0x7f262daa6f48]
.../libglib-2.0.so.0(g_main_context_iteration 0x2c)[0x7f262daa6ffc]

.../libQt5Core.so.5(QEventDispatcherGlib::processEvents(QFlags)
 0x6c)[0x7f262eb391cc]

.../libQt5Core.so.5(QEventLoop::exec(QFlags) 
0x112)[0x7f262eade512]
.../libQt5Core.so.5(QThread::exec() 0xb4)[0x7f262e89ecb4]
.../libQt5Core.so.5( 0x9cd2e)[0x7f262e8a3d2e]
.../libpthread.so.0( 0x80a4)[0x7f2632cec0a4]
.../libc.so.6(clone 0x6d)[0x7f2631ccd04d]

Full catchsegv log:

http://qutebrowser.org:8010/builders/debian-jessie/builds/1214/steps/unittests/logs/stdio

This has been reported and fixed upstream:

https://bugreports.qt.io/browse/QTBUG-44407
https://codereview.qt-project.org/#/c/111893/

And indeed I've not seen this happen since 5.4.2.

I'd be glad if the patch could be backported:

http://code.qt.io/cgit/qt/qtbase.git/patch/?id=3f0f707d4b898a96e63e16c13a29f12be01d9b4c

Thanks,

Florian

-- System Information:
Debian Release: 8.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libqt5network5 depends on:
ii  libc6  2.19-18+deb8u1
ii  libqt5core5a   5.3.2+dfsg-4+deb8u1
ii  libqt5dbus55.3.2+dfsg-4+deb8u1
ii  libstdc++6 4.9.2-10
ii  multiarch-support  2.19-18+deb8u1
ii  zlib1g 1:1.2.8.dfsg-2+b1

libqt5network5 recommends no packages.

libqt5network5 suggests no packages.

-- no debconf information

Bug#804758: libqt5widgets5: Crashes and drawing errors related to SHM

[Florian Bruhin]

Package: libqt5widgets5
Version: 5.3.2+dfsg-4+deb8u1
Severity: normal

Dear Maintainer,

Since a few days, QtWebKit applications (such as Calibre or my minimal
PyQt test script[1]) crash when resizing the window. I think it mostly
happens when it's resized bigger than the window size when the
application was started.

Sometimes there's a segfault, sometimes just a warning printed:

[...]
QXcbShmImage: shmget() failed (28) for size 103376 (364x71)
QXcbShmImage: shmget() failed (28) for size 905664 (636x356)
QXcbShmImage: shmget() failed (28) for size 921600 (640x360)
QXcbShmImage: shmget() failed (28) for size 8294400 (1920x1080)
QXcbShmImage: shmget() failed (28) for size 8294400 (1920x1080)
[...]

I also see drawing errors when using KeePassX (wich doesn't use
QtWebKit) with similar errors:

QNativeImage: Unable to attach to shared memory segment. 
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode: 62 (X_CopyArea)
  Resource id:  0x0
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode: 62 (X_CopyArea)
  Resource id:  0x0

screenshot: http://the-compiler.org/tmp/qt5drawing.png

Everything non-Qt seems to work fine.

[1] 
https://github.com/The-Compiler/qutebrowser/blob/master/scripts/minimal_webkit_testbrowser.py

Florian

-- System Information:
Debian Release: 8.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libqt5widgets5 depends on:
ii  libc6  2.19-18+deb8u1
ii  libglib2.0-0   2.42.1-1
ii  libqt5core5a   5.3.2+dfsg-4+deb8u1
ii  libqt5gui5 5.3.2+dfsg-4+deb8u1
ii  libstdc++6 4.9.2-10
ii  libx11-6   2:1.6.2-3
ii  multiarch-support  2.19-18+deb8u1

libqt5widgets5 recommends no packages.

libqt5widgets5 suggests no packages.

-- no debconf information

Bug#804758: Duplicate

[Florian Bruhin]

I did some more research on this, and I think I'm actually running
into #799587:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799587

Closing the Java application I was running did indeed fix the issue...

So I guess this can be merged into #799587 - sorry for the noise!

Florian

-- 
http://www.the-compiler.org | m...@the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
 I love long mails! | http://email.is-not-s.ms/


signature.asc
Description: Digital signature

Bug#790718: screenshot

[Florian Bruhin]

Attaching a screenshot. It seems some parts of the UI are unaffected,
but the URL completion is (and e.g. the webinspector as well).

-- 
http://www.the-compiler.org | m...@the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
 I love long mails! | http://email.is-not-s.ms/


pgpiG2RfLsdN_.pgp
Description: PGP signature

Bug#790718: chromium: Fonts blurry in Chromium since some update

[Florian Bruhin]

Package: chromium
Version: 43.0.2357.65-1~deb8u1
Severity: normal
Tags: upstream

Dear Maintainer,

Since some update a few weeks (months?) ago, all fonts in my Chromium
appear blurry. I don't think this is the same issue as in #580622
because it doesn't seem to be connected to subpixel rendering.

The upstream bug for this seems to be:
http://code.google.com/p/chromium/issues/detail?id=484400

Screenshots can also be found there - it looks the same on my system.
Note that Chromium's UI is affected as well.

There's an upstream fix but the Debian package doesn't seem to contain
it:

http://code.google.com/p/chromium/issues/detail?id=484400#c52

The mentioned workaround of doing xrandr --dpi 96x96 fixed the issue
for me.

Let me know if there's anything else I can provide - I'm a bit
confused by all the very similar upstream reports.

-- System Information:
Debian Release: 8.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages chromium depends on:
ii  libasound2   1.0.28-1
ii  libatk1.0-0  2.14.0-1
ii  libc62.19-18
ii  libcairo21.14.0-2.1
ii  libcups2 1.7.5-11+deb8u1
ii  libdbus-1-3  1.8.18-0+deb8u1
ii  libexpat12.1.0-6+b3
ii  libfontconfig1   2.11.0-6.3
ii  libfreetype6 2.5.2-3
ii  libgdk-pixbuf2.0-0   2.31.1-2+b1
ii  libglib2.0-0 2.42.1-1
ii  libgnome-keyring03.12.0-1+b1
ii  libgtk2.0-0  2.24.25-3
ii  libharfbuzz0b0.9.35-2
ii  libjpeg62-turbo  1:1.3.1-12
ii  libnspr4 2:4.10.7-1
ii  libnss3  2:3.17.2-1.1
ii  libpango-1.0-0   1.36.8-3
ii  libpangocairo-1.0-0  1.36.8-3
ii  libpci3  1:3.2.1-3
ii  libspeechd2  0.8-7
ii  libspeex11.2~rc1.2-1
ii  libsrtp0 1.4.5~20130609~dfsg-1.1
ii  libstdc++6   4.9.2-10
ii  libx11-6 2:1.6.2-3
ii  libxcomposite1   1:0.4.4-1
ii  libxcursor1  1:1.1.14-1+b1
ii  libxdamage1  1:1.1.4-2+b1
ii  libxext6 2:1.3.3-1
ii  libxfixes3   1:5.0.1-2+b2
ii  libxi6   2:1.7.4-1+b2
ii  libxml2  2.9.1+dfsg1-5
ii  libxrandr2   2:1.4.2-1+b1
ii  libxrender1  1:0.9.8-1+b1
ii  libxslt1.1   1.1.28-2+b2
ii  libxss1  1:1.2.2-1
ii  libxtst6 2:1.2.2-1+b1
ii  x11-utils7.7+2
ii  xdg-utils1.1.0~rc1+git20111210-7.4

chromium recommends no packages.

Versions of packages chromium suggests:
pn  chromium-inspector  none
pn  chromium-l10n   none

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#786567: python-distlib-whl=0.2.0-2 breaks pip

[Florian Bruhin]

This seems to be a duplicate of #785787 which was fixed with
python-pip 1.5.6-6.

-- 
http://www.the-compiler.org | m...@the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
 I love long mails! | http://email.is-not-s.ms/


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#752088: pnp4nagios-web: Error message Non-static method nagios_Core::SummaryLink()

[Florian Bruhin]

Package: pnp4nagios-web
Version: 0.6.16-2
Followup-For: Bug #752088

I see the same happening after updating from Wheezy to Jessie. I can
confirm the mentioned workaround of adding ~E_DEPRECATED to index.php
works (thus the debsum error below).

I think the severity of this bug report should be raised to important
(has a major effect on the usability of a package, without rendering
it completely unusable to everyone) or grave (makes the package in
question unusable or mostly so).

-- System Information:
Debian Release: 8.0
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-042stab104.1 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages pnp4nagios-web depends on:
ii  adduser3.113+nmu3
ii  debconf [debconf-2.0]  1.5.56
ii  libapache2-mod-php55.6.7+dfsg-1
ii  libfpdi-php1.4.1-1
ii  libjs-jquery   1.7.2+dfsg-3.2
ii  libjs-jquery-ui1.10.1+dfsg-1
ii  libkohana2-php 2.3.4-2
ii  php5   5.6.7+dfsg-1
ii  php5-gd5.6.7+dfsg-1
ii  rrdtool1.4.8-1.2

Versions of packages pnp4nagios-web recommends:
ii  pnp4nagios-bin  0.6.16-2

Versions of packages pnp4nagios-web suggests:
pn  rrdcached  none

-- Configuration Files:
/etc/pnp4nagios/apache.conf changed:
Alias /pnp4nagios /usr/share/pnp4nagios/html
Directory /usr/share/pnp4nagios/html
AllowOverride None
Order allow,deny
Allow from all
#
# Use the same value as defined in nagios.conf
#
AuthName Nagios Access
AuthType Basic
AuthUserFile /etc/icinga/htpasswd.users
Require valid-user
IfModule mod_rewrite.c
# Turn on URL rewriting
RewriteEngine On
Options FollowSymLinks
# Installation directory
RewriteBase /pnp4nagios/
# Protect application and system files from being viewed
RewriteRule ^(application|modules|system) - [F,L]
# Allow any files or directories that exist to be displayed 
directly
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
# Rewrite all other URLs to index.php/URL
RewriteRule .* index.php/$0 [PT,L]
/IfModule
/Directory

/etc/pnp4nagios/config.php changed:
?php
$conf['use_url_rewriting'] = 1;
$conf['rrdtool'] = /usr/bin/rrdtool;
$conf['graph_width'] = 500;
$conf['graph_height'] = 200;
$conf['zgraph_width'] = 500;
$conf['zgraph_height'] = 200;
$conf['right_zoom_offset'] = 30;
$conf['pdf_width']= 675;
$conf['pdf_height']   = 100;
$conf['pdf_page_size']= A4;   # A4 or Letter
$conf['pdf_margin_top']   = 30;
$conf['pdf_margin_left']  = 17.5;
$conf['pdf_margin_right'] = 10;
$conf['graph_opt'] = ; 
$conf['pdf_graph_opt'] = ; 
$conf['rrdbase'] = /var/lib/pnp4nagios/perfdata/;
$conf['page_dir'] = /etc/pnp4nagios/pages/;
$conf['refresh'] = 90;
$conf['max_age'] = 60*60*6;   
$conf['temp'] = /var/tmp;
$conf['nagios_base'] = /cgi-bin/icinga;
$conf['multisite_base_url'] = /check_mk;
$conf['multisite_site'] = ;
$conf['auth_enabled'] = FALSE;
$conf['livestatus_socket'] = unix:/usr/local/nagios/var/rw/live;
$conf['allowed_for_all_services'] = ;
$conf['allowed_for_all_hosts'] = ;
$conf['allowed_for_service_links'] = EVERYONE;
$conf['allowed_for_host_search'] = EVERYONE;
$conf['allowed_for_host_overview'] = EVERYONE;
$conf['allowed_for_pages'] = EVERYONE;
$conf['overview-range'] = 1 ;
$conf['popup-width'] = 500px;
$conf['ui-theme'] = 'smoothness';
$conf['lang'] = en_US;
$conf['date_fmt'] = d.m.y G:i;
$conf['enable_recursive_template_search'] = 1;
$conf['show_xml_icon'] = 1;
$conf['use_fpdf'] = 1;  
$conf['background_pdf'] = '/etc/pnp4nagios/background.pdf' ;
$conf['use_calendar'] = 1;
$views[] = array('title' = '4 Hours',   'start' = (60*60*4) );
$views[] = array('title' = '25 Hours',  'start' = (60*60*25) );
$views[] = array('title' = 'One Week',  'start' = (60*60*25*7) );
$views[] = array('title' = 'One Month', 'start' = (60*60*24*32) );
$views[] = array('title' = 'One Year',  'start' = (60*60*24*380) );
$conf['RRD_DAEMON_OPTS'] = '';
$conf['template_dirs'][] = '/etc/pnp4nagios/templates';
$templates_d = glob(/etc/pnp4nagios/templates.d/*, GLOB_ONLYDIR);
if (is_array($templates_d)  (count($templates_d)  0)) {
foreach ($templates_d as $dirname) {
$conf['template_dirs'][] = $dirname;
}
}
$conf['template_dirs'][] = '/usr/share/pnp4nagios/html/templates.dist';
$conf['special_template_dir'] = '/etc/pnp4nagios/templates.special';
$conf['mobile_devices'] = 'iPhone|iPod|iPad|android';
?


-- no debconf information

-- debsums errors found:
debsums: changed file 

Bug#780748: Change merged upstream

[Florian Bruhin]

Any update on this? The change has now been merged upstream:
http://code.qt.io/cgit/qt/qtwebkit.git/commit/?h=5.4id=2810aea1f6c9cca48b93130a7c245f9a2f85637e

Florian

-- 
http://www.the-compiler.org | m...@the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
 I love long mails! | http://email.is-not-s.ms/


pgpofOjy8LjfH.pgp
Description: PGP signature

Bug#780748: libqt5webkit5: QtWebKit logs visited URLs to WebpageIcons.db in private browsing mode

[Florian Bruhin]

Package: libqt5webkit5
Version: 5.3.2+dfsg-3
Severity: important
Tags: upstream patch security

Dear Maintainer,

I've just submitted a change[1] to QtWebKit upstream to prevent it recording
visited URLs to its favicon database (WebpageIcons.db) while using private
browsing mode.

The change has been accepted in upstream's Gerrit and is currently integrating
in their CI.

Raw patch: [2]

I think this should be backported as it's a privacy issue.

Thanks,

Florian

[1] https://codereview.qt-project.org/#/c/108936/
[2] 
http://code.qt.io/cgit/qt/qtwebkit.git/patch/?id=101feb8867ba85b1615656669bbb3ecf8574aaab


-- System Information:
Debian Release: 8.0
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libqt5webkit5 depends on:
ii  dpkg  1.17.24
ii  libc6 2.19-15
ii  libgl1-mesa-glx [libgl1]  10.3.2-1
ii  libglib2.0-0  2.42.1-1
ii  libgstreamer-plugins-base0.10-0   0.10.36-2
ii  libgstreamer0.10-00.10.36-1.5
ii  libicu52  52.1-7.1
ii  libjpeg62-turbo   1:1.3.1-11+deb7u1
ii  libpng12-01.2.50-2+b2
ii  libqt5core5a [qtbase-abi-5-3-2]   5.3.2+dfsg-4+b1
ii  libqt5gui55.3.2+dfsg-4+b1
ii  libqt5network55.3.2+dfsg-4+b1
ii  libqt5opengl5 5.3.2+dfsg-4+b1
ii  libqt5printsupport5   5.3.2+dfsg-4+b1
ii  libqt5qml5 [qtdeclarative-abi-5-3-2]  5.3.2-4
ii  libqt5quick5  5.3.2-4
ii  libqt5sql55.3.2+dfsg-4+b1
ii  libqt5widgets55.3.2+dfsg-4+b1
ii  libsqlite3-0  3.8.7.1-1
ii  libstdc++64.9.2-10
ii  libwebp5  0.4.1-1.2+b2
ii  libx11-6  2:1.6.2-3
ii  libxcomposite11:0.4.4-1
ii  libxml2   2.9.1+dfsg1-5
ii  libxrender1   1:0.9.8-1+b1
ii  libxslt1.11.1.28-2+b2
ii  multiarch-support 2.19-15
ii  zlib1g1:1.2.8.dfsg-2+b1

libqt5webkit5 recommends no packages.

libqt5webkit5 suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#780748: Invalid URL

[Florian Bruhin]

Hi,

I just had to update the upstream fix as I accidentally made a mistake
which means it didn't compile.

Please ignore the raw patch link above, and instead use the
codereview link[1] which links to the newest version.

Sorry for the inconveniences!

[1] https://codereview.qt-project.org/#/c/108936/

-- 
http://www.the-compiler.org | m...@the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
 I love long mails! | http://email.is-not-s.ms/


pgp54mR4x1OY3.pgp
Description: PGP signature