Libreport crashes

Hello, peeps!

I am experiencing crashes with gnome-abrt. I have several crashes that I want to report in Bugzilla, but libreport keeps crashing when I try to file reports. I tried to launch it through the terminal to see what was causing it and this is the output:

~$ gnome-abrt

(gnome-abrt:12043): Gtk-WARNING **: 17:29:39.302: Theme parsing error: main-dark.css:2470:0: Expected a valid selector

(org.freedesktop.GnomeAbrt:12068): Gtk-WARNING **: 17:29:42.849: Theme parsing error: main-dark.css:2470:0: Expected a valid selector
free(): double free detected in tcache 2

At first I thought it was an issue with the theme I was using, but switching back to the default theme did not solve the issue:

free(): double free detected in tcache 2

Any help is greatly appreciated.

1 Like

Looks like

May be the source of the problem.


Ah, thanks. If you don’t mind me asking: how did you find this out? Just so that I can do the same for future issues.

1 Like

I went to [Simple Search] and searched for

free(): double free detected in tcache 2

or libreport

And sorted by date


Sweet! Appreciate it :slight_smile:

lib report crashes every time I try to report any bug.
I have used delete option to clear all reports, but this doesn’t help.

It’s been like 2 days since I have got this error popping up whenever I try to report a bug. It crashes abruptly.

Is there something I can do about this? I have read about abrt command which can be used to tackle this, but not so sure about it. Let me know if you need more info about the system.

pranav@fedora ~> uname -a
Linux fedora 5.12.8-300.fc34.x86_64 #1 SMP Fri May 28 15:20:54 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Check this topic and see if it is the same issue

1 Like

yes, this is the same issue. Is there something I can add to help!?

1 Like

You can help by add comments to the bug report.

1 Like

According to the latest comments on that bug report, it is fixed. Please update your computer (if not done already) and the crashes in libreport should be gone.

yes, it has been fixed in a recent update (i.e 2 days ago).

I was waiting so much for it. Finally, it has been fixed.

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.