Bug 1584636
Summary: | abrt-cli list failed due to cannot connect system dbus: Error calling StartServiceByName | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | xhe <xhe> |
Component: | abrt | Assignee: | abrt <abrt-devel-list> |
Status: | CLOSED DUPLICATE | QA Contact: | BaseOS QE - Apps <qe-baseos-apps> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 7.6 | CC: | jkrysl, mhoyer, mkutlak |
Target Milestone: | rc | Keywords: | Regression |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-07-03 12:04:34 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
xhe@redhat.com
2018-05-31 10:57:25 UTC
RHEL-7.5: # uname -r 3.10.0-862.el7.x86_64 # abrt-cli list The Autoreporting feature is disabled. Please consider enabling it by issuing 'abrt-auto-reporting enabled' as a user with root privileges RHEL-7.6: # uname -r 3.10.0-915.el7.x86_64 # abrt-cli list Can't connect to system DBus: Error calling StartServiceByName for org.freedesktop.problems: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process org.freedesktop.problems received signal 9 So it is a regression, setting accordingly. But I tried updating abrt and abrt-cli on RHEL-7.5 to the ones on RHEL-7.6 and the result is the same (work on 7.5, fails on 7.6), so probably not an abrt regression. Not sure what cased it though, so leaving it to abrt. Please investigate and change component if needed. versions tested on RHEL 7.5 / 7.6: abrt-2.1.11-51.el7 abrt-cli-2.1.11-51.el7 Note: 'abrt-auto-reporting enabled' results in the same, just without the warning on 7.5. Could be a dup of bz#1583080 I can confirm that this issue should be fixed with selinux-policy-3.13.1-205.el7. *** This bug has been marked as a duplicate of bug 1583080 *** |