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

v239.1: loginctl refuses to work without a user bus #93

Closed
Yamakuzure opened this Issue Nov 9, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@Yamakuzure
Copy link
Collaborator

Yamakuzure commented Nov 9, 2018

After enabling user buses, see issue #87, loginctl does no longer work if only a system bus is available.

This is caused by hitting superfluous checks whether systemd has been used to boot the machine before allowing to connect to the system bus.

Before that, connecting to a user bus was re-routing to connect to the system bus, which bypassed these checks.

Thanks a lot to Stefan for finding this out, and mailing me a fix.

Yamakuzure added a commit that referenced this issue Nov 9, 2018

bus-util: Remove invalid check against systemd providing PID 1. (#93)
This check always returns error -EHOSTDOWN, because sd_booted()
always returns 0. This will fix loginctl execution error, returned
from the login/loginctl.c:main().

Before enabling user buses, this check was bypassed by re-routing
attempts to connect to user buses to the system bus.

Bug: #87
Bug: #93
Closes: #93
Sigend-off-by: Sven Eden <sven.eden@prydeworx.com>

@Yamakuzure Yamakuzure closed this in fd02598 Nov 9, 2018

@Yamakuzure Yamakuzure self-assigned this Nov 9, 2018

@Yamakuzure Yamakuzure added the bug label Nov 9, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment