nepomukserver still doesn't have sesame2 backend

Bug #277032 reported by humufr
32
This bug affects 4 people
Affects Status Importance Assigned to Milestone
soprano (Debian)
Fix Released
Unknown
soprano (Ubuntu)
Fix Released
Wishlist
Unassigned
Declined for Intrepid by Harald Sitter

Bug Description

The nepomukserver which is part of kdebase-runtime does still miss the sesame2 backend and so it's very slow. The problem of the high CPU load and that kde4 is very very very slow on kubuntu (still valid with Intrepid unfortunatly) is strigi and yes it's not started by default but why not remove it completely it's no use without this backend.

https://bugs.kde.org/show_bug.cgi?id=161380

sopranocmd --help

--backend The backend to use when accessing a storage directly and not via the Soprano server.
                       Possible backends are:
                       redland

Changed in kdebase-runtime:
importance: Undecided → Wishlist
Revision history for this message
humufr (humufr-deactivatedaccount) wrote :

no chance to have it in intrepid?

Revision history for this message
Harald Sitter (apachelogger) wrote :

No.

Revision history for this message
humufr (humufr-deactivatedaccount) wrote :

and for Jaunty are you evaluated to do the change or it's pretty sure that you'll keep redland?

Revision history for this message
humufr (humufr-deactivatedaccount) wrote :

it's seems for the first alpha of jaunty that nothing change so I don't think that this backend will be there in jaunty neither.

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

It won't be included until they stop distributing binary blobs (non-free software) in the sesame backend.

Revision history for this message
humufr (humufr-deactivatedaccount) wrote :

How sesame2 can be DFSG compliant and have non free blob?

http://<email address hidden>/msg21273.html

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Obviously wrong, as it was re-added in 2.1:

soprano (2.1+dfsg.1-1) unstable; urgency=low
   * New upstream release.

   +++ Changes by Modestas Vainius:

   * Bump shlibs to 2.1.
   * Add myself to uploaders.
   * Update debian/copyright.
   * Add prune-nonfree debian/rules target as a helper to get rid of jars and
     *.class files inside the tarball.
   * Add dfsg suffix to the original tarball name. It was pruned.

 -- Debian Qt/KDE Maintainers <email address hidden> Wed, 23 Jul 2008 17:26:55 +0300

Revision history for this message
humufr (humufr-deactivatedaccount) wrote :

If I'm reading this page correctly:

http://www.openrdf.com/license.jsp

sesame2 is under BSD-like license so how that can be non-free software?

Revision history for this message
humufr (humufr-deactivatedaccount) wrote :

I have another question. What will kubuntu people do to correct the behavior of the kde bug (present in kubuntu naturally) https://bugs.kde.org/show_bug.cgi?id=161380 ?

With redland, cpu and hard drive space is used a lot for nothing because the indexation nevere ended and after a 3 Gigs of hard drive (on a 10 gig home partition) used by strigi I prefer to delete it and stop completely the process. So if I resume the situation right now:

- redland is not usable (optimazation problem)
- sesame2 can't be provide (license problem)

Because of this:
nepomuk and strigi are completely useless.

So perhaps they must be remove. Naturally that means that one of the coolest feature of KDE4 (semantic desktop) can't be provide. And so what to replace strigi to have a little bit of modern desktop search? Tracker, beagle or another one?

Revision history for this message
Michael Blakeley (mike+ubuntu) wrote :

With intrepid + http://ppa.launchpad.net/kubuntu-experimental/ubuntu (KDE 4.2 Beta 1), the bad performance is gone - because strigi-daemon refuses to run altogether.

$ grep -i strigi ~/.xsession-errors
[/usr/bin/nepomukservicestub] nepomukstrigiservice(29566) Nepomuk::StrigiService::StrigiService: Will not start when using redland Soprano backend due to horrible performance.
NepomukServer(32234) Nepomuk::ServiceController::slotServiceInitialized: Failedto initialize service "nepomukstrigiservice"
nepomukstrigiservice(29713) Nepomuk::StrigiService::StrigiService: Failed to load sopranobackend Strigi index manager.
NepomukServer(32234) Nepomuk::ServiceController::slotServiceInitialized: Failedto initialize service "nepomukstrigiservice"
NepomukServer(32234) Nepomuk::ServiceController::slotProcessFinished: Service "nepomukstrigiservice" went down

$ apt-show-versions strigi-daemon
strigi-daemon/unknown uptodate 0.5.11-2ubuntu1~intrepid1~ppa1
$ apt-show-versions soprano-daemon
soprano-daemon/unknown uptodate 2.1.64+dfsg.1-0ubuntu1~intrepid1~ppa1

Would it make sense to move soprano-daemon to non-free?

Revision history for this message
humufr (humufr-deactivatedaccount) wrote :

I think that kubuntu decide to use less disk space on the hard drive. They will remove everything linked to soprano and so nepomuk. Because I don't see the logic to keep of this things that will never be used in KDE since 4.2...

<i>KDE 4.2 will disable strigi when using the redland backend because it is unusable slow for that.</i>

http://linux.derkeiler.com/Mailing-Lists/KDE/2008-09/msg00202.html

Revision history for this message
Luis Silva (lacsilva) wrote :

the sesame2 backend for soprano just entered the repos.

Changed in soprano:
status: New → Fix Released
Revision history for this message
Russ Brown (pickscrape) wrote :

Apologies if I'm being a bit thick here, but how do I go about telling it to use the sesame2 backend? Everything I've tried so far has resulted in it going back to redland (and yes, I have installed it, just don't know what to do next).

Changed in soprano:
status: Unknown → Confirmed
Revision history for this message
Daniel Hahler (blueyed) wrote :

Russ, try installing soprano-backend-sesame (which is there in Karmic at least).

Changed in soprano (Debian):
status: Confirmed → Won't Fix
Changed in soprano (Debian):
status: Won't Fix → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.