The "syndaemon" init-script fails with message "Can't open display. " when being automatically started because it requires an X server with an exported "DISPLAY" env. variable. Another problem is that the stop() in the init-script uses a file "/var/run/syndaemon.pid" to terminate it, but syndaemon never creates the file. Reproducible: Always Steps to Reproduce: 1. rc-update add syndaemon default 2. reboot computer 3. whatch the error message since syndaemon is started before the X-server Actual Results: The init-script generates the following error message: Can't open display. and does not start. Expected Results: Syndaemon should have started after the X server and not display any error messages
This is a duplicate of #37767. Please mark as such. I also pointed out a solution for this bug.
Although the symptoms are not exactly the same, the resolution is and this bug is discussed in 37767. Marking as dupe. *** This bug has been marked as a duplicate of 37767 ***
