I decided to try starting SELinux Trouble shooter from the command line
to see if I could get more information on why it will not start. and
this is what I got:
$ 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
Have a Great Day!
Pat (tablepc)
On 10/15/18 5:26 PM, pmkellly@xxxxxxxxxxxx wrote:
Geoff,
I did the (sudo dnf resinstall setroubleshoot). The dnf reinstall went
normally. Then I did a restart and when I tried to open the SELinux
Troubleshooter by clicking the icon, I got the same result. The menu
header came up temporarily in the top bar, but the window never opened.
Have a Great Day!
Pat (tablepc)
On 10/15/18 3:37 PM, Geoffrey Marr wrote:
Pat,
Hmm, I just tried to open my SELinux Troubleshooter and it opened the
window with no alerts present. Can you try reinstalling the program
and see
if that fixes the issue?
sudo dnf resinstall setroubleshoot
Geoff Marr
IRC: coremodule
On Mon, Oct 15, 2018 at 11:52 AM pmkellly@xxxxxxxxxxxx <
pmkellly@xxxxxxxxxxxx> wrote:
Good Day Everyone,
I've been testing the F29 Workstation Live 10/13 drop for several hours
now and so far I found one problem and it's not a required thing.
The problem is with SELinux Troubleshooter; it won't start and show it's
window. When I click the icon, I get the SELinux Troubleshooter menu
header in the top bar, but the window never comes up. and after several
seconds, the menu header leaves the top bar.
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.
I'm wondering if this is a bug I should report, or a new feature that it
won't show the window unless there is an Alert to display.
Have a Great Day!
Pat (tablepc)
_______________________________________________
test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/test@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/test@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/test@xxxxxxxxxxxxxxxxxxxxxxx
