On Tue, 2017-03-28 at 21:24 -0700, Adam Williamson wrote:
On Mon, 2017-03-27 at 08:17 -0500, Michael Catanzaro wrote:
On Mon, 2017-03-27 at 14:40 +0200, Jiri Eischmann wrote:
abrt itself is preinstalled and abrtd seems to be running. What is missing is the gnome-abrt which gives you UI for viewing the crashes and reporting them in BZ. So crashes are probably collected and automatically reported if permitted, but the user is not notified about them and there is no easy way to report them in BZ.
This is not intentional. The workstation-product group in comps includes the abrt-desktop package, and that requires gnome-abrt. So it should definitely be included. Further investigation is required to see what's going wrong here.
Haven't looked fully into this yet, but the anaconda packaging log for the Alpha RC4 Workstation live image compose:
https://kojipkgs.fedoraproject.org//work/tasks/5428/18645428/anaconda-packag...
shows abrt-desktop initially being selected for install, but not actually being installed. That suggests there was some kind of dependency issue and dnf just left it out of the transaction instead of complaining / aborting / whatever (I'm not sure if this is new or old behaviour).
Poking around on this, some background in:
https://bugzilla.redhat.com/show_bug.cgi?id=1292892
After that bug, I think dnf was made to error out if a *mandatory* package from a selected group cannot be installed, but not if a *default* package from a selected group cannot be installed.
https://bugzilla.redhat.com/show_bug.cgi?id=1427365
A similar case I came across recently (outside of anaconda).
I *think* comps entries with no explicit 'type' default to being treated as 'default', not 'mandatory', and dnf is considering it to be OK if a 'default' group package cannot be installed. After looking at the references, I'm pretty sure this is not how yum behaved. I don't know offhand why this behaviour was changed in dnf.