As mentioned in the gnome bug report, I suspect one particular font.
Launching gnome-shell with that environment variable is going to be tricky, 
I'll see what I can do.
I've tried the demo programs, no luck reproducing the issue so far. 

On 22 April 2019 21:06:53 BST, Werner LEMBERG <[email protected]> wrote:
>
>> So, unfortunately I have not been able to build cairo with debug
>> symbols, but with freetype, this is the result (see attachments).
>> There are 3 attachements because being stopped in a loop, the bt
>> depends on where it's interrupted, so I've included 3 samples in
>> case it helps.
>
>Thanks.  Alas, it doesn't help much, since I don't see the name of the
>font that gets used.
>
>Please compile and install a special version of the FreeType library
>with debugging symbols enabled (see file
>`include/freetype/config/ftoption.h')
>
>  #define FT_DEBUG_LEVEL_ERROR
>  #define FT_DEBUG_LEVEL_TRACE
>
>After doing this, rerun your program from the console with something
>like
>
>  FT2_DEBUG=any:7 your_program &> freetype.log
>
>Expect *huge* output.  Please send this file (heavily compressed) – in
>case it's too large please send it to me privately.
>
>>> Try the programs from the `ft2demos' [...]
>> 
>> I'll try this out when I get some time and if the backtraces are not
>> sufficient.
>
>Try this out :-)
>
>
>    Werner

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
_______________________________________________
Freetype mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/freetype

Reply via email to