musescore / musescore/MuseScore

Weird circular dependencies in this repo cause the MuseScore flatpak to have very outdated screenshots

Open
#34,950 0 comments 0 reactions 1 assignee View on GitHub

@shoogle is already working on this.

Since Sep 18, 2026.

needs review P3
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

Other type of issue

Description with steps to reproduce

This file in this repo here contains references to outdated screenshots in the Musescore flatpak's repo:

https://github.com/musescore/MuseScore/blob/main/buildscripts/packaging/Linux%2BBSD/org.musescore.MuseScore.appdata.xml.in

For example, there is a reference to

https://raw.githubusercontent.com/flathub/org.musescore.MuseScore/master/screenshots/01-start-center.png

Because these files are referenced here, the Musescore flatpak project does not want to update the screenshots for the flatpak. They say this is an upstream responsibility, because the org.musescore.MuseScore.appdata.xml.in file is maintained here.

See these issues:

https://github.com/flathub/org.musescore.MuseScore/issues/156
https://github.com/flathub/org.musescore.MuseScore/issues/164

Supporting files, videos and screenshots

See links above

In which versions of MuseScore Studio is this issue present?

Does not depend on the MS version

Regression

I was unable to check

Operating system

Linux

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.