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

Bug #1228884 reported by Peter Bašista
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tracker (Ubuntu)
New
Undecided
Unassigned

Bug Description

I was copying some data from external e-sata drive when this error happened.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: tracker-miner-fs 0.16.1-1ubuntu2
ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1
Uname: Linux 3.11.0-8-generic x86_64
ApportVersion: 2.12.4-0ubuntu1
Architecture: amd64
Date: Sun Sep 22 13:55:02 2013
ExecutablePath: /usr/lib/tracker/tracker-miner-fs
InstallationDate: Installed on 2013-09-14 (7 days ago)
InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64 (20130903)
MarkForUpload: True
ProcCmdline: /usr/lib/tracker/tracker-miner-fs
SegvAnalysis:
 Segfault happened at: 0x7f6b3e0a5933 <g_type_check_is_value_type+355>: cmp (%rdx),%edi
 PC (0x7f6b3e0a5933) ok
 source "(%rdx)" (0x4821740438bf9104) not located in a known VMA region (needed readable region)!
 destination "%edi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: tracker
StacktraceTop:
 g_type_check_is_value_type () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_value_type_compatible () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: tracker-miner-fs crashed with SIGSEGV in g_type_check_is_value_type()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Peter Bašista (pbasista) wrote :
Revision history for this message
Apport retracing service (apport) wrote : 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 #1088024, 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.

information type: Private → Public
tags: removed: need-amd64-retrace
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.