xwordgrinder SIGABRT on Fedora

[funnelfiasco]

I haven't had a chance to set up an F42 (currently in Beta) machine to reproduce this, but I have a report of SIGABRT when launching xwordgrinder:

Version-Release number of selected component:
wordgrinder-x11-0.8-11.fc42

Additional info:
reporter:       libreport-2.17.15
type:           CCpp
reason:         xwordgrinder killed by SIGABRT
journald_cursor: s=85d7d4edc4194ffb8e2b91bc71cda67e;i=71cb8;b=30d8788a40f64c0ea8eaaf5f650440e0;m=10e719b32;t=631f3b5ff5672;x=944b813f8e0c26df
executable:     /usr/bin/xwordgrinder
cmdline:        /usr/bin/xwordgrinder
cgroup:         0::/user.slice/user-1000.slice/[user@1000.service](mailto:user@1000.service)/app.slice/[app-wordgrinder@69d3ec2eea5b441abb3687d1c7813abf.service](mailto:app-wordgrinder@69d3ec2eea5b441abb3687d1c7813abf.service)
rootdir:        /
uid:            1000
kernel:         6.14.0-63.fc42.x86_64
package:        wordgrinder-x11-0.8-11.fc42
runlevel:       N 5
backtrace_rating: 4
crash_function: sprintf
comment:        Launching wordgrinder-x11 (xwordgrinder), the application would crash on startup.

Truncated backtrace:
Thread no. 1 (13 frames)
 #9 sprintf at /usr/include/bits/stdio2.h:30
 #10 load_fonts at src/c/arch/unix/x11/glyphcache.c:74
 #11 glyphcache_init at src/c/arch/unix/x11/glyphcache.c:91
 #12 dpy_start at src/c/arch/unix/x11/x11.c:131
 #13 initscreen_cb at src/c/screen.c:25
 #14 luaD_precall at src/c/emu/lua-5.1.5/ldo.c:320
 #15 luaV_execute at src/c/emu/lua-5.1.5/lvm.c:591
 #16 luaD_call at src/c/emu/lua-5.1.5/ldo.c:378
 #17 luaD_rawrunprotected at src/c/emu/lua-5.1.5/ldo.c:116
 #18 luaD_pcall.constprop.0 at src/c/emu/lua-5.1.5/ldo.c:464
 #19 lua_pcall at src/c/emu/lua-5.1.5/lapi.c:821
 #20 docall at src/c/lua.c:59
 #21 script_run at src/c/lua.c:150

[davidgiven]

Mm, that's not good. From the stack trace my guess is that it was configured to use a particular font, and now that font isn't available, and this isn't being handled properly?

That code has now been replaced with something entirely different for 0.9, and I can't duplicate it there. 0.9 is 'out' but I haven't announced it yet because there's maybe two minor things which need fixing.

[funnelfiasco]

I can start building 0.9 in a Copr repo for the time being. That way if you can't resolve the bug in 0.8, the reporter might be able to use 0.9 (assuming the minor things that need fixing aren't blockers for them). Is there a particular commit to target, or should I treat HEAD as 0.9 for this purpose?

[davidgiven]

It's not tagged yet, so go for HEAD.