I wanted to mention the issue with the icons, because it seemed relevant,
and something we'd need to think about if we kept the package. But
certainly, the right thing to do if keeping setroubleshoot would be to make
sure that setroubleshoot notifies via the normal mechanisms (which are what
users are used to for updates, ABRT, etc) rather than to jump through hoops
to keep a hard-to-identify yellow nag icon that shows up on the desktop.
It sounds like from what Elad says, that nothing is necessary - and that
setroubleshoot was already using libnotify. That's good, and does slightly
reduce the bar to retain setroubleshoot, but having looked at
setroubleshoot UI again, I just don't feel there's a justification to
notify the user in the default configuration that they need to visit this
application - it's just not well suited to the task of walking a
non-operating-system-export through reporting an issue with the operating
system.
Owen
On Tue, Dec 19, 2017 at 9:57 AM, Stephen Gallagher <sgallagh(a)redhat.com>
wrote:
On Tue, Dec 19, 2017 at 9:38 AM Owen Taylor <otaylor(a)redhat.com> wrote:
> Hi Adam,
>
> While I appreciate that setroubleshoot can be a useful tool for testers
> to file bug reports, to be in the default install, I think it needs to meet
> some minimum requirement of good experience for users encountering it. -
> and when you consider setroubleshoot in the role of:
>
> Average target user encounters an operating system defect and reports it
>
> I just don't think it meets that target. In addition, as of gnome-3.26,
> we don't even show indicator icons unless you install an extension, so
> setroubleshoot isn't filling the expected role of notifying about problems.
>
>
I'm really not sure "We made a terrible decision to suppress projects'
notification mechanisms" == "this project isn't notifying about
problems".
The tool notifies... you just decided to stop showing that to the user and
are now using that as a circular argument for why the tool is not useful.
There are valid complaints to make about the user experience. However,
removing a tool that is eminently useful to developers of the system simply
because you don't think it's pretty enough is cutting off your nose to
spite your face.
The overwhelming majority of SELinux bugs get found and fixed because
people like me use Rawhide/Branched and use SETroubleshoot to report them.
This is why the Workstation WG seems to think that SELinux bugs don't
happen that often... we're catching them before you notice most of the time.
Yes, people can still install the package after the fact, but honestly
without it (and without the notifications you are suppressing by default),
people often do not realize the denials are occurring.
I think we need to get this back in the default install and fix the
misfeature of suppressing the system tray icon (even if this means
installing TopIcons+ by default on Workstation).
_______________________________________________
desktop mailing list -- desktop(a)lists.fedoraproject.org
To unsubscribe send an email to desktop-leave(a)lists.fedoraproject.org