Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
notmike-5 opened this issue May 20, 2017 · 3 comments
Labels

Comments

@notmike-5
Copy link

notmike-5 commented May 20, 2017

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

@jamesan
Copy link
Owner

jamesan commented Feb 21, 2018

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.

@notmike-5
Copy link
Author

notmike-5 commented Feb 21, 2018

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.

@bphd
Copy link

bphd commented Apr 26, 2020

same

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants