Description of problem: Opened GIMP Version-Release number of selected component: luajit-2.1.1720049189-1.fc41 Additional info: reporter: libreport-2.17.15 type: CCpp reason: luajit-2.1.1720049189 killed by SIGSEGV journald_cursor: s=97aa099c66af4d0a9db6d9ecbc74c7fa;i=8413;b=9895525df7fb4d8cb7c1ba05199f57c7;m=25509a8e0;t=622fdde5f0896;x=9e145a75df6ff5f4 executable: /usr/bin/luajit-2.1.1720049189 cmdline: /usr/bin/luajit /usr/lib64/gimp/3.0/extensions/org.gimp.extension.goat-exercises/goat-exercise-lua.lua -gimp 274 117 116 -query 1 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-gimp-38056.scope rootdir: / uid: 1000 kernel: 6.11.0-63.fc41.x86_64 package: luajit-2.1.1720049189-1.fc41 runlevel: N 5 backtrace_rating: 4 crash_function: lgi_marshal_2lua comment: Opened GIMP Truncated backtrace: Thread no. 1 (14 frames) #0 lgi_marshal_2lua at /builddir/build/BUILD/lua-lgi-0.9.2-build/lua51-lua-lgi-0.9.2-20.fc41/lgi/marshal.c:1269 #1 lgi_marshal_field at /builddir/build/BUILD/lua-lgi-0.9.2-build/lua51-lua-lgi-0.9.2-20.fc41/lgi/marshal.c:1522 #2 lj_BC_FUNCC at buildvm_x86.dasc:859 #3 lgi_marshal_access at /builddir/build/BUILD/lua-lgi-0.9.2-build/lua51-lua-lgi-0.9.2-20.fc41/lgi/marshal.c:1547 #4 lj_BC_FUNCC at buildvm_x86.dasc:859 #5 lua_call at /usr/src/debug/luajit-2.1.1720049189-1.fc41.x86_64/src/lj_api.c:1122 #6 lj_cf_package_require at /usr/src/debug/luajit-2.1.1720049189-1.fc41.x86_64/src/lib_package.c:464 #7 lj_BC_FUNCC at buildvm_x86.dasc:859 #8 lua_pcall at /usr/src/debug/luajit-2.1.1720049189-1.fc41.x86_64/src/lj_api.c:1122 #9 docall at /usr/src/debug/luajit-2.1.1720049189-1.fc41.x86_64/src/luajit.c:122 #10 handle_script at /usr/src/debug/luajit-2.1.1720049189-1.fc41.x86_64/src/luajit.c:292 #11 pmain at /usr/src/debug/luajit-2.1.1720049189-1.fc41.x86_64/src/luajit.c:549 #12 lj_BC_FUNCC at buildvm_x86.dasc:859 #13 lua_cpcall at /usr/src/debug/luajit-2.1.1720049189-1.fc41.x86_64/src/lj_api.c:1179 Potential duplicate: bug 2309471
Created attachment 2048746 [details] File: proc_pid_status
Created attachment 2048747 [details] File: maps
Created attachment 2048748 [details] File: limits
Created attachment 2048749 [details] File: environ
Created attachment 2048750 [details] File: open_fds
Created attachment 2048751 [details] File: mountinfo
Created attachment 2048752 [details] File: os_info
Created attachment 2048753 [details] File: cpuinfo
Created attachment 2048754 [details] File: core_backtrace
Created attachment 2048755 [details] File: exploitable
Created attachment 2048756 [details] File: dso_list
Created attachment 2048757 [details] File: backtrace
It actually crashes in lua-lgi.
This message is a reminder that Fedora Linux 41 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 41 on 2025-12-15. 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 '41'. 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 41 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 41 entered end-of-life (EOL) status on 2025-12-15. Fedora Linux 41 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.