In this case, the daemon remains running when the integration service is being disabled. systemctl status shows the daemon running and active, but the daemon is not working actually. Re-enabling the service does not make the daemon to work properly. Manually starting a new instance of the daemon results in the daemon actually working, but with two different PIDs in the process list.
To sum it up, yes, it has the second issue as well.
I have tested 4.4.0-2.16 from here: https:/ /launchpad. net/ubuntu/ +source/ linux/4. 4.0-2.16/ +build/ 8908724
In this case, the daemon remains running when the integration service is being disabled. systemctl status shows the daemon running and active, but the daemon is not working actually. Re-enabling the service does not make the daemon to work properly. Manually starting a new instance of the daemon results in the daemon actually working, but with two different PIDs in the process list.
To sum it up, yes, it has the second issue as well.