Forum / NoMachine for Linux / Cannot enable executable stack as shared object requires: Permission denied
- This topic has 4 replies, 2 voices, and was last updated 1 month ago by
vetrov.
-
AuthorPosts
-
September 23, 2025 at 11:33 #54422
vetrovParticipant/usr/NX/bin/nxplayer.bin: error while loading shared libraries: libnxcim.so: cannot enable executable stack as shared object requires: Permission denied
Startup error
Debian 12
nomachine_9.1.24_6_amd64.deb
September 24, 2025 at 02:16 #54435
vetrovParticipantThe error “libnxcim.so: cannot enable executable stack as shared object requires: Permission denied” occurs when software (software) attempts to allow execution of code located in the software stack. By default, execution of such code is prohibited because it may pose a security risk.
Causes
The error can be caused by:
Enabling code execution permission control in the software stack in the operating system. Attempts to allow such execution are logged in the audit log, and the error occurs if the software attempts to set the execution permission flag on a memory area (for example, by executing the mprotect() system call).
An error in the software that sets the library as requiring an executable stack. This may be due to an error in the software version or an error in the build.
wiki.astralinux.ru
sourceforge.net
Solution
To resolve the error, it is recommended to:
If possible, avoid using the software that generates the error as it may be potentially unsafe. Contact the software developers to improve the software and eliminate potentially unsafe actions.
Disable the control of code execution permission in the software stack in the operating system if necessary, but the software generates an error. To do this, follow these steps:
Add the kernel parameter parsec.execstack with a value of 1 to the parameter value string.
September 24, 2025 at 02:35 #54436
vetrovParticipantAstra Linux 1.8.3.8 on Debian 12 (Bookworm)
September 25, 2025 at 16:56 #54459
BritgirlKeymasterHi,
thanks for reporting. Looking at the output you pasted, that parsec.execstack option is specific to Astra Linux kernel. When it’s set to 1, the system prevents stack execution, so the only temporary workaround offered consists in removing the flag. In the meantime, we’ll investigate what needs to be fixed in our library.
September 26, 2025 at 01:08 #54465
vetrovParticipantThank you, I prefer your program to other solutions, and this is not the first time that support has solved my problems in a timely manner. I will continue to wait for a solution, and I thank you again.
-
AuthorPosts
You must be logged in to reply to this topic. Please login here.
