Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#60211 - [tracker] Segfaults with 2.1.5-1

Attached to Project: Arch Linux
Opened by Felix Meyer (fm) - Wednesday, 26 September 2018, 21:28 GMT
Last edited by Jan Alexander Steffens (heftig) - Friday, 05 October 2018, 02:49 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan Alexander Steffens (heftig)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 6
Private No

Details

Description:

tracker-miners 2.1.5-1

$dmesg
[ 25.778875] tracker-miner-a[995]: segfault at 20 ip 00007efccf4da16b sp 00007fffebdbbc90 error 4 in libtracker-sparql-2.0.so.0[7efccf496000+47000]

I get this when logging in into gnome3 from gdm.


[ 700.624446] tracker-extract[1893]: segfault at 20 ip 00007fdbf808516b sp 00007ffd148faa40 error 4 in libtracker-sparql-2.0.so.0[7fdbf8041000+47000]

when stating gnome-documents.
This task depends upon

Closed by  Jan Alexander Steffens (heftig)
Friday, 05 October 2018, 02:49 GMT
Reason for closing:  Fixed
Additional comments about closing:  tracker 2.1.5-2
Comment by Felix Meyer (fm) - Thursday, 27 September 2018, 06:21 GMT
its package tracker not tracker-miners downgrade tracker && tracker-miners to 2.1.4 solves the issue.
Comment by Stanislav T (stas-t) - Thursday, 27 September 2018, 20:50 GMT
Can confirm the issue. In my case it happens with many (any?) tracker services - tracker-extract, tracker-miner-rss, tracker-miner-fs, tracker-miner-apps. For any such crash the backtrace is similar - it fails at tracker_sparql_connection_get (libtracker-sparql-2.0.so.0).

UPD: Downgrading tracker and tracker-miners to 2.1.4-1 resolved issues for me as well.
Comment by David Sapienza (dsap) - Sunday, 30 September 2018, 11:06 GMT
I'm experiencing the same issue when logging with GDM.
Downgrading to 2.1.4 solves the problem.

I attached the relevant output from the systemd journal.
Comment by Eric (erock) - Wednesday, 03 October 2018, 15:18 GMT

Loading...