strigidaemon crashed with SIGSEGV in memcpy()

Bug #149960 reported by David Blewett
6
Affects Status Importance Assigned to Milestone
strigi (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Every time I click the Index link in the strigi kio, it starts then immediately stops.

ProblemType: Crash
Architecture: i386
Date: Sat Oct 6 14:57:38 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/strigidaemon
NonfreeKernelModules: cdrom
Package: strigi-daemon 0.5.5-2ubuntu2
PackageArchitecture: i386
ProcCmdline: /usr/bin/strigidaemon
ProcCwd: /
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:
 memcpy () from /lib/tls/i686/cmov/libc.so.6
 lucene::store::RAMIndexOutput::flushBuffer ()
 lucene::store::IndexOutput::flush ()
 lucene::store::IndexOutput::close ()
 lucene::store::RAMIndexOutput::close ()
Title: strigidaemon crashed with SIGSEGV in memcpy()
Uname: Linux pharaon 2.6.22-13-generic #1 SMP Thu Oct 4 17:18:44 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Tags: apport-crash
Revision history for this message
David Blewett (david.blewett) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:memcpy () from /lib/tls/i686/cmov/libc.so.6
lucene::store::RAMIndexOutput::flushBuffer () from /usr/lib/libclucene.so.0
lucene::store::IndexOutput::flush () from /usr/lib/libclucene.so.0
lucene::store::IndexOutput::close () from /usr/lib/libclucene.so.0
lucene::store::RAMIndexOutput::close () from /usr/lib/libclucene.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.