tracker-miner-fs crashed with SIGABRT in raise()

Bug #1843262 reported by Sosha
176
This bug affects 36 people
Affects Status Importance Assigned to Milestone
Tracker
New
Unknown
tracker-miners (Ubuntu)
Triaged
High
Unassigned

Bug Description

after turn on pc

ProblemType: Crash
DistroRelease: Ubuntu 19.10
Package: tracker-miner-fs 2.1.6-1ubuntu1
ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9
Uname: Linux 5.2.0-15-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 9 17:17:05 2019
ExecutablePath: /usr/lib/tracker/tracker-miner-fs
InstallationDate: Installed on 2019-07-14 (57 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190701)
ProcCmdline: /usr/lib/tracker/tracker-miner-fs
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
Signal: 6
SourcePackage: tracker-miners
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libtracker-miner-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libtracker-miner-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libtracker-miner-2.0.so.0
Title: tracker-miner-fs crashed with SIGABRT in g_assertion_message_expr()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
separator:

Revision history for this message
Sosha (soshaw) wrote :
information type: Private → Public
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in tracker-miners (Ubuntu):
status: New → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

tags: added: need-amd64-retrace
Changed in tracker-miners (Ubuntu):
importance: Undecided → Low
status: Confirmed → Incomplete
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 raise () from /tmp/apport_sandbox_pksn0aka/lib/x86_64-linux-gnu/libc.so.6
 abort () from /tmp/apport_sandbox_pksn0aka/lib/x86_64-linux-gnu/libc.so.6
 g_assertion_message.cold () from /tmp/apport_sandbox_pksn0aka/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6103.0
 g_assertion_message_expr () from /tmp/apport_sandbox_pksn0aka/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6103.0
 file_tree_lookup (tree=0x7f308400ff50, file=file@entry=0x7f3074004340, parent_node=parent_node@entry=0x7fff13dca088, uri_remainder=uri_remainder@entry=0x7fff13dca090) at ../src/libtracker-miner/tracker-file-system.c:259

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
summary: - tracker-miner-fs crashed with SIGABRT in g_assertion_message_expr()
+ tracker-miner-fs crashed with SIGABRT in raise()
tags: removed: need-amd64-retrace
Revision history for this message
Sosha (soshaw) wrote :

This problem was repeated again after turning on PC!

Revision history for this message
Cedric Rochefolle (jscdroiddev) wrote :

I am also affected after upgrade from bionic to eaon.
Same StacktraceTop

Revision history for this message
Michael Cohen (mcohen) wrote :

Maybe you all can already tell this from the crash report, but here's what syslog says when this happens. As a previous poster noted, it happens every time the system boots up, and it started immediately after upgrading to Eoan (from Disco, in my case).

Oct 29 10:28:50 michael-XPS-13-9380 tracker-miner-fs.desktop[2100]: **
Oct 29 10:28:50 michael-XPS-13-9380 tracker-miner-fs.desktop[2100]: Tracker:ERRO
R:../src/libtracker-miner/tracker-file-system.c:259:file_tree_lookup: assertion
failed: (ptr[0] == '/')
Oct 29 10:28:50 michael-XPS-13-9380 tracker-miner-fs.desktop[2100]: Bail out! Tr
acker:ERROR:../src/libtracker-miner/tracker-file-system.c:259:file_tree_lookup: assertion failed: (ptr[0] == '/')

Revision history for this message
Eduardo Righes (eemmrr) wrote :

I am also seeing this issue.

Revision history for this message
Brent Pinkston (pinkston-brent) wrote :

I am also having this error, and the output is identical to the original poster, and also happens at each restart.

Revision history for this message
Srijan Kumar Sharma (raja-srijan) wrote :

I got the same error just after upgrading to 19.10 from 19.04. It didn't happen again.

Revision history for this message
Andreas Vinsander (andreas-vinsander) wrote :

Seeing this on each startup as well. The log looks like that posted in comment 10.

Changed in tracker-miners (Ubuntu):
importance: Low → High
status: Incomplete → Triaged
Changed in tracker:
status: Unknown → New
Revision history for this message
Dimitri (dimitri-lortet) wrote :

Seeing this on each startup as well.

Revision history for this message
Emil Kristensen (emil-ekristensen) wrote :

I'm also getting this error on every boot on my Dell XPS 13 (Model 9380) with Ubuntu 19.10. It has all updates installed. The error also shows up after sleep and at apparently random times as well.

Revision history for this message
Erlend Sjursen Lie (eslie) wrote :

Also getting this on every startup.

Revision history for this message
Carlo Röpke (carloroepke) wrote :

This affected me too. I'm using Ubuntu 19.10 on a Dell XPS 13 9360 with all updates installed. After some research I decided to disable tracker-miner-fs temporarily.
You can disable tracker-miner-fs too by using these commands:

/usr/bin/gsettings set org.freedesktop.Tracker.Miner.Files crawling-interval -2
/usr/bin/gsettings set org.freedesktop.Tracker.Miner.Files enable-monitors false

Afterwards you need to cleanup the database to reclaim some lost space on the disk using:

echo y | LANG=en tracker reset -r

While this doesn't fix the problem, it at least doesn't show me the error messages on every startup.
Hopefully someone can fix this problem soon.

Revision history for this message
Kurumor (kurumor) wrote :

I'm also getting same error message every time y boot my Alienware 15 R2. After upgrading to Ubuntu 19.10 from 19.04. All updates installed.

Revision history for this message
Gary M (gary-atahualpa) wrote :

I am also getting this exact error. I just upgraded from a pretty recent 19.04 installation to 19.10 and the bug occurs after every boot. All updates installed.

Revision history for this message
matsonfamily (david-matsonfamily) wrote :

carloroepke's workaround succeeded for me, but I used the gconf app for a GUI to change the crawling and enable-monitors values.

/org/freedesktop/tracker/miner/files/

Revision history for this message
Thomas (tombl) wrote :

I have 4 different machines, all four have different hardware, and I get this crasher every time at bootup, on all four of them since upgrading to 19.10.

Revision history for this message
Magnus (koma-lysator) wrote :

Happens at every boot.

Revision history for this message
Magnus (koma-lysator) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

The issue is due to a corrupted database, you can delete it and let tracker index again as a workaround
$ rm -rf ~/.cache/tracker

Revision history for this message
Richard Gagne (gagne-richard) wrote :

The solution(workaround) worked well for me.

Revision history for this message
Richard Gagne (gagne-richard) wrote :

oups ! the error is on return...sorry for the too quick comment.

tags: added: focal
Revision history for this message
Muhammad Ahmad (mdba) wrote :

I am also affected after upgrade from Ubuntu 18.04.4 LTS Bionic Beaver to Ubuntu 20.04 LTS Focal Fossa.

Revision history for this message
Muhammad Ahmad (mdba) wrote :

After running $ rm -rf ~/.cache/tracker the issue is resolved.
Thank you for the workaround.

Revision history for this message
pleabargain (dennisgdaniels) wrote :

trying to post bug

ubuntu-bug _usr_lib_tracker_tracker-miner-fs.1000.crash

and ubuntu crashed
:(

Revision history for this message
pleabargain (dennisgdaniels) wrote :

can't post follow up stack traces against this bug
https://youtu.be/AGEgEuHefFI

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.