Description of problem: If an alert occurs in Fedora 22, a new notification is added to the notification menu (top center). But after clicking on it, nothing happens. That is a bug, the setroubleshoot window should open instead showing the particular denial mentioned. Also, a tray icon is added to the bottom left. After clicking on it, it runs setroubleshoot. But the icon should not be there, at least in GNOME. There's no reason to duplicate this as notifications and tray icons. The purpose of new GNOME notification system is that have a persistent overview of past alerts. Version-Release number of selected component (if applicable): setroubleshoot-server-3.2.24-1.fc22.x86_64 setroubleshoot-3.2.24-1.fc22.x86_64 setroubleshoot-plugins-3.0.61-1.fc22.noarch gnome-shell-3.16.2-1.fc22.x86_64 How reproducible: always Steps to Reproduce: 1. cause an alert (I'm not sure how, but you'll surely know) 2. try to click on the notification in the notification menu, nothing happens 3. see that an icon was added to the tray (you might need to expand it first), shouldn't happen
Created attachment 1027004 [details] screenshot This is how it looks at the moment, after a denial happens.
It would need to rewrite seaplet to GTK+3 and to GNotification. I'd consider this as RFE for future releases.
*** Bug 1230091 has been marked as a duplicate of this bug. ***
(In reply to Petr Lautrbach from comment #2) > It would need to rewrite seaplet to GTK+3 and to GNotification. I'd consider > this as RFE for future releases. I agree.
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle. Changing version to '23'. (As we did not run this process for some time, it could affect also pre-Fedora 23 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23
*** Bug 1309395 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Still a problem in F26. Someone please update the version.
This bug appears to have been reported against 'rawhide' during the Fedora 27 development cycle. Changing version to '27'.
Because of https://bugzilla.gnome.org/show_bug.cgi?id=785956 (removal of the legacy tray entirely from GNOME in 3.26), there will not now be a functional SELinux Troubleshooter notification until this bug is fixed.
@Michael, this isn't an RFE, it is a functional regression on the *official/primary* Fedora desktop. AFAICS supporting the "new" (actually not new at all at this point - bug is from *2015*) notification system is also orthogonal to GTK3 support, and could be handled without porting (in the worst case, with a notifier shim).
Stephen, all, are you familiar with new notification system? Would you be able to come up with some initial change and attach it here or create a PR on pagure.io/setroubleshoot or github.com/fedora-selinux/setroubleshoot? I would really help to move things forward.
In Python/GObject yes, but don't have time to familiarise myself with the source/work out if it's in the Py or C parts at the moment unfortunately.
I started rewrite of seapplet to use Gnome 3 notifications in https://pagure.io/fork/plautrba/setroubleshoot/commits/WIP-gnome3-notifications Builds are available https://copr.fedorainfracloud.org/coprs/plautrba/setroubleshoot/ Original seapplet was renamed to seappletlegacy and the new seapplet.py is seapplet now.
*** Bug 1530639 has been marked as a duplicate of this bug. ***
Petr, thanks for your work. When I attempt to run the new seapplet I get the following message: $ seapplet Traceback (most recent call last): File "/usr/bin/seapplet", line 28, in <module> from pydbus import SystemBus ModuleNotFoundError: No module named 'pydbus' Installing "python3-pydbus" resolves the issue so you may wish to add a Requires for it.
So this is built from https://pagure.io/setroubleshoot/tree/764d0c3426cc93f0d57a21a361226b9abfb75459 in Rawhide now - setroubleshoot-3.3.15-1.fc28 If you want/need to use the original Gtk 2 seapplet, you can install setroubleshoot-legacy and change Exec= to /usr/bin/seappletlegacy in ~/.config/autostart/sealertauto.desktop
setroubleshoot-3.3.15-1.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-8496be2ef4
setroubleshoot-3.3.15-1.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-8496be2ef4
setroubleshoot-3.3.15-1.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.