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.

Details:
https://bugs.freedesktop.org/show_bug.cgi?id=95263

Can you please check that we don't have the same bug in rhel7 version of dbus daemon?

RHEL 7 has dbus-1.6.12-13.el7, which does not have the patch from commit e0c9d31be3b9eea9ee2a3a255bc2cf9aad713642 applied.

Ok, thanks for checking!

(In reply to Lukáš Nykrýn from comment #2)
> Ok, thanks for checking!

So ,will the lastest RHEL use this patch:https://bugs.freedesktop.org/show_bug.cgi?id=95263 , I find the latest version of dbus https://dbus.freedesktop.org/releases/dbus/ dbus-1.11.10.tar.gz didn't use this patch either?

But if dbus don't use this patch ,how to slove this problem:


The original issue is tracked here in systemd upstream:

https://github.com/systemd/systemd/issues/1961

And I figure this is actually the same issue:

https://github.com/systemd/systemd/issues/2925