RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). 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 rh-issues@redhat.com 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 "https://issues.redhat.com/browse/RHEL-XXXX", 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.

Description of problem: Running "systemctl --user status" gives the error "Failed to get D-Bus connection: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11"

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

systemd-208-11.el7_0.6.x86_64

How reproducible:

Always reproduces.

Steps to Reproduce:
1. Run "systemctl --user status" as a regular user

Actual results:

The command fails with the error "Failed to get D-Bus connection: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11".

Expected results:

The command shows the status of the systemd user manager's services.

Additional info:

Searching the web turns up posts that indicate the issue might be related to a bug in the D-Bus package that causes the DBUS_SESSION_BUS_ADDRESS environment variable to not be set.

Nope, this is becuase we are not starting user systemd in rhel7 by default.

(In reply to Lukáš Nykrýn from comment #1)
> Nope, this is becuase we are not starting user systemd in rhel7 by default.

How do we enable user systemd in rhel7 or what was the rationale to disable it?
I apologise if I missed the info somewhere. It is detailed in #1019738 but I dont have access to that bug.

Many thanks for your help.

OK I found some hint as to why `systemd --user` is removed in rhel7 in the presentation "Lukáš Nykrýn, Michal Sekletar: systemd in RHEL - upstream vs conservative enterprise distribution" from systemd-conf: https://youtu.be/kUWvSXEHMhU?t=3m45s
Basically not "enterprise ready".

> Basically not "enterprise ready".
Exactly. We are not even sure that --user will stay in upstream as is in the future.