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.

Created attachment 716426 [details]
Auth dialog that comes up

Description of problem:

Filing against systemd, please re-route if inappropriate.

I installed RHEL7 alpha3 from the iso in a KVM VM.  In one invocation of the VM, the system wouldn't power off, asking for root passwd as shown in the screenshot.  The session manager thinks there are other users logged in, whereas I have not created any other user accounts nor have I logged in multiple times.

If try to power off after a while, it succeeds.  Maybe this gives a clue.

'w' only shows the current user 'amit' logged in (twice, once the gdm-session-worker and one for gnome-terminal).

What sessions does "loginctl" show?
Try also "loginctl session-status <SESSION>".

This doesn't happen everytime, btw.  And that makes gathering details for this bug annoying: when it doesn't reproduce, 'power off' just switches the vm off, and I once again have to power on the vm and hope the bug would show up.

However, this bug appeared on an F18 desktop as well, loginctl only showed one session.  I couldn't grab the  session-status list on that box.  Would it be relevant to this bug if I pasted data from the other F18 box (where it appears to reproduce more often)?

Is this bug still an issue and if so can you please attach output from the mentioned commands? It will be useful even if the output is from fedora.

The Fedora bug doesn't happen anymore.  Best to close this now.  If it recurs, I'll update here.