'Re: [PyQt] support for upgraded qtwebkit initiative?'

[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pykde
Subject:    Re: [PyQt] support for upgraded qtwebkit initiative?
From:       Dan Hopkins <dan.hopkins () hanzoarchives ! com>
Date:       2017-01-31 19:14:51
Message-ID: 6a892c95-0bf5-f9d9-0b32-0d007f0d45ab () hanzoarchives ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]

On 31/01/17 16:31, Florian Bruhin wrote:
> Yes - I'm now using the qtwebkit-ng package on Archlinux which
> replaces the normal one.
>
>> My compilations from source for
>> PyQt-5.7.1/sip-4.19/Qt-5.7.1/QtWebKit[stable] on Ubuntu 14.04 segfault
>> consistently in libQt5WebKit.so
> Do you have a stacktrace?

Turns out I was being an idiot - supplying a font path that doesn't 
include the final /truetype/ suffix results in a coredump, not the 
friendliest failure mode, but I should have noticed.

Interestingly (maybe?), 'though the Qt5 configure detected FontConfig 
support, apps still fail to run without being supplied an explicit 
QT_QPA_FONTDIR pointing at system fonts. I assumed FontConfig would 
handle that transparently. It's one of a couple of reasons I'm curious 
to see other successful configure and cmake option sets (the other being 
odd OpenGL inconsistent detection) ... but this is all off PyQt topic.

Dan

[Attachment #5 (text/html)]

<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    On 31/01/17 16:31, Florian Bruhin wrote:
    <blockquote cite="mid:20170131163139.4caakkclr4w3shua@tonks"
      type="cite">
      <pre wrap="">Yes - I'm now using the qtwebkit-ng package on Archlinux which
replaces the normal one.

</pre>
      <blockquote type="cite">
        <pre wrap="">My compilations from source for
PyQt-5.7.1/sip-4.19/Qt-5.7.1/QtWebKit[stable] on Ubuntu 14.04 segfault
consistently in libQt5WebKit.so
</pre>
      </blockquote>
      <pre wrap="">
Do you have a stacktrace?
</pre>
    </blockquote>
    <br>
    Turns out I was being an idiot - supplying a font path that doesn't
    include the final <i>truetype</i> suffix results in a coredump, not
    the friendliest failure mode, but I should have noticed.<br>
    <br>
    Interestingly (maybe?), 'though the Qt5 configure detected
    FontConfig support, apps still fail to run without being supplied an
    explicit QT_QPA_FONTDIR pointing at system fonts. I assumed
    FontConfig would handle that transparently. It's one of a couple of
    reasons I'm curious to see other successful configure and cmake
    option sets (the other being odd OpenGL inconsistent detection) ...
    but this is all off PyQt topic.<br>
    <br>
    Dan<br>
  </body>
</html>

[Attachment #6 (text/plain)]

_______________________________________________
PyQt mailing list    PyQt@riverbankcomputing.com
https://www.riverbankcomputing.com/mailman/listinfo/pyqt

[prev in list] [next in list] [prev in thread] [next in thread] 