tracker-miner-fs crashed with SIGSEGV in g_type_check_is_value_type()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tracker (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Not quite sure, python-pip said it couldn't connect to a server and then this error popped up.
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: tracker-miner-fs 0.16.2-1ubuntu4
ProcVersionSign
Uname: Linux 3.13.0-17-generic x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Mar 17 11:33:59 2014
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2014-03-13 (4 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140312)
ProcCmdline: /usr/lib/
ProcEnviron:
LANGUAGE=en_US
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f201c76ea13 <g_type_
PC (0x7f201c76ea13) ok
source "(%rdx)" (0x0000019a) not located in a known VMA region (needed readable region)!
destination "%edi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: tracker
StacktraceTop:
g_type_
g_value_
?? () from /usr/lib/
g_signal_
g_signal_emit () from /usr/lib/
Title: tracker-miner-fs crashed with SIGSEGV in g_type_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo
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.