strigidaemon crashed with SIGSEGV in lucene::store::BufferedIndexInput::seek()

[Vangelis Tasoulas]

I was just testing strigidaemon because when I am starting indexing it always crashing.
I was stopping and starting the service frequently.
Finally I deleted the "~/.strigi" folder and started the service again. It has indexed about 13000 files in 19MBytes and then again the same behavior...
Always when I start indexing is crashing.

Finally I did a reboot and when I logged in the Crash manager handled that problem.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Fri Sep 21 11:20:03 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/strigidaemon
NonfreeKernelModules: fglrx
Package: strigi-daemon 0.5.5-2ubuntu2
PackageArchitecture: amd64
ProcCmdline: /usr/bin/strigidaemon clucene
ProcCwd: /home/cyber
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: strigi
StacktraceTop:
 lucene::store::BufferedIndexInput::seek ()
 lucene::index::FieldInfos::write ()
 lucene::index::DocumentWriter::addDocument ()
 lucene::index::IndexWriter::addDocument ()
 CLuceneIndexWriter::finishAnalysis ()
Title: strigidaemon crashed with SIGSEGV in lucene::store::BufferedIndexInput::seek()
Uname: Linux Aurora 2.6.22-11-generic #1 SMP Mon Sep 17 03:18:44 GMT 2007 x86_64 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

[Apport retracing service (apport)]

StacktraceTop:lucene::store::BufferedIndexInput::seek () from /usr/lib/libclucene.so.0
lucene::index::FieldInfos::write () from /usr/lib/libclucene.so.0
lucene::index::DocumentWriter::addDocument () from /usr/lib/libclucene.so.0
lucene::index::IndexWriter::addDocument () from /usr/lib/libclucene.so.0
CLuceneIndexWriter::finishAnalysis (this=0x6534e0, idx=0x430050c0)

[Harald Sitter (apachelogger)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

[Harald Sitter (apachelogger)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!