ABRT changes for Fedora Workstation (22 and further)

[Bastien Nocera]

Hey,

A small update on this.

----- Original Message -----
> Hey,
> 
> Before the end of year holidays, Allan and I went to Brno to meet up
> with the ABRT team, in order to see what could be done to integrate
> ABRT and gnome-abrt better into Fedora Workstation, and into GNOME.
> 
> We now have a number of TODO items, which can be worked on incrementally,
> which I will list below.
> 
> - ABRT:
>   - https://github.com/abrt/abrt/milestones/Fedora%2022
>   - https://github.com/abrt/abrt/issues/891
>   - https://github.com/abrt/abrt/issues/887

Those last 2 bugs have been fixed.

> - gnome-abrt:
>   - https://github.com/abrt/gnome-abrt/issues

Some headway was made, but we're currently blocking on a few architectural problems.

> - GNOME:
>   - https://bugzilla.gnome.org/show_bug.cgi?id=742375

This has been merged into control-center-3.15.90, soon in Fedora 22 and rawhide.

Note that the current privacy policy linked doesn't cover the uReport server, the
retrace server, or Bugzilla.

> - Retrace server:
>   - Make it possible to filter by Fedora product (Workstation, Server, Cloud)
> - Longer-term:
>   - Using gnome-abrt for better SELinux notifications
>   - "Merge" local and remote retracing into one:
>   - https://github.com/abrt/abrt/issues/832
>   - Look into privacy policies (what happens when Fedora contributors start
>     leaking information about a user's choice of documents in a bug report?)
> 
> Allan will be working on finalising the gnome-abrt mockups so that Jakub
> Filak can
> work on the gnome-abrt issues. He will also be documenting common workflows
> between
> server and desktop to share with the ABRT and Cockpit teams.
> 
> I'll be working on the GNOME Settings part of the equation in a couple of
> days,
> and will likely shift to ABRT or gnome-abrt issues further down the line.

I'm currently blocked on the way to handle bug reports for non-admin users, in particular,
when admins are also logged in.

There are also a number of architectural problems in abrtd:
- https://github.com/abrt/abrt/issues/917
- https://github.com/abrt/abrt/issues/916

For abrt-applet, we currently cannot accurately detect which application crashed to offer to
relaunch it, though we attempt to, or whether that application is running again now.

I'm also unclear on how bugs need to be auto-reported if abrt-applet wasn't running. It seems
easier longer term to move the notification directly in gnome-abrt.

Cheers