AppImage issue under Fedora 36 - Scaling and unresponsiveness

• May 12, 2022 - 08:08

Hi!

I'm running into a couple of issuea under Fedora 36. First of all the app-scaling is enormus. I had this issue before and launching the appimage from the terminal and prefixing it with:
QT_AUTO_SCREEN_SCALE_FACTOR=0 does fix the scaling.

The appimage though is "hanging" every few second and I'm getting a pop-up "Musescore3 is not responding" - FORCE QUIT or WAIT. It never crashes, but I have to wait a while.

Is there any way to fix the latter issue? Any help appreciated!


Comments

Hi, it seems we posted about the same issue at the very same time. I am having issues also with other package formats in Fedora

Just out of curiosity, which cpu and gpu do you use? On my laptop with an i5-11th gen with igpu MS shows up huge, on my desktop with a fairly older i5 everything is ok

In reply to by sberla

It's unlikely to have anything to do with CPU or GPU. Rather, it's almost certainly about your specific display and its resolution, along with any scaling you have set in the OS. For instance, if your display is much more than 100 DPI, then your OS is probably scaling things for the benefit of programs that don't know how to deal with high DPI displays, but then still reporting the higher resolution to MuseScore, which it dutifully responds to by also scaling for the higher resolution. So workarounds were created, like setting that environment variable (also QT_SCALE_FACTOR, where you can specify the scaling directly, like as 1.6 or whatever) or using the "-D" command line option to specify the true effective resolution

Any crashes you are seeing are likely unrelated.

In reply to by Marc Sabatella

Hi Marc, thanks for clarifying this.
Strangely -D made no change except for the scaling of icons and a few other elements. The UI stayed huge no matter which value I would give.
In the end, I managed with a workaround. I integrated the appimage into the system and appended the QT_AUTO_SCREEN_SCALE_FACTOR=0 variable to the .desktop file. The crash apparently seems related to the start centre, as Jojo Schmitz pointed out in another post. No start centre no crash. Or with start centre but disabling the web part of the startcenter with variable -w.

In reply to by sberla

Every OS is different in terms of how it handles scaling, probably also Linux distribution and every window manager within a given distribution. Plus different devices drivers for different displays; you end up with an absolutely insane number of possible configurations. Which is why there is no one-size-fits-all solution.

What value did you give the “-D”? Based on your description, I’d have assumed maybe 100 would do the trick. But not if your OS is scaling only graphics and not text or vice versa.

In reply to by Marc Sabatella

I gave it every possible value. I tried 10, 36, 72, 100, 150, 1500 and it only affected the icon size. Even with 1500 I got humongous icons but same text and UI elements. Even the Splash screen stays the same no matter the dpi

Rather than the os, it must be related to hardware or how it is handled in the os. The issue shows up only on my laptop, on the desktop the appimage works great. Both machine run the very same Fedora installation

In reply to by sberla

Well, it's hardware in the sense display is hardware, but it's more about the device driver and the OS settings for scaling. "-D" indeed only affects certain elements - the ones that the most common OS / configurations don't scale correctly otherwise. But in other cases, with other OS's or other displays, it might be other things that are not scales, and hence you might need one of the other workarounds. Including going into your OS settings to change how scaling is performed.

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