strigidaemon crashed with SIGSEGV in Strigi::AnalyzerConfiguration::indexType()

Bug #135050 reported by Giovanni Cucca
282
Affects Status Importance Assigned to Milestone
strigi (Ubuntu)
In Progress
Medium
Luka Renko

Bug Description

It crashes whenever I try to configure the strigi applet

ProblemType: Crash
Architecture: amd64
Date: Sun Aug 26 15:51:22 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/strigidaemon
NonfreeKernelModules: ath_hal
Package: strigi-daemon 0.5.5-2build1
PackageArchitecture: amd64
ProcCmdline: /usr/bin/strigidaemon clucene
ProcCwd: /home/spawn
ProcEnviron:
 LANGUAGE=it_IT:it:en_GB:en
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: strigi
StacktraceTop:
 Strigi::AnalyzerConfiguration::indexType ()
 CLuceneIndexWriter::addValue ()
 CLuceneIndexWriter::addValue ()
 ?? () from /usr/lib/libstreamanalyzer.so.0
 ?? () from /usr/lib/libstreamanalyzer.so.0
Title: strigidaemon crashed with SIGSEGV in Strigi::AnalyzerConfiguration::indexType()
Uname: Linux sincity 2.6.22-10-generic #1 SMP Wed Aug 22 07:42:05 GMT 2007 x86_64 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Tags: apport-crash
Revision history for this message
Giovanni Cucca (spawnhcs-deactivatedaccount) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:CLuceneIndexWriter::addValue (this=<value optimized out>, idx=0x430050c0, field=0x6d0000002e,
CLuceneIndexWriter::addValue (this=0x6543f0, idx=0x430050c0, field=0x6d0000002e,
Strigi::LineEventAnalyzer::endAnalysis (this=0x74d490, complete=true)
Strigi::EventThroughAnalyzer::handleEnd (this=0x74b360)
Strigi::DataEventInputStream::read (this=0x7fa050, start=@0x43004ef8, min=20480,

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
Revision history for this message
Luka Renko (lure) wrote :

This is fixed in SVN: r699698

r699698 | aumuell | 2007-08-14 00:14:47 +0200 (Tue, 14 Aug 2007) | 2 lines

don't crash because of using uninitialized tracksField

Changed in strigi:
assignee: nobody → lure
importance: Undecided → Medium
status: New → In Progress
Revision history for this message
Alexey Ermakov (strangebrew) wrote :

Same problem.

Revision history for this message
Daniele Sapino (daniele-sapino) wrote :

I dont'kow if it can help (forgive my luserness), when I get to the configuration page and I press "start strigi demon" everything seems ok, but when I press "start indexing" the demon seem to arrest after a couple of seconds and then i get the crash message. I run on Kubuntu Gutsy tribe 5.

Revision history for this message
"Kosmonaut" Bernd Müller (bernado-tornado) wrote :

confirming this bug

Revision history for this message
Francesco Battaglini (francesco-battaglini) wrote :

I have the same problem that Daniele has

Revision history for this message
obxjdt (mrxcg) wrote :

seem to be going around...

Revision history for this message
James D (james-d1) wrote :

I think that reporting this as a duplicate of #134049 is a bug in itself, seeing as #134049 throws up a 403.

Revision history for this message
obxjdt (mrxcg) wrote :

Not sure this report is accurate. I installed a kernel update that needed a reboot to complete. The reboot may have caused the crash buy shutting down a running app unexpectedly.

Revision history for this message
Paul-Sebastian Manole (brokenthorn) wrote :

It crashed after I reconfigured it and started indexing manually.

Revision history for this message
Jesse Burt (avsa242) wrote :

(In lieu of posting a report as a comment to bug #134049):
I confirm that this crashes when attempting to perform a manual index. It occurred one time upon bootup once the the KDE session had finished loading as well.

Revision history for this message
Paul-Sebastian Manole (brokenthorn) wrote : Re: [Bug 135050] Re: strigidaemon crashed with SIGSEGV in Strigi::AnalyzerConfiguration::indexType()

Yes, it happens exactly after loading up KDE. Killing it and restarting it
sometimes solved the crashing. Strigidaemon is a poor piece of software. Why
is is installed by default on the desktop?

On 10/9/07, Jesse Burt <email address hidden> wrote:
>
> *** This bug is a duplicate of bug 134049 ***
> https://bugs.launchpad.net/bugs/134049
>
> (In lieu of posting a report as a comment to bug #134049):
> I confirm that this crashes when attempting to perform a manual index. It
> occurred one time upon bootup once the the KDE session had finished loading
> as well.
>
> --
> strigidaemon crashed with SIGSEGV in
> Strigi::AnalyzerConfiguration::indexType()
> https://bugs.launchpad.net/bugs/135050
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
[Thorns]
Tessa IM at OL - http://obsidianlake.com/
My blog - http://obsidianlake.blogspot.com/
My host - http://www.aquawebsolutions.com/

Revision history for this message
Paul-Sebastian Manole (brokenthorn) wrote : Paul-Sebastian Manole wants to stay in touch on LinkedIn

LinkedIn
------------

Bug,

I'd like to add you to my professional network on LinkedIn.

- Paul-Sebastian Manole

Paul-Sebastian Manole
Electronic Security Systems Technician at SHIFT 3 SECURITY S.R.L.
Romania

Confirm that you know Paul-Sebastian Manole
https://www.linkedin.com/e/isd/1040409543/A58jzoiP/

------
(c) 2010, LinkedIn Corporation

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.