Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
"i3-msg restart" yields error code 1 even on successful restart #3565
I'm submitting a…
[x] Bug [ ] Feature Request [ ] Documentation Request [ ] Other (Please describe in detail)
Restarting i3wm in place with
Yielding the right error code allows me to run commands in a systemd unit file and script certain behavior with i3wm. Currently, whenever my systemd service restarts, it fails because the error code yields
This also makes it difficult for me to automate the installation of my systemd unit file with Ansible, because when the systemd service returns a failure, the running Ansible playbook halts.
This happens any time I call the command after logging into i3wm from gdm.
i3 version: 4.15 (2018-03-10)
- Logfile URL: https://logs.i3wm.org/logs/5730225442783232.bz2 - Linux Distribution & Version: Fedora 28 - Are you using a compositor (e.g., xcompmgr or compton): no
From what I can tell,
referenced this issue
Dec 23, 2018
Just a quick update, the problem seems to be specifically caused by the IPC clients getting freed before a shutdown or restart.
I think the fix would be to make the connection persist across restarts (possibly needed for #3570, too). I've been brainstorming a little on how to implement that, but I'll have more time once the holidays are over.