On 05/28/2015 08:00 AM, Ed Greshko wrote:
On 05/28/15 18:00, Temlakos wrote:
> On 05/28/2015 12:34 AM, Ed Greshko wrote:
>> I was configuring openVPN and the connection was failing. Checking the journal
revealed an selinux AVC was being encountered. However, unlike in F21, the setroubleshoot
client tool (sealert) did not pop up and there was no indication in the systray
notifications.
>>
>> Is this a plasma5 shortcoming at the moment?
>>
> You've run smack into the old v. new system tray issue. Whoever designed the
selinux troubleshooter needs to update the nature of his system tray icons. In the
meantime, install
What, if I am correct, annoys me is that sealert is part of the setroubleshoot-server
package which appears to be a "fedora hosted" project. IMO, this would be one
of the system tools that should have been identified and updated to work in the new
plasma5 environment.
> wmsystemtray
>
> and pass these commands to it:
>
> $ wmsystemtray --non-wmaker --bgcolor=white
I hate these workarounds.
> You likely need to run an selinux command to repair a label somewhere--a very simple
command. Your best bet, this instant, is to launch selinux troubleshooter directly, using
the application launcher. (Find it under Administration.) It should still have the alert
stored on it, so you can act on it.
>
Oh, I was sort of expecting this error seeing as the method I used to restore some files
in my test system was bound to not preserve the selinux context. And, the relevant info
was in the journal as I mentioned. So, it was easy to fix.
I had that same error. The first thing sealert suggested to me, as soon
as I could bring up its window, was to make a label repair.
I don't like that kind of workaround either. Now I just installed the
package sni-qt, in both the i686 and x86-64 architectures. It
reconfigures some, but not all, of the old systray icons to work with
the new systray.
Temlakos