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 623836 - crash in tracker-0.8.13-1.fc13: extract_msword_content
crash in tracker-0.8.13-1.fc13: extract_msword_content
Status: RESOLVED FIXED
Product: tracker
Classification: Core
Component: Extractor
0.8.x
Other Linux
: Normal normal
: ---
Assigned To: tracker-extractor
Jamie McCracken
Depends on:
Blocks:
 
 
Reported: 2010-07-08 13:54 UTC by Deji Akingunola
Modified: 2010-07-08 15:14 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Crash backtace (73.69 KB, text/plain)
2010-07-08 13:54 UTC, Deji Akingunola
Details

Description Deji Akingunola 2010-07-08 13:54:43 UTC
Created attachment 165478 [details]
Crash backtace

Fedora bug; https://bugzilla.redhat.com/show_bug.cgi?id=612273

architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/tracker-extract
component: tracker
crash_function: extract_msword_content
executable: /usr/libexec/tracker-extract

comment
-----
tracker also dumps lots of error messages into ~/.xsession-errors, but since
these are not time-stamped, I can't correlate them to the crash reported above.
The error message from .xsession-errors that looks most interesting is:
Tracker-Message: ---> [210|tracker-miner-fs] Failed, Unable to insert multiple
values for subject
`urn:software-category:%2Fusr%2Fshare%2Fdesktop-directories%2Fgnomecc.directory'
and single valued property `nfo:fileLastModified' (old_value:
'<untransformable>', new value: '<untransformable>')

How to reproduce
-----
1.  It happens every time I login
2.  Resetting the databases with "tracker-control -r" caused the crash log to
list a different Microsoft Word document than previously, but the reports look
the same
3.
Comment 1 Aleksander Morgado 2010-07-08 15:14:49 UTC
Table of pieces seems empty in a msword file being parsed.

Fixed in a0f02d59ebedfcef1eb4e5e0ae2958b811b8beb2

This problem has been fixed in our software repository. The fix will go into the next software release. Thank you for your bug report.