Re: [Bug 135050] Re: strigidaemon crashed with SIGSEGV in Strigi::AnalyzerConfiguration::indexType()

2007-10-09 Thread Paul-Sebastian Manole
*** This bug is a duplicate of bug 134049 *** https://bugs.launchpad.net/bugs/134049 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,

[Bug 135050] Re: strigidaemon crashed with SIGSEGV in Strigi::AnalyzerConfiguration::indexType()

2007-10-08 Thread Jesse Burt
*** 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

[Bug 135050] Re: strigidaemon crashed with SIGSEGV in Strigi::AnalyzerConfiguration::indexType()

2007-10-04 Thread Paul-Sebastian Manole
*** This bug is a duplicate of bug 134049 *** https://bugs.launchpad.net/bugs/134049 It crashed after I reconfigured it and started indexing manually. -- strigidaemon crashed with SIGSEGV in Strigi::AnalyzerConfiguration::indexType() https://bugs.launchpad.net/bugs/135050 You received this

[Bug 135050] Re: strigidaemon crashed with SIGSEGV in Strigi::AnalyzerConfiguration::indexType()

2007-09-22 Thread obxjdt
*** This bug is a duplicate of bug 134049 *** https://bugs.launchpad.net/bugs/134049 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. -- strigidaemon crashed

[Bug 135050] Re: strigidaemon crashed with SIGSEGV in Strigi::AnalyzerConfiguration::indexType()

2007-09-14 Thread obxjdt
*** This bug is a duplicate of bug 134049 *** https://bugs.launchpad.net/bugs/134049 seem to be going around... -- strigidaemon crashed with SIGSEGV in Strigi::AnalyzerConfiguration::indexType() https://bugs.launchpad.net/bugs/135050 You received this bug notification because you are a

[Bug 135050] Re: strigidaemon crashed with SIGSEGV in Strigi::AnalyzerConfiguration::indexType()

2007-09-14 Thread James Dowden
*** This bug is a duplicate of bug 134049 *** https://bugs.launchpad.net/bugs/134049 I think that reporting this as a duplicate of #134049 is a bug in itself, seeing as #134049 throws up a 403. -- strigidaemon crashed with SIGSEGV in Strigi::AnalyzerConfiguration::indexType()

[Bug 135050] Re: strigidaemon crashed with SIGSEGV in Strigi::AnalyzerConfiguration::indexType()

2007-09-12 Thread Francesco Battaglini
*** This bug is a duplicate of bug 134049 *** https://bugs.launchpad.net/bugs/134049 I have the same problem that Daniele has -- strigidaemon crashed with SIGSEGV in Strigi::AnalyzerConfiguration::indexType() https://bugs.launchpad.net/bugs/135050 You received this bug notification because

[Bug 135050] Re: strigidaemon crashed with SIGSEGV in Strigi::AnalyzerConfiguration::indexType()

2007-09-07 Thread Kosmonaut
*** This bug is a duplicate of bug 134049 *** https://bugs.launchpad.net/bugs/134049 confirming this bug -- strigidaemon crashed with SIGSEGV in Strigi::AnalyzerConfiguration::indexType() https://bugs.launchpad.net/bugs/135050 You received this bug notification because you are a member of

[Bug 135050] Re: strigidaemon crashed with SIGSEGV in Strigi::AnalyzerConfiguration::indexType()

2007-09-06 Thread Daniele Sapino
*** This bug is a duplicate of bug 134049 *** https://bugs.launchpad.net/bugs/134049 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

[Bug 135050] Re: strigidaemon crashed with SIGSEGV in Strigi::AnalyzerConfiguration::indexType()

2007-09-05 Thread Tier
*** This bug is a duplicate of bug 134049 *** https://bugs.launchpad.net/bugs/134049 Same problem. -- strigidaemon crashed with SIGSEGV in Strigi::AnalyzerConfiguration::indexType() https://bugs.launchpad.net/bugs/135050 You received this bug notification because you are a member of Ubuntu

[Bug 135050] Re: strigidaemon crashed with SIGSEGV in Strigi::AnalyzerConfiguration::indexType()

2007-09-03 Thread Luka Renko
*** This bug is a duplicate of bug 134049 *** https://bugs.launchpad.net/bugs/134049 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 (Ubuntu)

[Bug 135050] Re: strigidaemon crashed with SIGSEGV in Strigi::AnalyzerConfiguration::indexType()

2007-08-27 Thread Giovanni Cucca
** Attachment added: CoreDump.gz http://launchpadlibrarian.net/9009882/CoreDump.gz ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/9009883/Dependencies.txt ** Attachment added: Disassembly.txt http://launchpadlibrarian.net/9009884/Disassembly.txt ** Attachment

[Bug 135050] Re: strigidaemon crashed with SIGSEGV in Strigi::AnalyzerConfiguration::indexType()

2007-08-27 Thread Apport retracing service
StacktraceTop:CLuceneIndexWriter::addValue (this=value optimized out, idx=0x430050c0, field=0x6d002e, CLuceneIndexWriter::addValue (this=0x6543f0, idx=0x430050c0, field=0x6d002e, Strigi::LineEventAnalyzer::endAnalysis (this=0x74d490, complete=true)