musescore / musescore/MuseScore
Bad rendering in AppImage version with non-integer scaling (Linux)
@DmitryArefiev 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
UI bug (incorrect info or interface appearance)
Description with steps to reproduce
Original forum post I was advised to make back in February: https://musescore.org/en/node/389739
Tl;dr:
- When I run the AppImage version of MuseScore in Ubuntu+KDE Plasma on my High-DPI laptop, and my system scaling is set to anything besides 100% or 200%, the score display in MuseScore has lots of visual artifacts and lacks smoothness of lines and curves. This only affects the score display, not the overall program UI (however it does include formatting marks like the line break symbol).
Supporting files, videos and screenshots
Example of poor rendering: (it happens in any score, but it is more apparent with really dense scores.)
In which versions of MuseScore Studio is this issue present?
OS: Ubuntu 25.10, Arch.: x86_64, MuseScore Studio version (64-bit): 4.6.5-253511702, revision: github-musescore-musescore-653f38d
Regression
No.
Operating system
Kubuntu 25.10 (Questing Quokka)
Additional context
System Info:
Operating System: Kubuntu 25.10
KDE Plasma Version: 6.4.5
KDE Frameworks Version: 6.17.0
Qt Version: 6.9.2
Kernel Version: 6.18.7-061807-generic (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ Ultra 7 258V
Memory: 32 GiB of RAM (30.9 GiB usable)
Graphics Processor: Intel® Graphics
Manufacturer: LENOVO
Product Name: 83HM
System Version: Yoga Slim 7 15ILL9
Laptop screen resolution: 2880 x 1800
Approximate screen size: 14"
Also, at least one other person has had the same issue back in 2022 on MuseScore 3.6: see https://musescore.org/en/node/337398
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.