Hi Kevin,

I was under the impression that the problem with many emails from Bugzilla has already been fixed:
https://bugzilla.redhat.com/show_bug.cgi?id=1660157
https://github.com/abrt/libreport/commit/569bf0e3fed698e93b8e098bf6a0bb2f773aed6a


Regards,
Jakub



On 4/7/19 1:59 AM, Zbigniew Jędrzejewski-Szmek wrote:
> Hi,
>
> I was looking at some abrt reports in the bugzilla [1,2,3], and I seems that
> the reports contain much less information than in the past. In particular,
> the "var_log_messages" attachment is always just a few useless lines that
> a) seems to be cut down just to messages *from* the service, and has no
> messages *about* the service
> b) the messages are only from a short time period before the crash
>
> When a service dies, systemd logs quite a bit of useful information [4]
> about the causes. We also have services like pcp, which log information about
> resource starvation [5].
>
> This extra information would surely be helpful to diagnose abrt reports.
> Can we please make the reports contain useful logs again (at least
> full 'journalctl -u' for the service and all logs timed from around the crash) ?
>
> More information about the machine, for example /proc/meminfo would be
> great too.

I think:

https://github.com/abrt/abrt/

is the correct place to file bugs/RFE's.
I don't know if any of the abrt developers read the list or not.

I really wish someone could fix libreport to only send 1 or 2 emails on
new abrt bugzilla tickets again. It used to do this, but somehow broke
with bugzilla5 upgrade, so now when someone files an abrt bug you get
like 25 emails for it. I thought I filed a bug on this, but I can't seem
to find it right now, will look more and refile if I can't find it.

Also, someone noted the other day that abrt/libreport doesn't work with
the new signin options on bugzilla5. You login with the redhat or fedora
idps and it will ask you still for a username/password to file the bug.
:(

kevin

_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org