Casper Jeukendrup

Just in case: the fact that it's fixed in the nightly build may also mean that it's a MuseScore settings issue. Nightly builds namely don't read/write configuration from/to the same...

When you click "Details", it shows you which changes are necessary

Related to #19809

And the `master` nightly builds from https://musescore.org/en/nightly-builds?

Might be interesting to check if Qt 6 has brought any improvement w.r.t. this

@MarcSabatella Can we consider this fixed now the Wayland problem has been fixed? Trying to fix it for `xcb` (or rather Xwayland) too might not be worth the effort since...

On macOS, no crash, but strange behaviour too: panels already jump to the second screen even if I'm still hundreds of pixels away from the edge of the first screen....

I think we should close this as a duplicate of https://github.com/musescore/MuseScore/issues/17648, as it is essentially the same problem. We're planning to address that issue (at least in a temporary manner)...

If you haven't done so already, it would be good to try the `master` nightly builds too (https://musescore.org/en/nightly-builds), because those contain even more changes to shortcut handling

Have you by chance already tried whether this is fixed in MuseScore 4.4, which has been released today? MuseScore 4.4 uses Qt 6.2 instead of 5.15, which may have improved...