After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 685378 - Failure to index the content of many files
Failure to index the content of many files
Status: RESOLVED DUPLICATE of bug 680897
Product: tracker
Classification: Core
Component: General
0.14.x
Other Linux
: Normal normal
: ---
Assigned To: tracker-general
Depends on:
Blocks:
 
 
Reported: 2012-10-03 11:51 UTC by Laurent Bonnaud
Modified: 2012-10-24 15:35 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Here is a PDF file that triggers the problem on my system (678.47 KB, application/force-download)
2012-10-03 12:00 UTC, Laurent Bonnaud 		Details

Description Laurent Bonnaud 2012-10-03 11:51:51 UTC 
I am using (the yet unreleased) Ubuntu 12.10 with the following package
versions:

ii  libtracker-extract-0.14-0                                   0.14.1-1ubuntu5
                           i386         tracker extractor library
ii  libtracker-miner-0.14-0                                     0.14.1-1ubuntu5
                           i386         tracker data miner library
ii  libtracker-sparql-0.14-0                                    0.14.1-1ubuntu5
                           i386         metadata database, indexer and search
tool - library
ii  tracker                                                     0.14.1-1ubuntu5
                           i386         metadata database, indexer and search
tool
ii  tracker-explorer                                            0.14.1-1ubuntu5
                           i386         metadata database, indexer and search
tool - developer tool
ii  tracker-extract                                             0.14.1-1ubuntu5
                           i386         metadata database, indexer and search
tool - metadata extractors
ii  tracker-gui                                                 0.14.1-1ubuntu5
                           i386         metadata database, indexer and search
tool - GNOME frontends
ii  tracker-miner-fs                                            0.14.1-1ubuntu5
                           i386         metadata database, indexer and search
tool - filesystem indexer
ii  tracker-utils                                               0.14.1-1ubuntu5
                           i386         metadata database, indexer and search
tool - commandline tools

and I decided to completely reindex my homedir.  So I removed all tracker files
and directories in my homedir and started a new session.

The symptoms of this problem are:

 - the ~/.local/share/tracker/tracker-extract.log file contains many error messages such as:
Tracker-Warning **: Content extraction of PDF Timed out
Tracker-Critical **: Extraction task for 'file:///home/bonnaud/foo.pdf' went
rogue and took more than 20 seconds. Forcing exit.
(null)-Warning **: Attempted to read beyond buffer

Those error messages also appear for other file types (text, JPEG, ...)

 - the ~/.local/share/tracker/tracker-miner-fs.log contains many error messages such as:

Tracker-Warning **:   Got extraction DBus error on 'file:///home/bonnaud/foo.pdf': GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)

Note that the concerned files are not specially big and converting them to text with pdftotext is instantaneous.
Comment 1 Laurent Bonnaud 2012-10-03 12:00:54 UTC 
Created attachment 225676 [details]
Here is a PDF file that triggers the problem on my system
Comment 2 Jürg Billeter 2012-10-05 18:32:38 UTC 
This might be a duplicate of bug 680897.
Comment 3 Laurent Bonnaud 2012-10-05 20:19:04 UTC 
Indeed.  I am looking forward to a 14.3 tracker release...
Comment 4 Martyn Russell 2012-10-24 15:35:01 UTC 
It certainly is a duplicate as Jürg says AFAICS. This is not something we can fix. It's a bug in the poppler as the other report mentions. Feel free to follow that bug ;)

*** This bug has been marked as a duplicate of bug 680897 ***