strigidaemon crashed with SIGSEGV in CLuceneIndexWriter::deleteEntry()

Bug #141228 reported by Vangelis Tasoulas
6
Affects Status Importance Assigned to Milestone
strigi (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

The crash manager with that report came up just when I logged in....

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Wed Sep 19 23:15:49 2007
Disassembly: 0x50:
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/strigidaemon
NonfreeKernelModules: fglrx
Package: strigi-daemon 0.5.5-2ubuntu2
PackageArchitecture: amd64
ProcCmdline: 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:
 ?? ()
 CLuceneIndexWriter::deleteEntry ()
 CLuceneIndexWriter::deleteEntries ()
 ?? () from /usr/lib/libstreamanalyzer.so.0
 ?? () from /usr/lib/libstreamanalyzer.so.0
Title: strigidaemon crashed with SIGSEGV in CLuceneIndexWriter::deleteEntry()
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

Revision history for this message
Vangelis Tasoulas (cyberang3l) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()
?? ()
Strigi::DirAnalyzer::Private::update (this=0x66b9c0, analyzer=0x8f2160) at /build/buildd/strigi-0.5.5/src/streamanalyzer/diranalyzer.cpp:139
updateInThread (d=0x818790) at /build/buildd/strigi-0.5.5/src/streamanalyzer/diranalyzer.cpp:76
start_thread () from /lib/libpthread.so.0

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in strigi:
importance: Undecided → Medium
Revision history for this message
Harald Sitter (apachelogger) wrote :

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.

Changed in strigi:
status: New → Incomplete
Revision history for this message
Harald Sitter (apachelogger) wrote :

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!

Changed in strigi:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.