Audiveris
Application won't open.
Describe the bug I just installed the MacOS installer to install the program, and when I did everything worked fine and seemed normal. I dragged it over and everything and it showed up in my applications. When I tried to open the application though, it just seemed to refuse. I put it on my task bar aswell to see if it stopped trying to open every time and it did each time that I tried to open it.
To Reproduce If possible and relevant, post the input image so that we can reproduce the problem.
Expected behavior When I clicked on the app I expected it to open up into a gui.
Screenshots If applicable, add screenshots to help explain your problem.
Audiveris environment:
If possible, post the content of the "Help | About" dialog
(This dialog provides a Copy button which copies its content to the clip-board)
Otherwise, please post the information manually:
- OS: MacOS
- Audiveris version: 5.5.0-bis
- Building from sources: Don't know.
- Using an installer: Yes
Additional context Add any other context about the problem here.
@msteed01 The Audiveris macOS installer was published as a pre-release 2 days ago. So you are probably one of the first users to try it. Congratulations! :-)
I personally have no access to a macOS environment, therefore I can't really help you efficiently. Have you read the handbook section on installation, and especially the section on macOS? If not, I'd strongly suggest that you have a look at it.
I'm having the same issue. I completed all of the security and privacy steps, and the application attempts to open, but quits almost immediately. Console log from the attempt attached. It looks like there is something strange going on with session management - but I'm not super familiar with macOS development.
@fbmrqs
Fabio, could you have a look at @cszalaj log file in the message above? I cannot decrypt what is happening.
Same here, I tried launching the binary directly to get a Terminal output and here's what it shows:
Unrecognized option: --add-exports java.desktop/com.apple.eawt=ALL-UNNAMED
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
I am on Apple Silicon, will try compiling.
@mikypilota
--add-exports java.desktop/com.apple.eawt=ALL-UNNAMED
There is a typo in the option, it should be:
--add-exports=java.desktop/com.apple.eawt=ALL-UNNAMED
I will publish a new pre-release immediately, so that you can retry a download and install.
@mikypilota New pre-release just published
Hi, thanks for looking into this. I have downloaded the new installer but it seems like the very same issue persists.
I have downloaded the installer from the release section but just to sure I also directly downloaded the artifact produced from the actions run.
On the contrary, running with gradlew works!
I have downloaded the installer from the release section but just to sure I also directly downloaded the artifact produced from the actions run.
On the contrary, running with gradlew works!
This is not very clear for me.
- You can get the installer from the assets of the release
- Or you can go to the actions workflow and grab the installer there
By construction, these files are identical.
When you say that gradlew works, what do you mean precisely?
- The ability to build the app and run (./gradlew :app:run)
- The ability to build the installer and then use it (./gradlew :packaging:jpackage)
I guess the former works of course. I'm right now more interested by the latter. Could you confirm what you did?
I downloaded the installer from the release section, and upon open I still get:
Unrecognized option: --add-exports java.desktop/com.apple.eawt=ALL-UNNAMED
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
Which made think that perhaps the wrong installer was attached to the release (eg a reupload of the old one), so to be sure, I downloaded the installer from this run, cross checking the referenced commit and it's indeed the one where you made the relevant changes.
Running ./gradlew :packaging:jpackage on my machine produces a working installer.
It's also worth noting that when using the installer built from the GitHub VM I can see no app icon.
Running
./gradlew :packaging:jpackageon my machine produces a working installer.
This is already a very good news by itself.
I suspect I made something wrong when building the release.
The tag 5.5.0-ter points to the old version of packaging/build.gradle.
I will fix all this.
@hbitteur Though out of curiosity I also built the installer from master, eg where you still have --add-exports java.desktop/com.apple.eawt=ALL-UNNAMED and it also works. Which makes me think it's either the environment (I am using openjdk 21.0.6) or something related to signing the bundle (which BTW also causes the app to be tagged for quarantine and I need to manually allow it or remove the quarantine attribute, here for more info).
I'm a bit lost.
I made the fix of packaging/build.gradle on the development branch, committed and pushed.
In a browser, looking directly on github site, and selecting the development branch, the file is OK at line 181. Fine.
Still in the browser, selecting the master branch, the file is OK!!! at line 186. But I never made the fix on this branch!
@mikypilota Yet another pre-release. Take the latest one (tag 5.5.0-alpha) Should be OK this time.
Should be OK this time.
And it is! Attached installer to the 5.5.0-alpha tag is working now.
Before I mentioned that running jpackage without the fix would produce a working installer anyways, but it could have been because I did not run ./gradlew clean between builds. I have tested again now and I can confirm that resetting locally to before 1e18e6c, cleaning and packaging will output a broken installer. Pulling, cleaning and running jpackage again will produce a good installer.