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

delete qubes/systemd/corridor.target.d/qubes-service.conf #27

Closed
wants to merge 1 commit into from

Conversation

adrelanos
Copy link
Contributor

Currently Whonix repository contains a corridor package that works for Qubes-Whonix, but not out of the box for Debian. Having distinct packages for Qubes Debian templates and plain Debian would be a shame.

Therefore, please delete qubes/systemd/corridor.target.d/qubes-service.conf. We could re-add it in the more appropriate place in qubes-core-agent.

Related:

@adrelanos
Copy link
Contributor Author

ce0b65c did not fix it.

For testing purposes I deleted /var/run/qubes-service. Result:

ConditionPathExists=/var/run/qubes-service/corridor was not met

@rustybird
Copy link
Owner

Hmm, if anything, shouldn't systemctl status say "none of the trigger conditions were met"? But the message above looks like you might have a stale file lying around somewhere, e.g. in /usr/local/lib/systemd/system, or another of the directories listed by pkg-config --variable systemdsystemunitpath systemd.

@adrelanos
Copy link
Contributor Author

My mistake. I thought ce0b65c was included in https://github.com/rustybird/corridor/releases/tag/v0.10.0 but it is not.

Anyhow. I updated the package in Whonix repository and this very bug should be fixed. //cc @HulaHoopWhonix

@adrelanos
Copy link
Contributor Author

Yes. Just now tested. Works for me.

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

Successfully merging this pull request may close these issues.

None yet

2 participants