this is part of our effort to better integrate with Cockpit. On this May, I
posted a video here and the video is showing how users can report crashes
via ABRT Cockpit module .
You asked me if there is a relevant journal entry, but there wasn't a good
journal message generated by ABRT at that time. Therefore Matej has been
working a new tool that creates nice journal messages (not all the time -
just last few weeks :).
Few days ago I asked him to create a demonstration video and inform Cockpit
ML about the possibility to show ABRT journal catalog messages in
What is the state of Troubleshooting module?
Is there anything we can do to help Cockpit team?
On 11/16/2016 04:43 PM, Stef Walter wrote:
> On 16.11.2016 16:40, Matej Habrnal wrote:
>> I'd like to inform you there is a new feature in ABRT.
>> Now, it's is possible to report problems into systemd journal.
>> If some problem occurs, abrt sends a catalog message into systemd
>> journal with some details about the problem (e.g. truncated backtrace, reason,
>> and also some information how to analyse the problem via abrt etc..
>> Content of catalog messages for each problem type can be configured,
>> the following wiki page  shows the default formatting of catalog messages.
>> For better understanding, I've created a video with examples .
> Does can that detailed information show up on the "Logs" page? Should
> there be another tab there with "Problems" or "Crashes"?
> Because this is essentially a log of system events, likely it should go
> there, no?
> cockpit-devel mailing list -- cockpit-devel(a)lists.fedorahosted.org
> To unsubscribe send an email to cockpit-devel-leave(a)lists.fedorahosted.org