When systemd tries to kill nodm, nodm restarts itself instead

[mkaito]

I suppose systemd is trying to kill the wrong PID. Eventually, the kill operation times out and systemd hard-kills the process. This happens, for example, when trying to reboot or halt the computer.

Arch Linux, everything up to date.
Nodm version 0.12

Here's the systemd service file:

[Unit]
Description=nodm display manager

[Service]
EnvironmentFile=/etc/nodm.conf
ExecStart=/usr/bin/nodm

[Install]
WantedBy=multi-user.target

[ndchugn]

same with me, sometime i have to press on power button to turnoff the laptop

[sunweaver]

This should be solved by ede6a3f.

Feel free to reopen, if not.

[eugene2k]

Doesn't look like it is.

[PatrickNowak]

Not fixed for me either with version 0.13-1.3.

[mkaito]

As far as I can tell, not fixed.

[r-darwish]

@sunweaver can you please reopen the issue? It seems that it is still relevant

[sunweaver]

@r-darwish: Ack. Reopened. Patches are welcome!

[needs]

Could this line be what cause this issue? It seems like once the session lasted longer than NODM_MIN_SESSION_TIME, it shouldn't be restarted if it ends. Changing it to something like return E_SUCCESS; should do the trick.

Also, I tried and failed to get my build of nodm working on my computer to test this change. I don't want to submit a completely untested pull request.

[MikeMitterer]

I just found this old bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=531869
You think it's somehow related?

[felixsanz]

This is very annoying. Any idea whats going on? Anyone working on it? I think nodm is ignoring system run levels. It shouldn't restart itself when system is moving into restart/shutdown levels

[mkaito]

Actually, it's probably systemd killing the wrong PID. Quoting Félix Sanz (2017-08-02 22:22:30)

…

This is very annoying. Any idea whats going on? Anyone working on it? I think nodm is ignoring system run levels. It shouldn't restart itself when system is moving into restart/shutdown levels -- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: #5 (comment)

[rtandy]

This sounds pretty similar to my Debian bug report: https://bugs.debian.org/785592