Bug 1651780 - Unable to launch setroubleshoot
Summary: Unable to launch setroubleshoot
Keywords:
Status: CLOSED DUPLICATE of bug 1651235
Alias: None
Product: Fedora
Classification: Fedora
Component: setroubleshoot
Version: 29
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Daniel Walsh
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-20 19:44 UTC by Mike
Modified: 2018-11-20 20:30 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-20 20:30:24 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Log of "messages" during attempted launching of setroubleshoot (11.15 KB, text/plain)
2018-11-20 19:44 UTC, Mike
no flags Details

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 ***


Note You need to log in before you can comment on or make changes to this bug.