FS#51033 - [nodm] Automatically restarts when stopped by systemd

Attached to Project: Community Packages
Opened by Michishige Kaito (mkaito) - Thursday, 29 September 2016, 10:42 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Tuesday, 08 August 2017, 21:44 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sven-Hendrik Haase (Svenstaro)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

When systemd tries to stop nodm, for example during system shutdown, nodm will restart and sit there until systemd times out and kills it.

On one hand, it's quite confusing. When issuing the shutdown command, my window manager restarts and sits there for a few minutes. I had no idea what was happening.

On the other, it adds an unnecessary delay during shutdown.

Additional info:
nodm 0.12-1

Steps to reproduce:

* Install nodm
* Start the nodm service and arrive at desktop
* Ask systemd to stop nodm
* nodm will restart instead
This task depends upon

Closed by  Sven-Hendrik Haase (Svenstaro)
Tuesday, 08 August 2017, 21:44 GMT
Reason for closing:  Upstream
Comment by Sven-Hendrik Haase (Svenstaro) - Sunday, 30 October 2016, 03:35 GMT
Can you report this against upstream and link the issue here?
Comment by Michishige Kaito (mkaito) - Wednesday, 02 November 2016, 20:10 GMT
Did so. See bug report here: https://github.com/spanezz/nodm/issues/5
Comment by Chad Granum (exodist) - Saturday, 01 April 2017, 02:34 GMT
Bump, as of March 31, 2017 I am seeing this issue as well, has been bothering me for months, but only now found an existing bug report.
Comment by Kasi (popsch) - Monday, 26 June 2017, 17:21 GMT
Bump. As of June 26, 2017, this is still an issue. It's a problem, because 'reboot' in the terminal doesn't work, because nodm restarts and the reboot hangs for 1.5 min to wait for nodm before killing it.
Comment by Sven-Hendrik Haase (Svenstaro) - Tuesday, 08 August 2017, 21:44 GMT
Well I'm going to close this as there still is no patch that I could use and it does indeed appear to be an upstream problem.

Loading...