Bug 1737810 Comment 29 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
So this seems to be happening for various fonts; skimming through the reports, I see at least these:

/usr/share/fonts/truetype/fonts-japanese-gothic.ttf
/usr/share/fonts/truetype/takao-gothic/TakaoGothic.ttf
/usr/share/fonts/opentype/noto/NotoSansCJK-Regular.ttc
/usr/share/fonts/opentype/noto/NotoSansCJK-Bold.ttc
Revision 1 by
on 
So this seems to be happening for various fonts; skimming through the reports, I see at least these:

/usr/share/fonts/truetype/fonts-japanese-gothic.ttf
/usr/share/fonts/truetype/takao-gothic/TakaoGothic.ttf
/usr/share/fonts/opentype/noto/NotoSansCJK-Regular.ttc
/usr/share/fonts/opentype/noto/NotoSansCJK-Bold.ttc
/usr/share/fonts/truetype/ubuntu/Ubuntu-R.ttf
Revision 2 by
on 
So this seems to be happening for various fonts; skimming through the reports, I see at least these:

/usr/share/fonts/truetype/fonts-japanese-gothic.ttf
/usr/share/fonts/truetype/takao-gothic/TakaoGothic.ttf
/usr/share/fonts/opentype/noto/NotoSansCJK-Regular.ttc
/usr/share/fonts/opentype/noto/NotoSansCJK-Bold.ttc
/usr/share/fonts/truetype/ubuntu/Ubuntu-R.ttf

It's hard to imagine that there's really something wrong with all these fonts (which are commonly-used fonts that normally work fine). Is it possible that the snap environment somehow intercepts file accesses as part of its sandboxing/security, and is doing something unreliable such that sometimes when freetype tries to read the file, it gets broken data?
Revision 3 by
on 
So this seems to be happening for various fonts; skimming through the reports, I see at least these:

/usr/share/fonts/truetype/fonts-japanese-gothic.ttf
/usr/share/fonts/truetype/takao-gothic/TakaoGothic.ttf
/usr/share/fonts/opentype/noto/NotoSansCJK-Regular.ttc
/usr/share/fonts/opentype/noto/NotoSansCJK-Bold.ttc
/usr/share/fonts/truetype/ubuntu/Ubuntu-R.ttf
/usr/share/fonts/truetype/croscore/Cousine-Regular.ttf

It's hard to imagine that there's really something wrong with all these fonts (which are commonly-used fonts that normally work fine). Is it possible that the snap environment somehow intercepts file accesses as part of its sandboxing/security, and is doing something unreliable such that sometimes when freetype tries to read the file, it gets broken data?

Back to Bug 1737810 Comment 29