Window and font way too big

• Aug 3, 2021 - 12:28

I'm using AV Linux which are based on MX Linux. I think it's Qt5 scaling problem and I'm also using TV monitor. I've been searching for workaround and properly run MuseScore 3 by typing in terminal :

Is there anyway to override these setting permanently ? Perhaps editing some config in text editor but I don't know where it's located. I start to lose my mind because I had more time fixing than writing music

Sorry my bad english


Depending of your desktop environment it should be possible to add these options to the execute command of the properties from your desktop item or by editing the menu entry (via right click).

In reply to by Jojo-Schmitz

There's MuseScore 3 file that I edit the exec= but I don't know how to export it.

[Desktop Entry]
Name=MuseScore 3
GenericName=Music notation
GenericName[fr]=Notation musicale
Comment=Create, play and print sheet music
Comment[ru]=Визуальный редактор нотных партитур
Comment[fr]=Gravure de partitions musicales
Exec=QT_AUTO_SCREEN_SCALE_FACTOR=0 mscore3 -D 100 %F
Keywords=music;notation;composition;composing;arranging;making;sheet music;music notation software;lead sheet;leadsheet;score;full score;scorewriter;MIDI;musicxml;playback;instrument;

On one of my Linux systems, the environment variable doesn't matter, but on the others it does. I set this globally using facilities that are unfortunately very much distribution-specific. My distribution is a special version of Debian for Chromebook, so the way I need to set it probably isn't the way you would. But /etc/environment would probably do the job for you. Or just modify the desktop file as noted. Or create a shell script wrapper and execute that instead of the AppImage file directly.

In reply to by Marc Sabatella

I don't install MuseScore3 via appimage. It already installed by default in AV Linux.

I already try to tweak /etc/environment but nothing change. I found workaround by edit my launcher menu and change the command into env QT_AUTO_SCREEN_SCALE_FACTOR=0 mscore3 -D 100 %F and it finally worked flawlessly. :D

In reply to by lelegurame

Hmm, really? What version of MuseScore do they provide? See Help / About; current version is 3.6.2.

We don't really support or recommend using third party builds like this - they might happen to work, but more often than not they are out of date and have issues with their build processes that cause hard-to-diagnose problems later. So I definitely recommend the AppImage. But anyhow, the same methods as described should work either way.

Do you still have an unanswered question? Please log in first to post your question.