Instant hang when accessing ttc-iosevka
Description:
Today's pacman -Syu updated extra/freetype2 from 2.13.3-3 to 2.14.0-1. After rebooting the system, my wayland compositor niri would not start anymore. It just draw the background image and got stuck. I've tried with sway, too, which also got stuck where I could still see the linux console where I issued the sway command.
On #archlinux@libera.chat on IRC, other people mentioned similar problems. The actual culprit might indeed be that the new freetype2 version has some issue with the ttc-iosevka fonts which is quite popular and used by many (including myself) in their wayland compositor setups (like the font used by waybar).
I haven't had the time to debug any further but just downgraded freetype2 to 2.13.3-3 again on both on my systems (I've had the issue on both) to get in a state where I can start my day-job.
Additional info:
extra/freetype2 2.14.0-1
- package version(s):
- config and/or log files:
- link to upstream bug report, if any:
Steps to reproduce:
- Update to extra/freetype2 from 2.14.0-1
- Start sway or niri-session from a linux console (I've configured sway to use the Iosevka font and niri auto-starts waybar using the Iosevka font in my config)