tracker-miner-fs crashed with SIGSEGV in g_type_check_instance_is_a()

Bug #1725486 reported by vinid223
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
tracker-miners (Ubuntu)
Expired
Medium
Unassigned

Bug Description

I was navigating in the file system and expanded a folder. I was playing with the settings of the file manager during that time.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: tracker-miner-fs 2.0.2-1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 20 17:16:00 2017
ExecutablePath: /usr/lib/tracker/tracker-miner-fs
InstallationDate: Installed on 2017-10-19 (1 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcCmdline: /usr/lib/tracker/tracker-miner-fs
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fb3202e177e <g_type_check_instance_is_a+62>: testb $0x4,0x16(%rdx)
 PC (0x7fb3202e177e) ok
 source "$0x4" ok
 destination "0x16(%rdx)" (0x656572662e677282) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: tracker-miners
StacktraceTop:
 g_type_check_instance_is_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_file_equal () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? ()
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/libtracker-miner-2.0.so.0
Title: tracker-miner-fs crashed with SIGSEGV in g_type_check_instance_is_a()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
vinid223 (vinid223) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_type_check_instance_is_a (type_instance=type_instance@entry=0x56003f462580, iface_type=iface_type@entry=94559046120912) at ../../../../gobject/gtype.c:4013
 g_file_equal (file1=0x56003f462580, file2=0x7fb2e8001e40) at ../../../../gio/gfile.c:667
 writeback_remove_recursively (mf=0x56003e59c190, file=0x7fb2e8001e40) at tracker-miner-files.c:266
 miner_files_filter_event (fs=<optimized out>, type=<optimized out>, file=0x7fb2e8001e40, source_file=0x7fb2e8001e40) at tracker-miner-files.c:315
 filter_event (source_file=0x7fb2e8001e40, file=0x7fb2e8001e40, type=TRACKER_MINER_FS_EVENT_MOVED, fs=0x56003e59c190) at tracker-miner-fs.c:2295

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
Changed in tracker-miners (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Matthias Klose (doko)
information type: Private → Public
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
Erich Eickmeyer (eeickmeyer) wrote :

Thank you for reporting this bug to Ubuntu.

Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in.

Changed in tracker-miners (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for tracker-miners (Ubuntu) because there has been no activity for 60 days.]

Changed in tracker-miners (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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