strigidaemon cannot start, apparently for an error in the libclucene files

[Luke12]

Binary package hint: libclucene0

When trying to activate strigidaemon from the command line, the output is the following one:

strigidaemon: symbol lookup error: /usr/lib/libcluceneindex.so.0: undefined symbol: _ZN6Strigi13FieldRegister16contentFieldNameE

As a consequence, the daemon cannot be started and hence strigi is not usable.

[Daniel Hahler (blueyed)]

I cannot confirm it here, using strigi-daemon 0.5.6-0ubuntu1 (Ubuntu Gutsy).
I've also tried it on a Feisty virtual machine.

[Luke12 (luca-venturini)]

I am using that same version on a Gutsy box (sorry I did not specify it
earlier :$ ). I will try a purge followed by an install, hope it will
function...

Il Wednesday 10 October 2007 00:42:55 dAniel hAhler ha scritto:
> I cannot confirm it here, using strigi-daemon 0.5.6-0ubuntu1 (Ubuntu
> Gutsy). I've also tried it on a Feisty virtual machine.
>
> ** Changed in: clucene-core (Ubuntu)
> Status: New => Incomplete

[Luke12 (luca-venturini)]

It did not function. I do not know how else to reproduce the bug however. As I
specified I am using the 0.5.6 version on a Gutsy - and purging +
reinstallation did not solve the problem, I still receive the same console
output.

Il Wednesday 10 October 2007 21:06:14 Luke12 ha scritto:
> I am using that same version on a Gutsy box (sorry I did not specify it
> earlier :$ ). I will try a purge followed by an install, hope it will
> function...
>
> Il Wednesday 10 October 2007 00:42:55 dAniel hAhler ha scritto:
> > I cannot confirm it here, using strigi-daemon 0.5.6-0ubuntu1 (Ubuntu
> > Gutsy). I've also tried it on a Feisty virtual machine.
> >
> > ** Changed in: clucene-core (Ubuntu)
> > Status: New => Incomplete

[Tim Holy (holy-wustl)]

I don't know if it's related, but when I selected strigi for installation in the Adept installer, somehow strigi-daemon was not one of the packages that got installed. An apt-get install strigi-daemon worked for me.

I was upgrading edge->feisty->gutsy via an apt-get dist-upgrade (but strigi didn't get installed until I manually selected it after the upgrade process was complete).

[Daniel Hahler (blueyed)]

Luke, is this (or has it been) the same problem for you, too? That strigi-daemon was/is not updated accordingly?

[rusivi2 (rusivi2-deactivatedaccount)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. The version of Ubuntu your using is in End of Life status. More information may be found at: https://wiki.ubuntu.com/Releases As well, the issue that you reported should be reproducible with the live environment of the Desktop CD development release - Maverick Meerkat. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/. Please repost a detailed error report and update the bug status. Thanks again and we appreciate your help.