musescore / musescore/MuseScore
Error messages when creating first rehearsal mark
@RomanPudashkin is already working on this.
Since Mar 20, 2026.
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Issue type
Choose option...
Description with steps to reproduce
Error messages about Inconsistent state (for the AccessibilityController) appear in the log.
- Start MuseScore Studio from command line
- create a new score from the Jazz/Big Band template
- select the whole measure rest in the first measure and press ctrl-M to create a rehearsal mark. press Esc
- result: a rehearsal mark A is created
- Observe error messages appearing in the terminal
The following INFO/ERROR/WARN messages appear:21:20:36.086 | INFO | main_thread | ActionsDispatcher::doDispatch | try call action: rehearsalmark-text
21:20:36.108 | ERROR | main_thread | AccessibilityController::stateChanged | Inconsistent state for item: "Rest Measure, Measure 1 Beat 1"
21:20:36.110 | ERROR | main_thread | AccessibilityController::stateChanged | Inconsistent state for item: "Rehearsal mark A, Measure 1 Beat 1"
21:20:48.633 | INFO | main_thread | ActionsDispatcher::doDispatch | try call action: action://cancel
21:20:48.634 | INFO | main_thread | ActionsDispatcher::doDispatch | try call action: action://notation/cancel
21:20:48.634 | WARN | main_thread | Score::endCmd | no command active
21:20:48.645 | ERROR | main_thread | AccessibilityController::stateChanged | Inconsistent state for item: "Rehearsal mark A, Measure 1 Beat 1"
No Error messages (or warning messages) should appear. There should be no inconsistent state of any Rest Measure or Rehearsal mark.
Supporting files, videos and screenshots
In which versions of MuseScore Studio is this issue present?
OS: Ubuntu 24.04.4 LTS, Arch.: x86_64, MuseScore Studio version (64-bit): 4.7.0-260317043, revision: github-musescore-musescore-e51c5a2
Regression
Choose option...
Operating system
Ubuntu 24.04.4 LTS
Additional context
No response
Checklist
- This report follows the guidelines for reporting bugs and issues
- I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
- I have attached all requested files and information to this report
- I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.