Open
Conversation
While most distros have migrated over to dbus-broker, we still provide dbus-daemon, and we do not enable user sessions, so each user login does not have any dbus that can be used to communicate with the user session's systemd manager. This leads to frequent error messages while upgrading packages, and at other times, similar to: Failed to connect to bus: No medium found Reload daemon failed: Transport endpoint is not connected Those errors also mean that while the systemd system manager (pid1) can be reloaded or reexeced, systemd user managers will not be reexeced on a package upgrade, nor can any other package that provides user session services cause their user services to reload/reexec on upgrade. This may leave user processes running old code after some package updates. Note that the user can still communicate with the user session systemd manager, via systemctl, because it will use the private systemd bus. However, the root user (including scripts run during package updates) cannot connect to any user's private systemd bus and so must use the public user dbus, which is not provided by our dbus package currently. This changes the dbus build to include support for user sessions.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
While most distros have migrated over to dbus-broker, we still provide dbus-daemon, and we do not enable user sessions, so each user login does not have any dbus that can be used to communicate with the user session's systemd manager. This leads to frequent error messages while upgrading packages, and at other times, similar to:
Failed to connect to bus: No medium found
Reload daemon failed: Transport endpoint is not connected
Those errors also mean that while the systemd system manager (pid1) can be reloaded or reexeced, systemd user managers will not be reexeced on a package upgrade, nor can any other package that provides user session services cause their user services to reload/reexec on upgrade. This may leave user processes running old code after some package updates.
Note that the user can still communicate with the user session systemd manager, via systemctl, because it will use the private systemd bus. However, the root user (including scripts run during package updates) cannot connect to any user's private systemd bus and so must use the public user dbus, which is not provided by our dbus package currently.
This changes the dbus build to include support for user sessions.
Merge Checklist
All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)
*-staticsubpackages, etc.) have had theirReleasetag incremented../cgmanifest.json,./toolkit/scripts/toolchain/cgmanifest.json,.github/workflows/cgmanifest.json)./LICENSES-AND-NOTICES/SPECS/data/licenses.json,./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md,./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)*.signatures.jsonfilessudo make go-tidy-allandsudo make go-test-coveragepassSummary
enable user dbus support
Change Log
enables user dbus support
Does this affect the toolchain?
n
Associated issues
Links to CVEs
Test Methodology