Description of problem: SELinux Trouble shooter will not start and show its window. Version-Release number of selected component (if applicable): 3.3.18-1.fc29 How reproducible: Click the SELinux troubleshooter icon, or use "sealert -b" at the commend line. Steps to Reproduce: 1. Install setroubleshoot 2. Attempt to run setroubleshoot from either the icon or from the command line. 3. Actual results: SELinux Troubleshooter never shows its window though the menu header does appear in the top bar briefly when the attempted start is from the icon click. When the attempt is made from the command line I get the following: $ sealert -b /usr/bin/sealert:32: DeprecationWarning: Importing dbus.glib to use the GLib main loop with dbus-python is deprecated. Instead, use this sequence: from dbus.mainloop.glib import DBusGMainLoop DBusGMainLoop(set_as_default=True) import dbus.glib There were no further messages and the trouble shooter did not start. The trouble shooter menu header did not appear in the top bar. (echo $?) produced 0 Expected results: SELinux Troubleshooter should start and show its window. Additional info: This happened with F29 Workstation Live 10/17 drop. This was a clean install on bare metal (Lenovo M58p with E8400 processor) from a DVD. The ISO check-sum was good and the media test ran and passed. The installation ran without errors and the system restarted after the install without errors or problems of any kind. SELinux Troubleshooter was the only additional software installed after the install from the DVD and it was installed with (sudo dnf install setroubleshoot) at the command line. The install ran without error. I tried doing a reintall from the command line (sudo dnf reinstall setroubleshoot) and the bug persisted. This bug was also present in the 10/13 drop, but I did not test this in drops prior to 10/13; so I don't know how far back it goes.
Version-Release number of selected component (if applicable): 3.3.18-1.fc29 This bug persists in drop 10/22.
Version-Release number of selected component (if applicable): 3.3.18-1.fc29 This bug persists in drop 10/25 (RC 1.2).
Version-Release number of selected component (if applicable): 3.3.18-1.fc29 This bug persists in the fully updated released version of F29.
Thank you for reporting the issue. I tried to reproduce it on the released version of F29 and sealert started as expected (albeit with a delay of several seconds). Could you please try to reproduce the issue after switching "sealert_log" and "setroubleshootd_log" levels in /etc/setroubleshoot/setroubleshoot.conf to "DEBUG"? The output of "journalctl -t setroubleshoot" could give us some clues. Also, does the issue persist after reboot?
Created attachment 1505269 [details] setroubleshoot.conf
Created attachment 1505270 [details] journalctl -t setroubleshoot.txt
I set the /etc/setroubleshoot/setroubleshoot.conf as you asked. I have attached a copy of the file. I did a restart and then tried to start SELinux troubleshooter. The result was SELinux Troubleshooter never shows its window though the menu header does appear in the top bar briefly. This is the same result I got when I wrote the bug report. I have attached a copy of the journalctl results. Yes, The bug happens even after a reboot. The bug occurs on all attempts to start the troubleshooter.
Please try running "sealert -b" while you have "sudo journalctl -f" running in a separate terminal. Does any new message appear?
Created attachment 1505343 [details] SEAlertJournal
Created attachment 1505350 [details] SEAlert
I have attached two files. One is the journal that ran on one terminal. The other is trying to run the SEAlert in another terminal while the journal was running in the first terminal.
This is a dbus issue. Please see https://bugzilla.redhat.com/show_bug.cgi?id=1641456 It should be fixed by reinstalling dbus packages.
I reinstalled the dbus-common and dbus-daemon and did a restart. After that the SELinux Alert Browser started as it should. Since this bug is present in the released F29 I think I will just add these reinstalls to the script I use to set up PCs.
*** This bug has been marked as a duplicate of bug 1641456 ***