musescore / musescore/MuseScore

Exporting is broken

Open
#33,341 17 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

community os: linux
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

Import/export issue

Description with steps to reproduce

Using the AppImage export in any format.

Supporting files, videos and screenshots

11:53:28.232 | WARN | main_thread | Qt | qrc:/qml/Muse/UiComponents/StyledMenuLoader.qml:28:1: QML StyledMenuLoader: Created graphical object was not placed in the graphics scene.
11:53:29.098 | INFO | main_thread | ActionsDispatcher::doDispatch | try call action: file-export
11:53:30.715 | ERROR | main_thread | GuiApp::perform | error: qrc:/qml/Muse/Ui/internal/FileDialog.qml:25:1: QML FileDialog: Window.window does only support types deriving from Item

11:53:30.716 | WARN | main_thread | Qt | qrc:/qml/Muse/Ui/internal/FileDialog.qml:25:1: QML FileDialog: Window.window does only support types deriving from Item

In which versions of MuseScore Studio is this issue present?

4.6.5

Regression

I was unable to check

Operating system

Linuz -> Arch Linux -> Zenned

Additional context
  • Being unable to export makes the app almost useless.
  • The precompiled package is also broken too, due to a qt-6.11 bug.
  • The Flatpak package works. But I don't want to use that, as nothing on my distro requires Flatpaks.
  • But there is no way to make a working native package, either compiled from sourced or wrapped around the AppImage.
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.

Research direction

Reproduce exporting in any format with the AppImage on MuseScore Studio 4.6.5 and begin with the reported qrc:/qml/Muse/Ui/internal/FileDialog.qml warning. Compare the AppImage behavior with the working Flatpak and the supplied export logs; done means export works from the native package without the reported failure.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.