Reporting bugs - GNU LilyPond
Description: GNU LilyPond

Next: Error messages, Previous: Updating files with convert-ly, Up: Running LilyPond

### 12.4 Reporting bugs

If you have input that results in a crash or an erroneous output, then that is a bug. We try to respond to bug-reports promptly, and fix them as soon as possible. Help us by sending a defective input file, so we can reproduce the problem. Send the report via:

    http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.bugs

A few tips:

- Try to produce a very small input file which demonstrates the problem; one or two bars is often sufficient to reproduce a bug. The smaller the input file is, the easier it is for us to debug the problem.
- Don't forget to tell which version of LilyPond you use!
- If possible, use `ragged-right` in your example. This makes sure that the bug can be reproduced in all paper sizes.

Here is an example of a good bug report:

    It seems that placement of accidentals is broken.  In the
    following example, the accidental touches the note head.

    Using Mac OSX 10.3.7, lilypond 2.7.32

    \version "2.7.32"
    \layout { ragged-right = ##t }
    \relative c'' {
       a4 b cis d
    }

This page is for LilyPond-2.8.8 (stable-branch).

Other languages: English.
Using automatic language selection.