Description of problem: maxima killed by SIGSEGV Version-Release number of selected component (if applicable): 5.45.1-3.fc37.x86_64 How reproducible: always Steps to Reproduce: 1. run `maxima` Actual results: Segmentation fault (core dumped) Expected results: A running maxima session. Additional info: I was unable to report the bug automatically: --- Running report_uReport --- Server responded with an error: 'Element 'stacktrace' is invalid: List element is invalid: Element 'frames' is invalid: List element is invalid: Element 'file_name' is missing' ('report_uReport' exited with 1) Installing a different maxima runtime (I tested maxima-runtime-clisp, the default seems to be sbcl), and running with `maxima -l clisp` succeeds without a segfault.
After reading https://maxima.sourceforge.io/lisp.html I tried out just running `rmaxima`--which succeeded. $ rmaxima Maxima 5.45.1 https://maxima.sourceforge.io using Lisp SBCL 2.0.1-8.fc36 Distributed under the GNU Public License. See the file COPYING. Dedicated to the memory of William Schelter. The function bug_report() provides bug reporting information. (SBCL for F36?) Listing available runtimes still makes it crash: $ rmaxima --list-avail rlwrap: warning: maxima crashed, killed by SIGSEGV (core dumped). rlwrap itself has not crashed, but for transparency, it will now kill itself with the same signal warnings can be silenced by the --no-warnings (-n) option But it stopped working after running the following session: $ rmaxima Maxima 5.45.1 https://maxima.sourceforge.io using Lisp SBCL 2.0.1-8.fc36 Distributed under the GNU Public License. See the file COPYING. Dedicated to the memory of William Schelter. The function bug_report() provides bug reporting information. (%i1) 1+1 1+1 Maxima encountered a Lisp error: parser: end of file while scanning expression. Automatically continuing. To enable the Lisp debugger set *debugger-hook* to nil. Now all I get is: $ rmaxima rlwrap: warning: maxima crashed, killed by SIGSEGV (core dumped). rlwrap itself has not crashed, but for transparency, it will now kill itself with the same signal warnings can be silenced by the --no-warnings (-n) option
More data points: running in a fresh F37 toolbox yields $ maxima Maxima 5.45.1 https://maxima.sourceforge.io using Lisp SBCL 2.0.1-8.fc36 Distributed under the GNU Public License. See the file COPYING. Dedicated to the memory of William Schelter. The function bug_report() provides bug reporting information. (again, SBCL claims to be compiled for F36?) No crashes after running a similar session as in my other comment for `rmaxima`. My installed F37 (for which I created the original bug report) has been initially installed as F37-beta.
(In reply to René Kraneis from comment #1) > Now all I get is: > $ rmaxima > > rlwrap: warning: maxima crashed, killed by SIGSEGV (core dumped). > rlwrap itself has not crashed, but for transparency, > it will now kill itself with the same signal > > warnings can be silenced by the --no-warnings (-n) option I randomly do get a working session: $ rmaxima Maxima 5.45.1 https://maxima.sourceforge.io using Lisp SBCL 2.0.1-8.fc36 Distributed under the GNU Public License. See the file COPYING. Dedicated to the memory of William Schelter. The function bug_report() provides bug reporting information. Statistics for the nth run of `rmaxima`, that did not lead to SIGSEGV: sum: 101 min: 1 max: 20 median: 3.5 average: 5.6 Some fuzzing around shows, that the same is true for just running `maxima`, it was just by chance, that `rmaxima` succeeded on first try. I have no idea, what's going on and don't see this behavior in my F37 toolbox.
This message is a reminder that Fedora Linux 37 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05. 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 '37'. 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 37 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 37 entered end-of-life (EOL) status on None. Fedora Linux 37 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.