#1108668 after a short while, all texts disappear, needs restart

Package:
dia
Source:
dia
Description:
Diagram editor
Submitter:
Toni Mueller
Date:
2025-07-20 20:49:02 UTC
Severity:
normal
Tags:
#1108668#5
Date:
2025-07-02 15:27:08 UTC
From:
To:
Hi,

after a short while of usage, like 5-10 minutes, all texts disappear
from both the canvas and all menus, tooltips etc. Instead, I can only
see a number of empty boxes. At this point, I need to save and restart
dia, then everything will come back. On the console, I get a lot of
error messages related to Pango, Cairo and libfreetype. Here are a few
of these error messages:


(dia:3196422): DiaCairo-WARNING **: 16:14:46.537: ../lib/renderer/diacairo-renderer.c:539, error occurred in libfreetype
(dia:3196422): DiaCairo-WARNING **: 16:14:46.537: ../lib/renderer/diacairo-renderer.c:408, error occurred in libfreetype
(dia:3196422): DiaCairo-WARNING **: 16:14:46.537: ../lib/renderer/diacairo-renderer.c:513, error occurred in libfreetype
(dia:3196422): DiaCairo-WARNING **: 16:14:46.537: ../lib/renderer/diacairo-renderer.c:460, error occurred in libfreetype
(dia:3196422): DiaCairo-WARNING **: 16:14:46.537: ../lib/renderer/diacairo-renderer.c:729, error occurred in libfreetype
(dia:3196422): DiaCairo-WARNING **: 16:14:46.537: ../lib/renderer/diacairo-renderer.c:729, error occurred in libfreetype
(dia:3196422): DiaCairo-WARNING **: 16:14:46.537: ../lib/renderer/diacairo-renderer.c:1067, error occurred in libfreetype
(dia:3196422): DiaCairo-WARNING **: 16:14:46.537: ../lib/renderer/diacairo-renderer.c:408, error occurred in libfreetype
(dia:3196422): Pango-WARNING **: 16:14:51.924: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans 221179.6875'
(dia:3196422): Pango-WARNING **: 16:14:51.924: font_face status is: error occurred in libfreetype
(dia:3196422): Pango-WARNING **: 16:14:51.924: scaled_font status is: error occurred in libfreetype
(dia:3196422): Pango-WARNING **: 16:15:01.946: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans 185989.2041015625'
(dia:3196422): Pango-WARNING **: 16:15:01.946: font_face status is: error occurred in libfreetype
(dia:3196422): Pango-WARNING **: 16:15:01.946: scaled_font status is: error occurred in libfreetype
(dia:3196422): Pango-WARNING **: 16:15:02.039: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans 156397.6025390625'
(dia:3196422): Pango-WARNING **: 16:15:02.039: font_face status is: error occurred in libfreetype
(dia:3196422): Pango-WARNING **: 16:15:02.039: scaled_font status is: error occurred in libfreetype
(dia:3196422): Pango-WARNING **: 16:15:02.117: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans 131514.177734375'
(dia:3196422): Pango-WARNING **: 16:15:02.117: font_face status is: error occurred in libfreetype
(dia:3196422): Pango-WARNING **: 16:15:02.117: scaled_font status is: error occurred in libfreetype
(dia:3196422): Pango-WARNING **: 16:15:02.440: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans 110589.7939453125'
(dia:3196422): Pango-WARNING **: 16:15:02.440: font_face status is: error occurred in libfreetype
(dia:3196422): Pango-WARNING **: 16:15:02.440: scaled_font status is: error occurred in libfreetype
(dia:3196422): Pango-WARNING **: 16:15:02.479: failed to create cairo scaled font, expect ugly output. the offending font is 'Noto Sans 92994.5439453125'
(dia:3196422): Pango-WARNING **: 16:15:02.479: font_face status is: error occurred in libfreetype


I'm trying to use the software outside of Gnome, just with awesomewm.


Kind regards,
Toni

#1108668#10
Date:
2025-07-20 20:47:42 UTC
From:
To:
Hello,

Le 02/07/2025 à 17:27, Toni Mueller a écrit :
same bug than #1020531, which is fixed in testing/unstable, and thus
will be available in the next Debian release, trixie, planned for August
9th.

I just setup a fresh Debian testing VM with awesome window manager and
failed to reproduce the bug, which was a bit expected since the bug
should be fixed in testing.


Also, I don't understand why this bug is tagged ftbfs: it doesn't
mention a build failure.


Philippe.