When I attempt to build a score using a PianoStaff or GrandStaff (which contains more than one sub-staff), lilypond crashes. Reproducible: Always Steps to Reproduce: 1. Attempt to build a minimal reproducer (which I will attach) with lilypond-2.25.4 Actual Results: Slightly varying modes of crashing. #1) Without dumping core: --- 8< --- nils@makake:~/music> lilypond minimal.ly GNU LilyPond 2.25.4 (running Guile 2.2) Processing `minimal.ly' Parsing... Interpreting music... Preprocessing graphical objects... Finding the ideal number of pages... Fitting music on 1 page... Drawing systems... /usr/share/lilypond/2.25.4/ly/init.ly:64:2: error: Guile signaled an error for the expression beginning here # (let ((book-handler (if (defined? 'default-toplevel-book-handler) In procedure scm_hash_fn_create_handle_x: Error while printing exception. --- >8 --- #2) With dumping core: --- 8< --- nils@makake:~/music> lilypond minimal.ly GNU LilyPond 2.25.4 (running Guile 2.2) Processing `minimal.ly' Parsing... Interpreting music... Preprocessing graphical objects... Finding the ideal number of pages... Fitting music on 1 page... Drawing systems... /usr/share/lilypond/2.25.4/ly/init.ly:64:2: error: Guile signaled an error for the expression beginning here # (let ((book-handler (if (defined? 'default-toplevel-book-handler) In procedure scm_hash_fn_create_handle_x: Wrong type argument in position 1 (expecting hash-table): Segmentation fault (core dumped) --- >8 --- Expected Results: It builds a PDF from the score. - I get the same behavior on Fedora 38 and Rawhide. - Using the lilypond-2.25.3 Fedora package _or_ the 2.25.4 binary from upstream doesn’t exhibit the issue.
Created attachment 1965173 [details] Minimal reproducer exhibiting the issue
Interesting. If I rebuild using ./configure instead of %configure the bug goes away. Now to dig and see which flag is triggering the problem.
Or not. The above is true if I build that way outside the RPM, but remains in an RPM.
Reported upstream.
(In reply to Gwyn Ciesla from comment #3) > Or not. The above is true if I build that way outside the RPM, but remains > in an RPM. This is thoroughly weird, I can’t seem to reproduce it when building from source. Or else I would at least have attempted to bisect to zero in on the cause… 😬
Upstream sent a patch that fixes this, update incoming.
FEDORA-2023-02f1cb5ef4 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-02f1cb5ef4
FEDORA-2023-02f1cb5ef4 has been pushed to the Fedora 38 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-02f1cb5ef4` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-02f1cb5ef4 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
The update fixes the issue for me, both with the minimal producer and the original file I encountered it first with. Thank you very much!
Awesome, anytime!
*** Bug 2208744 has been marked as a duplicate of this bug. ***
FEDORA-2023-02f1cb5ef4 has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.