Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: Launching wordgrinder-x11 (xwordgrinder), the application would crash on startup. 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/app.slice/app-wordgrinder 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
Created attachment 2083402 [details] File: proc_pid_status
Created attachment 2083403 [details] File: maps
Created attachment 2083404 [details] File: limits
Created attachment 2083405 [details] File: environ
Created attachment 2083406 [details] File: open_fds
Created attachment 2083407 [details] File: mountinfo
Created attachment 2083408 [details] File: os_info
Created attachment 2083409 [details] File: cpuinfo
Created attachment 2083410 [details] File: core_backtrace
Created attachment 2083411 [details] File: dso_list
Created attachment 2083412 [details] File: var_log_messages
Created attachment 2083413 [details] File: backtrace
Launching xwordgrinder crashes it immediately. reporter: libreport-2.17.15 type: CCpp reason: xwordgrinder killed by SIGABRT journald_cursor: s=85d7d4edc4194ffb8e2b91bc71cda67e;i=71ce9;b=30d8788a40f64c0ea8eaaf5f650440e0;m=11f56884c;t=631f3c6e4438b;x=413f254e2512a5b4 executable: /usr/bin/xwordgrinder cmdline: /usr/bin/xwordgrinder cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-wordgrinder 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 xwordgrinder crashes it immediately.
Thanks for reporting this! I haven't had a chance to set up an F42 box to dig into this, but I went ahead and filed a bug with upstream: https://github.com/davidgiven/wordgrinder/issues/297
Hello, I'm upstream. This shouldn't happen. Could you attach your `$HOME/.wordgrinder/settings.dat`, please?
Created attachment 2084143 [details] settings.dat file I have attached my ~/.wordgrinder/settings.dat - it's worth mentioning that I have compiled wg from source as well and successfully launched it, so this file might have been overwritten by the working instance.
(In reply to Simone M from comment #16) > it's worth mentioning that > I have compiled wg from source as well and successfully launched it, so this > file might have been overwritten by the working instance. When you built it from source, did you build version 0.8 or the latest from git?
This message is a reminder that Fedora Linux 42 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 42 on 2026-05-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '42'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 42 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 42 entered end-of-life (EOL) status on 2026-05-27. Fedora Linux 42 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.