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 <me@the-compiler.org> 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&sq=package:chromium&g=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 | me@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/
Attachment:
signature.asc
Description: PGP signature