auto-xflux icon indicating copy to clipboard operation
auto-xflux copied to clipboard

Job for auto-xflux.service failed because the control process exited with error code.

Open notmike-5 opened this issue 8 years ago • 3 comments

For some reason the auto-xflux.service unit is not starting. When I run sudo systemctl start auto-xflux I receive:

Job for auto-xflux.service failed because the control process exited with error code. See "systemctl status auto-xflux.service" and "journalctl -xe" for details.

Here is the status:

$ systemctl status auto-xflux.service ● auto-xflux.service - Inputless xflux daemon that geocodes based on your external IP address Loaded: loaded (/usr/lib/systemd/user/auto-xflux.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Sat 2017-05-20 15:56:56 EDT; 43s ago Process: 15065 ExecStart=/usr/bin/auto-xflux (code=exited, status=255)

May 20 15:56:56 nYx systemd[1]: auto-xflux.service: Control process exited, code=exited status=255 May 20 15:56:56 nYx systemd[1]: Failed to start Inputless xflux daemon that geocodes based on your external IP address. May 20 15:56:56 nYx systemd[1]: auto-xflux.service: Unit entered failed state. May 20 15:56:56 nYx systemd[1]: auto-xflux.service: Failed with result 'exit-code'. May 20 15:56:56 nYx systemd[1]: auto-xflux.service: Service hold-off time over, scheduling restart. May 20 15:56:56 nYx systemd[1]: Stopped Inputless xflux daemon that geocodes based on your external IP address. May 20 15:56:56 nYx systemd[1]: auto-xflux.service: Start request repeated too quickly. May 20 15:56:56 nYx systemd[1]: Failed to start Inputless xflux daemon that geocodes based on your external IP address. May 20 15:56:56 nYx systemd[1]: auto-xflux.service: Unit entered failed state. May 20 15:56:56 nYx systemd[1]: auto-xflux.service: Failed with result 'exit-code'.

And here is what I have for the unit file:

$ cat auto-xflux.service [Unit] Description=Inputless xflux daemon that geocodes based on your external IP address After=network.target display-manager.service

[Service] Type=forking ExecStart=/usr/bin/auto-xflux Restart=always Environment=DISPLAY=:0

[Install] WantedBy=graphical.target

notmike-5 avatar May 20 '17 20:05 notmike-5

The packaged service unit file doesn't have the Environment line that you've included. The environment should already have the DISPLAY defined in advance of starting this unit.

To differentiate issues related to systemd vs. (auto-)xflux itself, execute /usr/bin/auto-xflux on its own. Running that has helped me pinpoint issues while developing this little package.

jamesan avatar Feb 21 '18 05:02 jamesan

Thanks for getting back to me.

I ran auto-xflux by itself which revealved:

Sorry, we only support 8 and 10-bit displays right now.

I don't really know what it means, though.

notmike-5 avatar Feb 21 '18 06:02 notmike-5

same

bphd avatar Apr 26 '20 15:04 bphd