Bug 1651780

Summary: Unable to launch setroubleshoot
Product: [Fedora] Fedora Reporter: Mike <MikeDawg>
Component: setroubleshootAssignee: Daniel Walsh <dwalsh>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 29CC: dwalsh, mgrepl, plautrba, vmojzis
Target Milestone: ---   
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-11-20 20:30:24 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:
Attachments:
Description Flags
Log of "messages" during attempted launching of setroubleshoot none

Description Mike 2018-11-20 19:44:37 UTC
Created attachment 1507457 [details]
Log of "messages" during attempted launching of setroubleshoot

Description of problem:

Unable to launch setroubleshoot.


Version-Release number of selected component (if applicable):

setroubleshoot-plugins-3.3.9-6.fc29.noarch
setroubleshoot-server-3.3.18-1.fc29.x86_64
setroubleshoot-3.3.18-1.fc29.x86_64

How reproducible:

Everytime, still unable to launch setroubleshoot

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Mike 2018-11-20 20:25:26 UTC
(In reply to Mike from comment #0)
> Created attachment 1507457 [details]
> Log of "messages" during attempted launching of setroubleshoot
> 
> Description of problem:
> 
> Unable to launch setroubleshoot.
> 
> 
> Version-Release number of selected component (if applicable):
> 
> setroubleshoot-plugins-3.3.9-6.fc29.noarch
> setroubleshoot-server-3.3.18-1.fc29.x86_64
> setroubleshoot-3.3.18-1.fc29.x86_64
> 
> How reproducible:
> 
> Everytime, still unable to launch setroubleshoot
> 
> Steps to Reproduce:
> 1.
> 2.
> 3.
> 
> Actual results:
> 
> 
> Expected results:
> 
> 
> Additional info:

I should have also noted, unable to launch sealert and setroubleshootd.

Comment 2 Mike 2018-11-20 20:30:24 UTC
Found, in a different bugzilla report, that the fix was to reinstall dbus-* and try again.

I did that, with success.

$  sudo dnf reinstall 'dbus-*' -y

appeared to fix this issue.

*** This bug has been marked as a duplicate of bug 1651235 ***