Re: firefox does not start after update to Tumbleweed 20220410
On Wednesday 20 April 2022, Berthold Höllmann wrote:
Michael Hamilton <michael@actrix.gen.nz> writes:
On Wednesday 13 April 2022, Werner LEMBERG wrote:
it crashes only with some specific fonts e.g. Noto Sans, Open Sans, ... Font DeJaVu Sans works
Maybe
https://gitlab.freedesktop.org/freetype/freetype/-/merge_requests/158
helps. Still waiting for confirmation before applying to FreeType's git...
A temporary alternative would be to build FreeType without SVG support.
Werner
This can't be happening to everyone (firefox crashing) or there would be more complaints. So why is it happening to some of us? Are we missing or using fonts or libraries others are not?
The only clue I have is both firefox and pycharm opened /usr/share/fonts/truetype/SourceCodePro-Regular.otf and fell over right afterward.
If a fix is not imminent, is there are there libraries or fonts I can remove to work around the problem. I've currently moved /etc/fonts to /etc/fonts.disabled (but that causes issues with some PDF documents when viewed in okular).
I uninstalled both packages containing the SourceCodePro font from my system (texlive-sourcecodepro-fonts, adobe-sourcecodepro-fonts) and the problem seems to be gone for now.
I really would prefer reinstalling the packages after an upstream bugfix solves the problem.
Berthold
Thanks Berthold, that's the hint I needed to fix my own desktop. Rather uninstall the font package, I've added the following rejectFont to fontconfig in /etc/fonts/local.conf <selectfont> <rejectfont> <pattern> <patelt name="family" > <string>Source Code Pro</string> </patelt> </pattern> </rejectfont> </selectfont> The family string was retrieved using fc-scan: % fc-scan /usr/share/fonts/truetype/SourceCodePro-Regular.otf --format='%{family}\n' The above was all based on the docs at: https://wiki.archlinux.org/title/font_configuration That's solved the problem until the actual fix gets released. Michael
Il 20/04/22 07:41, Michael Hamilton ha scritto:
That's solved the problem until the actual fix gets released.
AFAICS from the package changelogs from the usual snapshot release mail, today's snapshot includes the fix. -- Luca Beltrame GPG key ID: A29D259B
participants (2)
-
Luca Beltrame
-
Michael Hamilton