@parentibule have you intentionally enabled nvOC to run as a system service instead of as gnome profile launch script or you don't know what I'm talking about? In the first case, open an issue for that on github. In the second one, have you ever run the nvOC install-service command? You don't have to if you do not intend to switch to service mode, but if you have ever done this in the past, even accidentally, then check PR note here
#149edit:@parentibule I think there is a bug somewhere, we ill discuss it in github. For anyone else having problems with nvOC as a service the above general guideline is valid.
I try nvOC install-service because I have a lbocking problem with reboot:
m1@m1-desktop:~$/home/m1_2.1/nvOC reboot
Warning: The host will reboot in 10 seconds, ctrl-c to cancel...
Failed to start reboot.target: Connection timed out
See system logs and 'systemctl status reboot.target' for details.
And I thought installing (and stopping) nvOC as service could resolve it.
edit: note that I try all the known ways to (ssh) reboot linux and none works. I didn't even know it was possible!