strigidaemon crashed with SIGSEGV in EventListenerQueue::run()

Bug #127881 reported by Caleb Scott Cupples
12
Affects Status Importance Assigned to Milestone
strigi (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Crashed upon launching of the Strigi kicker plugin.

ProblemType: Crash
Architecture: i386
Date: Tue Jul 24 00:08:40 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/strigidaemon
NonfreeKernelModules: cdrom
Package: strigi-daemon 0.5.1svn20070712-0ubuntu4
PackageArchitecture: i386
ProcCmdline: /usr/bin/strigidaemon clucene
ProcCwd: /home/caleb
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:
 EventListenerQueue::run (this=0x80adb48)
 threadstarter (d=0x80adb48)
 start_thread () from /lib/tls/i686/cmov/libpthread.so.0
 clone () from /lib/tls/i686/cmov/libc.so.6
Title: strigidaemon crashed with SIGSEGV in EventListenerQueue::run()
Uname: Linux Suzuna-Kubuntu 2.6.22-8-generic #1 SMP Thu Jul 12 15:59:45 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Revision history for this message
Caleb Scott Cupples (cscupples) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:EventListenerQueue::run (this=0x80adb48) at /build/buildd/strigi-0.5.1svn20070712/./src/daemon/eventlistener/eventlistenerqueue.cpp:91
threadstarter (d=0x80adb48) at /build/buildd/strigi-0.5.1svn20070712/./src/daemon/strigithread.cpp:115
|����Ą () from /lib/tls/i686/cmov/libpthread.so.0
D8uC�WE܋G
9z
��) from /lib/tls/i686/cmov/libc.so.6

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
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.