Ubuntu GNOME

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

Bug #1567154 reported by Cheyenne on 2016-04-07

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	Ubuntu GNOME	New	Undecided	Unassigned

Bug Description

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: tracker-miner-fs 1.0.4-0ubuntu2+trusty2 [origin: LP-PPA-gnome3-team-gnome3-staging]
ProcVersionSignature: Ubuntu 4.2.0-35.40~14.04.1-generic 4.2.8-ckt5
Uname: Linux 4.2.0-35-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.20
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Wed Apr 6 20:21:14 2016
ExecutablePath: /usr/lib/tracker/tracker-miner-fs
InstallationDate: Installed on 2016-03-15 (22 days ago)
InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1)
ProcCmdline: /usr/lib/tracker/tracker-miner-fs
ProcEnviron:
LANGUAGE=en_CA:en
PATH=(custom, user)
XDG_RUNTIME_DIR=<set>
LANG=en_CA.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7fadde76a85c <g_file_get_uri+28>: cmp %rax,0x0(%rbp)
PC (0x7fadde76a85c) ok
source "%rax" ok
destination "0x0(%rbp)" (0x00000001) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: tracker
StacktraceTop:
g_file_get_uri () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
?? () from /usr/lib/x86_64-linux-gnu/libtracker-miner-1.0.so.0
?? () from /usr/lib/x86_64-linux-gnu/libtracker-miner-1.0.so.0
g_cclosure_marshal_VOID__BOOLEANv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: tracker-miner-fs crashed with SIGSEGV in g_file_get_uri()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin nopasswdlogin plugdev sambashare sudo

Tags:

Revision history for this message

Cheyenne (cheyenne-arrowsmith) wrote on 2016-04-07:

CrashDB.txt Edit (263 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (7.5 KiB, text/plain; charset="utf-8")

Revision history for this message

Ubuntu GNOME (ug-bot) wrote on 2016-04-07: This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1464218, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.