Regression on 3.4.1 (Linux) - CLI JSON job hangs - "qrc:/qml/TelemetryPermissionDialog.qml:30: ReferenceError: globalStyle is not defined"
When I run execute this JSON job on the CLI with the AppImage on Linux, MuseScore hangs. This worked previously in 3.3.4.
I have verified that this regression is on Linux ONLY. Windows x64 (3.4.1) and macOS (3.4.1) are unaffected.
I have supplied the JSON and MSCZ in the attached zip zile.
To reproduce, perform the following steps on Linux:
1) Unzip the files to a directory
2) Navigate to that directory in Terminal
3) wget http://ftp.osuosl.org/pub/musescore-nightlies/linux/x86_64/MuseScore-3… to retrieve MuseScore 3.4.1
4) chmod +x musescore3 (requires sudo)
5) ./MuseScore-3.4.1-x86_64.AppImage -j Blaster\ Master\ -\ Area\ 7.json -r 144 -m -s -w
6) ???
7) Observe that MuseScore starts up, says something about globalStyle not being defined, and hangs.
Here is my console output for MuseScore 3.4.1:
jroque@localhost:~$ ./MuseScore-3.4.1-x86_64.AppImage -j Blaster\ Master\ -\ Area\ 7.json -r 144 -m -s -w
/usr/lib/x86_64-linux-gnu/libjack.so.0
/usr/lib/x86_64-linux-gnu/libnss3.so
qrc:/qml/TelemetryPermissionDialog.qml:30: ReferenceError: globalStyle is not defined
qrc:/qml/DialogButton.qml:50: ReferenceError: globalStyle is not defined
qrc:/qml/DialogButton.qml:50: ReferenceError: globalStyle is not defined
Here is the console output when running MuseScore 3.3.4:
jroque@localhost:~$ ./MuseScore-3.3.4-x86_64.AppImage -j Blaster\ Master\ -\ Area\ 7.json -r 144 -m -s -w
/usr/lib/x86_64-linux-gnu/libjack.so.0
convert ...
part <[C]-Blaster Master - Area 7.pdf>
part <[Bb]-Blaster Master - Area 7.pdf>
part <[Eb]-Blaster Master - Area 7.pdf>
part <[F]-Blaster Master - Area 7.pdf>
part <[Alto]-Blaster Master - Area 7.pdf>
part <[Bass]-Blaster Master - Area 7.pdf>
part <[C]-Blaster Master - Area 7.png>
part <[Bb]-Blaster Master - Area 7.png>
part <[Eb]-Blaster Master - Area 7.png>
part <[F]-Blaster Master - Area 7.png>
part <[Alto]-Blaster Master - Area 7.png>
part <[Bass]-Blaster Master - Area 7.png>
part <[MID][C]-Blaster Master - Area 7.mid>
part <[MID][Bb]-Blaster Master - Area 7.mid>
part <[MID][Eb]-Blaster Master - Area 7.mid>
part <[MID][F]-Blaster Master - Area 7.mid>
part <[MID][Alto]-Blaster Master - Area 7.mid>
part <[MID][Bass]-Blaster Master - Area 7.mid>
to <[MP3]-Blaster Master - Area 7.mp3>
QMutex: destroying locked mutex
to <[MID]-Blaster Master - Area 7.mid>
... success!
Here is the version of Linux I am running on:
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04.3 LTS"
NAME="Ubuntu"
VERSION="18.04.3 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.3 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic
| Attachment | Size |
|---|---|
| 3.4.1-CLI-hang.zip | 3.07 MB |
Comments
Aside: Is this a joke about Blaster Master and Jason with his pet frog Fred?
In reply to Aside: Is this a joke about… by worldwideweary
No joke intended. I run VGLeadSheets.com which hosts over 400 lead sheets from video game music, and MuseScore is an integral part of our CICD pipeline. The song is indeed Blaster Master - Area 7.
I tried this with the latest nightly build, MuseScoreNightly-202001251252-master-ad4955f-x86_64.AppImage, and this does not appear to be an issue with it. Could it be related to TelemetryPermisisonDialog? Is there a way to disable that via CLI?
In reply to I tried this with the latest… by Blaarghinator
It sure is telemetry related and that is disabled in development builds
In reply to It sure is telemetry related… by Jojo-Schmitz
I think this is also related to the fact that the machine I'm running MuseScore on is remote, and has no proper GUI if that helps anything.
I see a hang in 3.4.1 even when trying to start MuseScore normally. I get an error "ReferenceError: globalStyle is not defined" in the terminal, and although the "Help Us Improve MuseScore" dialog appears I am unable to click any of the buttons, and a result MuseScore cannot start.
In reply to I see a hang in 3.4.1 even… by music_by_jeff
On my machine, everything is local. I'm running Ubunu 18.04.3 LTS
I met the exact same problem and came up with a workaround.
Like it as been said in other comments, this hanging is linked to a telemetry popup that opens when musescore >= 3.4 starts.
The solution to this is to update the config file. On a debian / ubuntu machine, it can be found in
~/.config/MuseScore/MuseScore3.ini. Add the following lines in the [application] section:startup\telemetry_access_requested=3.4.1
telemetry\allowed=false
I'd like to add that even though Musescore is really an incredible software, it is really hard to run in headless mode. Maybe the use case is not common enough.
In reply to I met the exact same problem… by Thibaultj
A fix for this has just been pushed and will be included in 3.4.2
Running headless will automatically disable telemetry for that run.
In reply to A fix for this has just been… by jeetee
Sweet, thanks for the news!