Package: libqt5webengine5 Version: 5.9.2+dfsg-2 Severity: normal Control: affects -1 qutebrowser
Hi, while testing the qutebrowser 1.0.3 upstream release for sponsoring an upload to Debian I noticed that neither "host not found errors" nor (suspectedly) unsupported protocol errors show up properly in qutebrowser. Thanks to the main qutebrowser upstream developer (Florian Bruhin, X-Debbugs-CC'ed) I am able to provide the following minimal and qutebrowser-independent test cases to reproduce these issues. For that minimal test case Florian suggested to use this minimal command-line wrapper script around Qt's browser engines (part of the qutebrowser source code, but it's not qutebrowser): https://github.com/qutebrowser/qutebrowser/blob/master/scripts/testbrowser.py Using this small test script, I can reproduce the issue as follows: $ python3 testbrowser.py --webengine http://domain.doesnotexist/ Loading progress: 10% Loading started Loading progress: 10% Loading progress: 70% Loading progress: 0% js: Uncaught ReferenceError: jstProcess is not defined Loading finished Loading progress: 100% Loading progress: 100% It shows some half-baked not-sure-what dialog (looks more like half of a download dialog) as shown in the attached 2017-11-26-231109_638x430_scrot.png screen shot.
The console output for trying to access a gopher page looks very similar, but the shown page is completely blank: $ python3 testbrowser.py --webengine gopher://gopher.semmel.ch/ Loading progress: 10% Loading started Loading progress: 0% js: Uncaught ReferenceError: jstProcess is not defined Loading finished Loading progress: 100% Loading progress: 100% Screenshot of the blank page is in 2017-11-26-231406_638x430_scrot.png.
And just as a proof that this gopher server indeed works, 2017-11-26-231803_638x430_scrot.png is a screenshot of accessing that gopher server with the gopher browser forg.
Since the messages, and even the warning testbrowser.py prints, are in both cases nearly identical, I assume this is one bug and not two different bugs. Feel free to clone this bug report if you think otherwise. And since the string "jstProcess" is neither present in qutebrowser's source code nor in testbrowser.py, but according to https://codesearch.debian.net/search?q=jstProcess in qtwebengine-opensource-src and chromium-browser, this seems to be a bug directly in libqt5webengine5 (and not qutebrowser). And since it only seems to happen on Debian (but not on other distributions according to qutebrowser upstream), it might be an issue specific to how qtwebengine is compiled for Debian. (This is not meant as an accusation but as a hint to where start looking. :-) -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'), (500, 'buildd-unstable'), (110, 'experimental'), (1, 'experimental-debug'), (1, 'buildd-experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.13.0-rc7-amd64 (SMP w/8 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages libqt5webengine5 depends on: ii libc6 2.25-2 ii libqt5core5a [qtbase-abi-5-9-2] 5.9.2+dfsg-4 ii libqt5gui5 5.9.2+dfsg-4 ii libqt5qml5 [qtdeclarative-abi-5-9-2] 5.9.2-3 ii libqt5quick5 5.9.2-3 ii libqt5webchannel5 5.9.2-2 ii libqt5webengine-data 5.9.2+dfsg-2 ii libqt5webenginecore5 5.9.2+dfsg-2 ii libstdc++6 7.2.0-16 libqt5webengine5 recommends no packages. libqt5webengine5 suggests no packages. -- no debconf information
