This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira ( If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1795555 - Provide a way for privileged users to interact with systemd user instances
Summary: Provide a way for privileged users to interact with systemd user instances
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: systemd
Version: 8.1
Hardware: All
OS: Linux
Target Milestone: rc
: 8.0
Assignee: Jacek Migacz
QA Contact: Frantisek Sumsal
: 1907903 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2020-01-28 10:12 UTC by Renaud Métrich
Modified: 2023-09-21 10:55 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2023-09-21 10:55:01 UTC
Type: Story
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github redhat-plumbers systemd-rhel8 pull 258 0 None Draft (#1795555) Provide a way for privileged users to interact with systemd user instances 2023-05-16 08:05:47 UTC
Github systemd systemd issues 14580 0 None closed systemctl -M VERB should work 2021-01-26 08:57:05 UTC
Github systemd systemd pull 17967 0 None closed add support for "systemctl --user" for connecting to user bus of user "foobar" 2021-07-26 09:30:48 UTC
Red Hat Issue Tracker   RHEL-5828 0 None Migrated None 2023-09-21 10:51:48 UTC
Red Hat Knowledge Base (Solution) 4661741 0 None None None 2020-01-28 10:14:51 UTC

Description Renaud Métrich 2020-01-28 10:12:48 UTC
Description of problem:

With RHEL8.x, users can have their own systemd instance, but there is no way for the root user or privileged users (e.g. in "wheel" group) to manage the systemd user instances at all.

So far, the only way is to use "sudo+XDG_RUNTIME_DIR" which is not a good solution: 

$ sudo -u user1 /bin/bash -c "export XDG_RUNTIME_DIR=/run/user/$(id -u user1); /usr/bin/systemctl --user list-units"

Version-Release number of selected component (if applicable):


How reproducible:


Additional info:

See also:

Comment 3 David Tardon 2021-01-04 12:57:14 UTC
*** Bug 1907903 has been marked as a duplicate of this bug. ***

Comment 11 David Tardon 2023-05-16 08:49:56 UTC
(In reply to Renaud Métrich from comment #0)
> $ sudo -u user1 /bin/bash -c "export XDG_RUNTIME_DIR=/run/user/$(id -u
> user1); /usr/bin/systemctl --user list-units"

This can be shortened a bit:

$ sudo -u user1 XDG_RUNTIME_DIR=/run/user/$(id -u user1) systemctl --user list-units

Comment 16 RHEL Program Management 2023-09-21 10:48:54 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 17 RHEL Program Management 2023-09-21 10:55:01 UTC
This BZ has been automatically migrated to the Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit for general account information.

Note You need to log in before you can comment on or make changes to this bug.