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 1531506 - dbus service needs to be restarted manually after update
Summary: dbus service needs to be restarted manually after update
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: dbus
Version: 7.5
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: rc
: ---
Assignee: David King
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-05 11:23 UTC by Dalibor Pospíšil
Modified: 2018-02-27 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-27 15:37:30 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Dalibor Pospíšil 2018-01-05 11:23:48 UTC 
Description of problem:
after update of dbus from dbus-1.6.12-17.el7 to dbus-1.10.24-3.el7, sepolicy gui tracebacks until the dbus service is restarted manually.

Version-Release number of selected component (if applicable):
dbus-1.10.24-3.el7

How reproducible:
100%

Steps to Reproduce:
1. run sepolicy gui
2.
3.

Actual results:
# sepolicy gui
/usr/lib64/python2.7/site-packages/sepolicy/gui.py:29: PyGIWarning: Gtk was imported without specifying a version first. Use gi.require_version('Gtk', '3.0') before import to ensure that the right version gets loaded.
  from gi.repository import Gtk
Traceback (most recent call last):
  File "/usr/bin/sepolicy", line 698, in <module>
    args.func(args)
  File "/usr/bin/sepolicy", line 324, in gui_run
    sepolicy.gui.SELinuxGui(args.domain, args.test)
  File "/usr/lib64/python2.7/site-packages/sepolicy/gui.py", line 110, in __init__
    self.dbus = SELinuxDBus()
  File "/usr/lib64/python2.7/site-packages/sepolicy/sedbus.py", line 12, in __init__
    self.dbus_object = self.bus.get_object("org.selinux", "/org/selinux/object")
  File "/usr/lib64/python2.7/site-packages/dbus/bus.py", line 241, in get_object
    follow_name_owner_changes=follow_name_owner_changes)
  File "/usr/lib64/python2.7/site-packages/dbus/proxies.py", line 248, in __init__
    self._named_service = conn.activate_name_owner(bus_name)
  File "/usr/lib64/python2.7/site-packages/dbus/bus.py", line 180, in activate_name_owner
    self.start_service_by_name(bus_name)
  File "/usr/lib64/python2.7/site-packages/dbus/bus.py", line 278, in start_service_by_name
    'su', (bus_name, flags)))
  File "/usr/lib64/python2.7/site-packages/dbus/connection.py", line 651, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute program /lib64/dbus-1/dbus-daemon-launch-helper: Success


Expected results:
no traceback
Comment 1 David King 2018-02-27 15:37:30 UTC 
Yes, this is the case. dbus is a low-level system service, and the whole system should be restarted after a dbus update. Restarting just the dbus service will cause problems, as large parts of systemd make extensive use of dbus (as just one example).
Note You need to log in before you can comment on or make changes to this bug.