After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 771184 - tracker-extract constantly crashes
tracker-extract constantly crashes
Status: RESOLVED DUPLICATE of bug 758315
Product: tracker
Classification: Core
Component: Extractor
1.8.x
Other Linux
: Normal normal
: ---
Assigned To: tracker-extractor
tracker-extractor
Depends on:
Blocks:
 
 
Reported: 2016-09-10 13:21 UTC by Inactive account
Modified: 2016-10-09 13:15 UTC
See Also:
GNOME target: ---
GNOME version: 3.19/3.20


Description Inactive account 2016-09-10 13:21:35 UTC 
I am finding on Ubuntu GNOME 16.04.1 with GNOME 3.20 that I am constantly many many times a day getting an error saying that tracker-extract has crashed.

I initially reported this bug here: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1615712

However as that bug report is private I will also link this one which is old but it appears to be a duplicate of: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1178402

It tells me "tracker-extract crashed with signal 5 in g_malloc()". This bug was initially reported downstream some years ago and as no progress seems to have been made with fixing it I thought I should report the issue upstream as well.
Comment 1 Laurent Bonnaud 2016-09-12 15:48:18 UTC 
> I initially reported this bug here: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1615712

> However as that bug report is private [...]

If you are the reporter of this bug you can change its status from private to public.
Comment 2 Inactive account 2016-09-12 16:06:55 UTC 
I can, but I don't know exactly what private information is there and in which files because the files are too long to look through entirely so I don't want to mark it as public until it's information I am fine with being public.

But I will look into this and see what I can do.
Comment 3 Carlos Garnacho 2016-10-09 13:15:46 UTC 
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed in the code repository.

*** This bug has been marked as a duplicate of bug 758315 ***