-
Notifications
You must be signed in to change notification settings - Fork 135
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Linux DEB package does not set correct permission on jre/lib/jspawnhelper #174
Comments
Hi @fvarrui , After installation of the DEB package, the issue is solved 100% if the user performs: sudo chmod 755 jre/lib/jspanwhelper from the package installation folder, so the DEB installer needs to perform this and then all will be okay ;-) Cheers, |
in src/main/java/io.github.fvarrui.javapackager/packagers/GernerateDEB you can add the following to the if (bundleJre) { } part to fix it : // set correct permissions on jre/lib/jspawnhelper Mapper javaSpawnHelperMapper = new Mapper(); File jSpawnHelperFile = new File(appFolder, jreDirectoryName + "/lib/jspawnhelper"); Data javaSpawnHelperData = new Data(); dataProducers.add(javaSpawnHelperData); // Now the DEB installer produces a working application on Linux Mint and Ubuntu and probably thus on all DEB distributions. Cheers, |
Hi @AstroPixelProcessor! |
Awesome @fvarrui , thank you very much ! |
I'll release JavaPackager 1.6.6 to Maven Central ASAP. |
JavaPackager v1.6.6 released to Maven Central |
I'm submitting a…
Short description of the issue/suggestion:
Linux DEB installer installs a non working java application in terms of being able to load native libs from external library JOGL (OpenGL) that needs to execute a script in user TMP directory to load native libs per platform.
By setting permissions of 755 (rwx,rx,rx) to jspawnhelper in jre/lib/jspawnhelper when the package is installed the issue is solved.
In the RPM packager this is done correctly and explicitely already, so needs to be fixed for the DEB packager.
Please tell us about your environment:
The text was updated successfully, but these errors were encountered: