Start MuseScore 3.4.2 freezes on Linux - globalStyle is not defined

• Feb 11, 2020 - 08:59

Hello, either MuseScore 3.4.1 or with MuseScore 3.4.2 crash on Linux (Debian Buster 64 bit). After double-click to start, I see the telemetry windows and crash. I join a screenshoot.

If I start MuseScore with the terminal, the error is "TelemetryPermissionDialog.qml:37: ReferenceError: globalStyle is not defined"

stephanie@PcServer:~/Software/MuseScore$ ./MuseScore-3.4.2-x86_64.AppImage
/usr/lib/x86_64-linux-gnu/libjack.so.0
/usr/lib/x86_64-linux-gnu/libnss3.so
qrc:/qml/TelemetryPermissionDialog.qml:37: ReferenceError: globalStyle is not defined
qrc:/qml/DialogButton.qml:74: ReferenceError: globalStyle is not defined
qrc:/qml/DialogButton.qml:74: ReferenceError: globalStyle is not defined
^C
stephanie@PcServer:~/Software/MuseScore$

Nightly builds work.

Best regards,

Stephanie

Attachment Size
Schermata del 2020-02-11 09-51-20.png 150.26 KB

Comments

Crash is probably not related to globalStyle message as it gets shown when MuseScore starts normally as well. Also your console output shows that you probably terminated MuseScore with Ctrl+C buttons, does it usually crash if you just wait for a while or after some action?

In reply to by stephanie4

Freezing and crashing aren't quite the same in computerdevelopertechnobabble.

Freezing means that the software is likely either doing something or waiting for something, but it is still there. (For example when a window opens off-screen and awaits user interaction).

Whereas crashing means that the program terminates itself automatically (so you wouldn't have had to press Ctrl-C because the program would've ended already...).

Try a reset to factory settings by running MuseScore with the -F command line argument.

In reply to by dmitrio95

Thanks, clicking on the blue area doesn't resolve, but clicking Esc the problem seems resolved und MS is loaded. If I quit MS and restart, the splash screen is not showed and it works.

Thank you very much, best regards,

Stephanie

stephanie@PcServer:~$ cd /home/stephanie/Software/MuseScore
stephanie@PcServer:~/Software/MuseScore$ ./MuseScore-3.4.2-x86_64.AppImage -f
/usr/lib/x86_64-linux-gnu/libjack.so.0
/usr/lib/x86_64-linux-gnu/libnss3.so
qrc:/qml/TelemetryPermissionDialog.qml:37: ReferenceError: globalStyle is not defined
qrc:/qml/DialogButton.qml:74: ReferenceError: globalStyle is not defined
qrc:/qml/DialogButton.qml:74: ReferenceError: globalStyle is not defined
qrc:/qml/DialogButton.qml:74: ReferenceError: globalStyle is not defined
qrc:/qml/DialogButton.qml:74: ReferenceError: globalStyle is not defined
qrc:/qml/TelemetryPermissionDialog.qml:37: ReferenceError: globalStyle is not defined
QMutex: destroying locked mutex
stephanie@PcServer:~/Software/MuseScore$

In reply to by dmitrio95

Hello, I have only one monitor. I use a Debian Buster 64 bit:

stephanie@PcServer:~$ cat /proc/version
Linux version 4.19.0-8-amd64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.98-1 (2020-01-26)
stephanie@PcServer:~$ cat /etc/issue
Debian GNU/Linux 10 \n \l

stephanie@PcServer:~$ cat /etc/*release
PRETTY_NAME="Debian GNU/Linux 10 (buster)"
NAME="Debian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
stephanie@PcServer:~$

Thank you and best regards,

Stephanie

I have exactly the same problem with 3.6. in Ubuntu Studio 20.04
I upgraded from 3.2.3 (installed from official Ubuntu repository). It did not have that problem.
If I pressed Esc the problem disappeared.
If I use the -F option the problem returns.
The only error message is 'globalStyle is not defined' (same as Stephanie)

In reply to by fauzie

-F reset everything to defaults, so yes if you had that issue by default, then it will reappear when restoring defaults..

The problem is some incompatibility between Qt and your window manager, so pressing Esc is the correct way to close that telemetry window. If you then later on do wish to enable telemetry you can do so in the advanced settings.

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