strigidaemon crashed with SIGSEGV in Strigi::AnalysisResult::Private::write()

[Arpan Patelia]

I just booted my system in to Intrepid alpha 5 of Kubuntu and I was told that an application has crashed. I am reporting the bug using the same "Report a problem" feature.

Package
strigi-daemon: 0.5.11-1

ProblemType: Crash
Architecture: i386
CrashCounter: 1
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/strigidaemon
NonfreeKernelModules: nvidia
Package: strigi-daemon 0.5.11-1
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/strigidaemon
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_IN
 SHELL=/bin/bash
 LANGUAGE=en_US
Signal: 11
SourcePackage: strigi
StacktraceTop:
 ?? () from /usr/lib/strigi/strigiindex_sopranobackend.so
 Strigi::AnalysisResult::Private::write ()
 Strigi::AnalysisResult::~AnalysisResult ()
 Strigi::DirAnalyzer::Private::update ()
 Strigi::DirAnalyzer::Private::updateDirs ()
Title: strigidaemon crashed with SIGSEGV in Strigi::AnalysisResult::Private::write()
Uname: Linux 2.6.27-2-generic i686
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:Strigi::AnalysisResult::Private::write (this=0xb26b8240)
~AnalysisResult (this=0xb6b50104)
Strigi::DirAnalyzer::Private::update (this=0x8298488, analyzer=0x8298494)
Strigi::DirAnalyzer::Private::updateDirs (this=0x8298488, dirs=@0xb6b501d8, nthreads=2, c=0xbfdbe584)
Strigi::DirAnalyzer::updateDirs (this=0xb6b501e4, dirs=@0xb6b501d8, nthreads=2, caller=0xbfdbe584)

[Xosé (ubuntu-galizaweb)]

Same here, I just booted into KDE.

[Jonathan Thomas (echidnaman)]

Does this crash still occur for you in Kubuntu 9.04?

[Randy Webster (randy-webster-family-ar)]

Went back to regular Ubuntu with the 9.04 release.

On Sun, 2009-08-02 at 16:15 +0000, Jonathan Thomas wrote:

> Does this crash still occur for you in Kubuntu 9.04?
>
> ** Changed in: strigi (Ubuntu)
> Status: New => Incomplete
>

[Jonathan Thomas (echidnaman)]

Great. :) (The duplicate bug reports ended around 9.04, so I thought that there was a chance that this was fixed.)