Open danielmussell opened 1 week ago
swaylock doesn't directly interact with fontconfig - that's all handled inside cairo, and the lock for the cache is entirely internal to fontconfig, released by fontconfig's own cache functions on return.
The possible ways this could happen:
info threads
.I see at least one path where fontconfig fails to unlock the cache lock: If allocation fails in FcCacheInsert. But that wouldn't normally happen.
While I have no idea if that's your issue, MR for the missing cache unlock: https://gitlab.freedesktop.org/fontconfig/fontconfig/-/merge_requests/341/diffs
swaylock 1.8.0/fontconfig 2.15.0 on Fedora 41.
I have this intermittent issue where after entering my password, swaylock hangs and cannot unlock the session. When this happens, I need to switch to another VT and kill the session, which is inconvenient to say the least. A backtrace from gdb gives
No other software using cairo/fontconfig is affected, just swaylock, which is why I'm reporting it here. fontconfig#318 is likely related.