musescore / musescore/MuseScore

Transpose dialog disappears immediately when there is a selection, with QT_QPA_PLATFORM=xcb

Open
#24,296 13 comments 0 reactions 1 assignee View on GitHub

@zacjansheski is already working on this.

Since Dec 16, 2025.

needs review os: linux 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

Select some measures, then choose Tools->Transpose...

A box appears briefly in the middle of the screen and then immediately vanishes, as if it tried to open the dialog and then immediately closed it.

If nothing is selected, then Tools->Transpose... selects the entire score and displays the Transpose dialog, as expected.

I'm on Fedora 40, using musescore-4.3.2-12.fc40.x86_64 run with QT_QPA_PLATFORM=xcb (to work around issue 15285). Without that set, the dialog appears and works as it should.

This looks similar to issue 17440, which was closed as a dup of 18608, the root cause of which was believed to be https://gitlab.gnome.org/GNOME/mutter/-/issues/2820, but I have mutter-46.4-1.fc40.x86_64, which I believe should have the fix.

Supporting files, videos and screenshots

none

What is the latest version of MuseScore Studio where this issue is present?

4.3.2

Regression

I was unable to check

Operating system

Fedora 40

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

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.