This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Fresh Fedora Core 4, NetBeans 4.1 and Profiler Milestone 8 (v3) installation. I'm getting following error message everytime I start NetBeans: Failed to initialize the Profiler engine: Problem with a required JFluid installation directory or file /opt/netbeans-4.1/profiler1/lib/deployed/jdk142/linux/libclient.so Original message: Could not load a the 'client' native library. Original exception: java.lang.UnsatisfiedLinkError: /opt/netbeans-4.1/profiler1/lib/deployed/jdk142/linux/libclient.so: /opt/netbeans-4.1/profiler1/lib/deployed/jdk142/linux/libclient.so: cannot restore segment prot after reloc: Permission denied, message = /opt/netbeans-4.1/profiler1/lib/deployed/jdk142/linux/libclient.so: /opt/netbeans-4.1/profiler1/lib/deployed/jdk142/linux/libclient.so: cannot restore segment prot after reloc: Permission denied
Created attachment 24079 [details] Exception from messages.log
The reason of this error is that SELinux is enabled and preventing the Profiler (shared) native library to be loaded. There are two possible workarounds: 1) change default security context for Profiler native libraries by calling chcon -t texrel_shlib_t /opt/netbeans-4.1/profiler1/lib/deployed/jdk142/linux/*.so (recommended) 2) disable SELinux by setting SELINUX=disabled in /etc/sysconfig/selinux config file (not recommended)
Workaround #1 has to be applied also on native libraries in /opt/netbeans- 4.1/profiler1/lib/deployed/jdk15/linux/ when using JDK 5.0 or 6.0 for profiling.
Cannot be fixed, this should be documented in FAQs
does workaround #1 work? is this specific to SELinux? are there other security enhanced configurations/installations that could cause this?
Both workarounds are tested to work, however the #2 completely disables enhanced security and thus is not recommended (but maybe could be noted). The "cannot restore segment prot after reloc: Permission denied" message is related only to SELinux, no other configurations are known to cause this.
*** Issue 65060 has been marked as a duplicate of this issue. ***
This issue can be fixed.
Fixed in trunk.
fix merged to release55 branch
Verified.