On Thu, Apr 15, 2010 at 2:01 PM, Jim Cunning wrote:
> I have KDE 4.4.2 installed on an AMD64 system. On login, I get the popup
> "Nepomuk was not able to find the configured database backend 'sesame2'.
> Existing data can thus not be"
>
> I have installed:
> jlc64 ~ # eix -I nepomuk
> [D] kde-base/nepomuk
> Available versions: (4.2) ~4.2.4
> {debug kdeprefix}
> Installed versions: 4.4.2(4.4)(12:08:59 AM 04/13/2010)(handbook -aqua -
> debug -kdeenablefinal -kdeprefix)
> [D] dev-libs/soprano
> Available versions: ~2.0.2!t ~2.1.1 ~2.2 ~2.2.1 ~2.2.1-r1 ~2.2.2
> {clucene dbus debug doc elibc_FreeBSD java raptor redland sesame2}
> Installed versions: 2.4.1(09:20:36 PM 04/12/2010)(dbus raptor redland
> virtuoso -clucene -debug -doc -elibc_FreeBSD -java)
>
> The config file .kde4/share/config/nepomukserverrc contains the line:
>
> Used Soprano Backend=sesame2
>
> There doesn't appear to be a sesame2 backend plugin installed for soprano,
> only redland and virtuoso, but changing the "sesame2" in the config file to
> "virtuoso" only changes the name of the backend in the failure message, not
> the failure.
>
> A search of the list archive shows several posts regarding this sort of error
> message, but apparently relating to nepomuk 4.4 on a KDE 4.3 system. My
> situation seems different and the solutions suggested don't apply.
>
> Any advice would be appreciated.
> --
> Jim
>
So if I'm clear about this, you have a stable AMD64 system with ~AMD64 KDE?
If you upgraded from KDE 4.3 did you try deleting all the old KDE
configuration stuff and starting new? I've not had your problems with
nepomuk but I run either AMD64 with just a couple of ~AMD64 packages,
or full ~AMD64. I haven't seen this problem on either system. However
I do run ~AMD64 portage, sandbox, gentoolkit, eix and a few other
installation things on all my systems so possibly that's part of it.
Good luck,
Mark
