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.
Bug 1650062 - dbus: Rejected send message after update dbus
Summary: dbus: Rejected send message after update dbus
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: abrt
Version: 7.5
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: ekulik
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
Depends On:
Blocks: 1553558
TreeView+ depends on / blocked
 
Reported: 2018-11-15 09:38 UTC by masanari iida
Modified: 2023-12-15 16:13 UTC (History)
7 users (show)

Fixed In Version: 2.1.11-39.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-21 11:01:09 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description masanari iida 2018-11-15 09:38:54 UTC 
Description of problem:
Experience following messages after update dbus RPM from RHEL7.5.

Detail
A customer installed RHEL7.2 some times ago.
Recently, the customer update dbus and dbus-libs (and its dependency) from RHEL7.5.
After the update, the customer start to see following messages every time after
ssh login to the system, as well as su on the system.
This symptom can be reproduced if you follow "setep to reproduce".

Nov 14 21:00:38 localhost dbus[864]: [system] Rejected send message, 
1 matched rules; type="method_call", sender=":1.18" 
(uid=0 pid=8794 comm="/usr/sbin/abrt-dbus -t133 ") 
interface="org.freedesktop.DBus.Properties" member="GetAll" 
error name="(unset)" requested_reply="0" destination="org.freedesktop.DBus" (bus)

Root cause.
The dbus RPM on RHEL7.2 was dbus-1.6.12.
The dbus RPM on RHEL7.5 was rebased to dbus-1.10.24.
It seemed abrt-dbus RPM from RHEL7.2 depends on abrt from RHEL7.2.
So if one update the dbus and dbus-libs from RHEL7.5 dvd, 
the one also need to update abrt-dbus as well.

Steps to Reproduce:
1. Install RHEL7.2 (GNOME environment).
2. Install libvirt from RHEL7.2 DVD. (dbus and dbus-libs are installed, too.)
3. Make sure you don't see error messages when you login or su on the system.
4. Update libvirt RPM from RHEL7.5 DVD. (dbus and dbus-libs are also updated)
5. Reboot the OS
6. ssh login to the system 
Expected result:   no error message
Actual result:     "Rejected send message"

7. su on the system.
Expected result:   no error message
Actual result:     "Rejected send message"

8. Update abrt-dbus and abrt RPMS.
9. Reboot the system
10. SSH login to the system 
Expected result:   no error message
Actual result:  no error message

11. su on the system
Expected result:   no error message
Actual result:  no error message

How Reproducible
100%

As you see the "steps to reproduce",  the symptom started when dbus (RHEL7.5) and abrt-dbus(RHEL7.2) are used.
It is happen because of version mismatch.
One can create such a system, if they are not careful.

My suggestion is, if abrt-dbus needs specific version of of dbus,
then dependency setting should be set in spec file.
If it is difficult to set dependency, I think it is time to create a KB to explain
how to fix it.
Comment 2 Shane Seymour 2018-11-22 05:00:06 UTC 
I would point out this:

"Red Hat recommends that application developers adopt the following principles in order to improve binary compatibility:
...
Package applications using the RPM mechanism. RPM provides a software-packaging mechanism that includes detailed specification of application dependencies. When creating RPMs, the following should be kept in mind:
...
(b) Explicitly state all required runtime and build dependencies using the appropriate RPM syntax."

From:

https://access.redhat.com/articles/rhel-abi-compatibility
Comment 3 Shane Seymour 2018-11-22 05:04:32 UTC 
If the issue is introduced by dbus-libs (or dbus-glib but that one isn't mentioned) they are listed at level 2 compatibility which is defined as:

"Compatibility level 2: APIs and ABIs are stable within one major release (RHEL 7)"
Comment 4 ekulik 2019-03-04 12:20:17 UTC 
(In reply to Shane Seymour from comment #3)
> If the issue is introduced by dbus-libs (or dbus-glib but that one isn't
> mentioned) they are listed at level 2 compatibility which is defined as:
> 
> "Compatibility level 2: APIs and ABIs are stable within one major release
> (RHEL 7)"

dbus-glib is no longer used in ABRT.

I suspect this one is fixed by https://bugzilla.gnome.org/show_bug.cgi?id=755421, which correlates with the versions of GLib in 7.2 (2.42.2) and 7.5 (2.54.2). Needs to be confirmed, but this is definitely not a dependency issue.
Note You need to log in before you can comment on or make changes to this bug.