MacOS - Cant run project from source / how did you manage to delete files without read & write permission #187
Comments
Yetispapa
changed the title
|
Hi @Yetispapa, Thank you for using OwlPlug ! 🙂
If the current user has no rights to read or modify these files, OwlPlug can't display or delete them. The only way is to run OwlPlug with elevated privileges.
It seems you are compiling OwlPlug with Java 19. In this version, a new class I think the compilation error can be fixed by adding the following line at the top of the import javafx.concurrent.Worker.State;I usually compile OwlPlug using openjdk17, so there might be some work to do for targeting openjdk19. |
|
Whoops, I missed something 😄 You have to add the following import in AbstractTask: import javafx.concurrent.Worker;And also change line 102, with this if (this.getState().equals(Worker.State.FAILED)) {
prefix = "F";
} |
|
@DropSnorz, thanks for the fast response 😁
Understand, but I normally don't run the app as a root, right? In MacOS its actually not that easy. You have to run the app through a terminal via sudo. Or how is it with Java? It was no deal for me, to uninstall Java 19 and installed Java 17. Its now running in: openjdk version "17.0.5". What version do you have? Unfortunately, if I follow your steps: I can now run Jan 06, 2023 10:12:09 PM com.sun.javafx.application.PlatformImpl startup This output was now via: Can you maybe help me here again. Thanks in advance 🙂 |
Have you faced unexpected behavior? The
Arrg, you are now facing this internal JDK bug on macOS. 😓 Can you show me the output of: The best way to get rid of this error seems to switch back to JDK 17.0.5. |
No, I was just curious. I'm a swift developer and had a similar case, where I wanted to delete files / directories under
I switched to 17.0.5 now and also let maven point to 17. Here are the terminal outputs:
Unfortunately, I still got the issue / an exception: Thanks for your help @DropSnorz 😄 |
I see, but no, I've done nothing to handle this particular case. For such use cases, OwlPlug app must be run with admin privileges from the command line or other ways provided by the OS.
Ok, it's more complicated than I tough 😄 When I'm producing OwlPlug binaries, I'm always using the latest JDK 17.X.X . The latest published OwlPlug version, 1.22.1, has been built using JDK 17.0.3 @Yetispapa Can you try with other JDKs 17 minor versions, I suggest the following order to try:
I've read the OpenJFX (app gui framework) mailing list, this bug has been resolved on OpenJFX 20 and it's a potential candidate for a backport to OpenJFX 17. I'll keep you updated on this. This problem will be a critical concern for the project, because I have a new version to publish in a few weeks, and the release binaries will be affected by the same issue on macOS Ventura. 😟 |
|
A patch has been released on OpenJFX 19.0.2.1. I'll keep the JDK up to date with the latest LTS 17.X.X and migrate the app from OpenJFX 17 to 19.0.2.1 |
|
Hey @DropSnorz, |
|
No problems. I've pushed the fix on the You should be able to run OwlPlug from this branch with any JDK 17. |
|
I've released the fix with OwlPlug 1.23.0 yesterday. You should be able to compile from the |
|
Awesome! Thanks @DropSnorz. I still didn't have much time unfortunately, but we can close this issue if you want and I will check it as soon as I have time :) |
|
I am closing this after inactivity. The app should be able to start on macOS. |
Hi @DropSnorz,
first of all. Thanks for this great project. Upfront a question: How did you manage to delete files / folders from
/Library/Audio/Plug-Insas those have not the read & write permission, so only administrators can delete themSecond, as i'm not a Java developer, I wanted to dig a bit in the project and wanted to run it from source, also to avoid the "damaged" error on MacOS. Unfortunately, I can't run it from source. Tried the latest release and master. As said, don't judge me, I have not that many expierence with Java.
When I run
mvn clean installI got this output, where owlplug-client has a failure:
This is probably the reason for this issue, after running:
Thanks in advance,
Cheers
The text was updated successfully, but these errors were encountered: