Ubuntu
tracker package

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

Bug #1380306 reported by Braham on 2014-10-12

This bug report is a duplicate of: Bug #1336997: tracker-miner-fs crashed with SIGSEGV in g_file_get_uri(). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	tracker (Ubuntu)	New	Undecided	Unassigned

Bug Description

Always get crag error even after sudo apt-get upgrade some packages

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: tracker-miner-fs 1.0.4-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1
Uname: Linux 3.16.0-10-generic i686
ApportVersion: 2.14.7-0ubuntu5
Architecture: i386
CrashCounter: 1
CurrentDesktop: Unity
Date: Sun Oct 12 19:25:49 2014
ExecutablePath: /usr/lib/tracker/tracker-miner-fs
InstallationDate: Installed on 2011-09-18 (1119 days ago)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
ProcCmdline: /usr/lib/tracker/tracker-miner-fs
ProcEnviron:
LANGUAGE=en_US:en
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0xb74e5f27 <g_file_get_uri+39>: cmp %eax,(%edi)
PC (0xb74e5f27) ok
source "%eax" ok
destination "(%edi)" (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/i386-linux-gnu/libgio-2.0.so.0
?? () from /usr/lib/i386-linux-gnu/libtracker-miner-1.0.so.0
?? () from /usr/lib/i386-linux-gnu/libtracker-miner-1.0.so.0
g_cclosure_marshal_VOID__BOOLEANv () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: tracker-miner-fs crashed with SIGSEGV in g_file_get_uri()
UpgradeStatus: Upgraded to utopic on 2014-08-23 (49 days ago)
UserGroups: adm admin cdrom dialout dip lpadmin plugdev sambashare

Tags:

Revision history for this message

Braham (brahamshakti) wrote on 2014-10-12:

Dependencies.txt Edit (6.9 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2014-10-12: 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 #1336997, 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.