Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
blugon.service: Main process exited, code=exited, status=11/n/a
See original GitHub issueI noticed that the blugon service wasn’t running after reboot. journalctl showed
-- Reboot --
Jan 16 18:02:03 archlinux systemd[1029]: Started Blue Light Filter.
Jan 16 18:02:04 archlinux systemd[1029]: blugon.service: Main process exited, code=exited, status=11/n/a
Jan 16 18:02:04 archlinux systemd[1029]: blugon.service: Failed with result 'exit-code'.
Jan 16 18:02:04 archlinux systemd[1029]: blugon.service: Service RestartSec=100ms expired, scheduling restart.
Jan 16 18:02:04 archlinux systemd[1029]: blugon.service: Scheduled restart job, restart counter is at 1.
Jan 16 18:02:04 archlinux systemd[1029]: Stopped Blue Light Filter.
The following 4 tries failed the same way.
I installed blugon using the AUR, and I’m using X, lightdm and awesomeWM. Starting the service manually works fine.
Issue Analytics
- State:
- Created 5 years ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
Crash: Main process exited, code=killed, status=11/SEGV ...
Bug report summary Systemd crashes with Main process exited, code=killed, status=11/SEGV OS / Environment Linux node2 5.4.78-2 #1 SMP PVE ...
Read more >systemctl - service exit codes and status information explanation
The question is about the part in bold: the main process exit code and status information. Is there a list of all the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I had an even better idea just now. Since the start up delay will be different for everyone you can now set the restart interval in the general config. Just change
to wait 5 seconds.
I’m sorry for breaking the old fix again tho.
Thanks so much. I appreciate the
.xinitrcworkaround. I’ll try that.