Red Hat Bugzilla – Bug 478509
Last modified: 2009-12-18 02:26:38 EST
$ rpm -q strigi
WARNING: field 'http://strigi.sf.net/ontologies/0.9#debugParseError' is not defined in any rdfs ontology database.
Oh joy, what better way to celebrate the New Year than a segfault! :-(
Apparently specific to x86_64, my i386 seems better (not tested too extensively yet).
boo, tried recently released 0.6.2, no love.
I think the bug is not in Strigi itself, but in Nepomuk's Strigi plugins (i.e. in KDE 4.2).
I think you're right... I'll try to snag a backtrace tonight.
A belated backtrace with strigi-0.6.3 + kdelibs-4.2.0-7:
#0 KComponentDataPrivate::lazyInit (this=0x0, component=@0x65a9c0)
#1 0x00007ffff4e206a0 in KComponentData::dirs (this=0x65a9c0)
#2 0x00007ffff605228f in init () at /usr/src/debug/kdelibs-4.2.0/nepomuk/core/nepomukmainmodel.cpp:107
#3 MainModel (this=0x6bd880, parent=0x6b7800)
#4 0x00007ffff604ebc6 in Nepomuk::ResourceManager::init (this=0x6cd870)
#5 0x00007ffff62980fb in createIndexManager () from /usr/lib64/strigi/strigiindex_sopranobackend.so
#6 0x0000000000c2f674 in Strigi::IndexPluginLoader::createIndexManager (name=<value optimized out>,
#7 0x00000000004160b4 in CombinedIndexManager (this=0x6b0080, type=@0x7fffffffd760,
indexdir=@0x7fffffffd750) at /usr/src/debug/strigi-0.6.3/src/combinedindexer/combinedindexmanager.cpp:135
#8 0x000000000040a5d6 in main (argc=<value optimized out>, argv=<value optimized out>)
bleh, I (accidentally) blew away ~/.strigi and now the problem's gone. Rats.
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '10'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 10's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 10 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.