NoMachine error crash - suggested run 'setenforce 0'

kd4e

Installed NoMachine and it threw this error:

Error in NoMachine
type:crash
signal 11 (SIGSEGV), CODE 1 (SEGV_MAPERR), fault addr 0x000000000000000

Tried adb shell su 0 setenforce 0 in terminal - "adb: inaccessible or not found".

I'm suspicious that this is referred to as "permissive mode". Does it violate the integrity of grapheneos?

If not a huge problem - how do I correctly set setenforce 0 please?

Thanks.

kd4e

kd4e OK, just realized that "adb" is android-specific ... so, is NoMachine impossible on a grapheneos phone, please?

tac

kd4e I don't know why you're jumping to the conclusion that for some remote desktop client to work instead of crashing due to segmentation violation, you'd have to entirely disable SELinux. It'd be an exceedingly bad idea. This is a security feature not just on GrapheneOS but even on standard Android: https://source.android.com/docs/security/features/selinux

You can try enabling Exploit protection compatibility mode for this app (tap and hold the icon, then choose App info). Maybe that's why it crashes. See here: https://grapheneos.org/usage#bugs-uncovered-by-security-features

kd4e

tac When I tried a Search - the only responses I found - recommended that.

That was the fix.

Thanks1

TBacker

kd4e Is it working okay for you?
I figured out the compatibility setting, but every time I start NoMachine it forces me to go through the welcome screens again. Toggling "Don't show this dialog anymore" is not saved / persisted.