strigi 5.5-2 segfaults on m3u files

[Milian Wolff]

Binary package hint: strigi-daemon

Current version of strigi in gutsy (5.5-2) has a bug which leads to a segfault when indexing `*.m3u` files.

To reproduce do the following:

$ cd /path/to/some/musik/
$ ls *.mp3 > test.m3u
$ xmlindexer test.m3u
nthreads: 2
<?xml version='1.0' encoding='UTF-8'?>
<metadata>
WARNING: field "TODO_trackNumber" is not defined in .fieldproperties ontology database.
WARNING: field "TODO_discNumber" is not defined in .fieldproperties ontology database.
 <file uri='test.m3u' mtime='1189119596'>
  <value name='content.format_subtype'>simple</value>
  <value name='system.size'>1100</value>
Segmentation fault

This was confirmed in #strigi on freenode and it seems that the following bug (which is already fixed in svn) is the cause:
http://sourceforge.net/tracker/index.php?func=detail&aid=1773644&group_id=171000&atid=856302

Since m3u files are pretty common (think amarok etc.) I'd suggest strigi should be updated. Phreedom told me on IRC that strigi release are quite frequent nowadays so lets see.

[Milian Wolff (milianw)]

**Workaround:**

Edit your `~/.strigi/daemon.conf` and add these lines to your filter section:

    <filter pattern='*.m3u' include='0'>
    </filter>

This will exclude all `*.m3u` files from being indexed.

[Dax Solomon Umaming (knightlust)]

Thank you for reporting this bug and helping make Ubuntu better. I confirm this bug and changing Importance to Low due to existing workaround.

[Michael Deelwater (launchpad-falsum)]

The described workaround does not work.

strigidaemon still segfaults. Since I recieve the warning

WARNING: field "TODO_trackNumber" is not defined in .fieldproperties ontology database.
WARNING: field "TODO_discNumber" is not defined in .fieldproperties ontology database.

even if I just pass one file to xmlindexer which is handled without problems I assume that the segfault is independent of the described warning.

I am trying to identify which files cause it but I feel uncomfortable with using xmlindexer since it seems to hang at certain files. strigidaemons segfault might have another reason.

[Harald Sitter (apachelogger)]

Still an issue with 0.5.11?

[Milian Wolff (milianw)]

Seems to work now.

*Waving back to Harald ;-)*

[Harald Sitter (apachelogger)]

Hehe.
Thank you, marking as fix released.