musescore / musescore/MuseScore

Page settings do not show.

Open
#31,127 3 comments 1 reaction 1 assignee View on GitHub

@zacjansheski is already working on this.

Since Nov 21, 2025.

needs review regression MS4 UX/interaction
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

UX/Interaction bug (incorrect behaviour)

Description with steps to reproduce

When I try to open page settings in Formát / Nastavení strany… (in Czech, translated as ‘Format / Page settings…’), it shows nothing instead of page settings, but the following appears in the terminal output.

20:11:03.613 | ERROR | main_thread     | GuiApp::perform | error: qrc:/qml/Muse/UiComponents/StyledMenuLoader.qml:28:1: QML StyledMenuLoader: Created graphical object was not placed in the graphics scene.

20:11:03.613 | WARN  | main_thread     | Qt              | qrc:/qml/Muse/UiComponents/StyledMenuLoader.qml:28:1: QML StyledMenuLoader: Created graphical object was not placed in the graphics scene.
20:11:05.671 | INFO  | main_thread     | ActionsDispatcher::doDispatch | try call action: page-settings
20:11:05.786 | ERROR | main_thread     | InteractiveProvider::onClose | ASSERT FAILED:    obj.objectId.isValid()    /home/runner/work/MuseScore/MuseScore/src/framework/ui/view/interactiveprovider.cpp:694
Supporting files, videos and screenshots

https://github.com/user-attachments/assets/6490eaa2-486a-44a1-8eb2-8cb599925018

In which versions of MuseScore Studio is this issue present?

4.6.3

Regression

Yes, this used to work in a previous version of MuseScore 4.x

Operating system

Arch Linux

Additional context

It used to work in 4.5.2 in a previously installed Arch Linux. After I reinstalled Arch Linux, it does not work even if I try older versions.

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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.