When using soprano 2.4.0, krunner won't start up properly. There are two instances of "kdeinit4 krunner" hanging. Also .xsession-error shows a dbus error that no reply was received. Killing both instances and starting krunner manually fixes the situation for that session. Also, starting KDE feels more sluggish. It takes a few seconds after the desktop appear until kmail starts asking for my kwallet password... whereas w/ 2.3.73 it is there almost right away. Downgrading to 2.3.73 fixes the situation. krunner starts fine and things start up a lot "speedier". Reproducible: Always
If you don't need the nepomuk-runner disable it. This solves the not working krunner-issue for me.
I can confirm this problem - with soprano 2.4.0, krunner, dolphin, nepomuk are not running, logging out takes a lot of time. Upgrading to nepomuk-9999 (kde overlay) didn't solve the problem. What do you mean with disabling "nepomuk-runner", where's that option?
> What do you mean with disabling "nepomuk-runner", where's that option? > $ killall -9 krunner $ krunner & Then Alt + F2 (open krunner) -> configure -> unselect the "Nepomuk Desktop Search runner" I do not have those problems dolphin, so this "fix" only concerns KRunner. Did you guys do the upgrade to virtoso-DB? .kde4/share/config/nepomukserverrc set -> Used Soprano Backend=virtuosobackend The previous default backend was the Sesame2-Backend. With Sesame2 still set nepomuk won't work! After changing this, stop nepomuk and start it again. I don't know the exact dbus-call, but logging out and in again should do the job, too ;)
Using soprano 2.4.0, killing krunner and starting it again (as you describe it) doesn't work in my case: benson@cupra ~ $ Connecting to deprecated signalQDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) krunner(10094) SaverEngine::applyManualSettings: no lock krunner(10094) SaverEngine::applyManualSettings: no lock krunner(10094) SaverEngine::applyManualSettings: no lock krunner(10094) SaverEngine::applyManualSettings: no lock krunner(10094) SaverEngine::enable: Saver Engine started, timeout: 420 krunner(10094)/kdecore (KSycoca) KSycocaPrivate::openDatabase: Trying to open ksycoca from "/var/tmp/kdecache-benson/ksycoca4" krunner(10094)/libplasma Plasma::RunnerManagerPrivate::loadRunners: ================= loading runner: "Webbrowser-Verlauf" ================= krunner(10094)/libplasma Plasma::RunnerManagerPrivate::loadRunners: ================= loading runner: "Befehlszeile" ================= krunner(10094)/libplasma Plasma::RunnerManagerPrivate::loadRunners: ================= loading runner: "Plasma-Umgebung" ================= krunner(10094)/libplasma Plasma::RunnerManagerPrivate::loadRunners: ================= loading runner: "Medienwiedergabe steuern" ================= krunner(10094)/libplasma Plasma::RunnerManagerPrivate::loadRunners: ================= loading runner: "Nepomuk-Desktopsuche" ================= "/usr/bin/krunner(10094)" Error in thread 140378591033248 : "org.freedesktop.DBus.Error.ServiceUnknown - The name org.kde.nepomuk.services.nepomukstorage was not provided by any .service files" krunner(10094)/nepomuk (library) <unnamed>::GlobalModelContainer::init: Connecting to local socket "/home/benson/.kde4/share/apps/nepomuk/socket" "/usr/bin/krunner(10094)" Error in thread 140378591033248 : "QLocalSocket::connectToServer: Invalid name" QMutex::unlock: mutex lock failure: <unknown program name>(10093)/: Communication problem with "krunner" , it probably crashed. Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." " So i had to downgrade soprano, uncheck "Nepomuk Desktop Search runner", and upgrade to 2.4.0... I've changed the backend in nepomukserverrc and restarted nepomuk with this command: $ kdeinit4 nepomukserver Seems to be running so far.
sorry to bug you again - programs like dolphin or kmail/kontat are still not working... i'm downgrading soprano till this gets fixed...
I have a feeling this is an upstream bug since there is a problem in Arch as well. For kmail users, you have to edit the kill commands to: $ killall krunner $ killall kmail $ krunner & in order for kmail to work properly. I would assume you can add kontact and other problem apps to that list, problem apps being anything requiring soprano/anakondi/virtuoso. Soprano-2.3.x causes bigger problems with KDE 4.4 IMO, with that nepomuk/strigi may seem like it's working but it's not actually indexing any files so you have to choose which route you want to take (soprano 2.3 vs 2.4). Perhaps using soprano-2.3.x with a virtuoso-6 backend may work, as KDE requires virtuoso-6 though I haven't tried it since I'm fine with my 3 line fix.
(In reply to comment #6) > Soprano-2.3.x causes bigger problems with KDE 4.4 IMO, with that nepomuk/strigi > may seem like it's working but it's not actually indexing any files so you have > to choose which route you want to take (soprano 2.3 vs 2.4). soprano-2.3.73 is perfectly working and fixes all the issue we get with 2.4.0 (and has all the new features needed by kde-4.4). You can get it from attic in CVS portage tree while waiting for a 2.4.0 fix. http://sources.gentoo.org/viewcvs.py/*checkout*/gentoo-x86/dev-libs/soprano/soprano-2.3.73.ebuild?rev=1.1
I upgraded to kde-4.4.0 before the soprano-2.4.0 update was available, here, so have everything built against soprano-2.3.73. I've seen no issues. Seeing this problem on the kde lists, I decided to locally package.mask 2.4.0 and stick with the 2.3.73 I have until this gets resolved. FWIW, here's a link to the kde-general list thread (it's not just Gentoo, as already mentioned in comment #6) on gmane, which will in turn link back here as soon as I post the followup I'm composing for it. http://comments.gmane.org/gmane.comp.kde.general/22683
https://bugs.kde.org/show_bug.cgi?id=226218#c2
+*soprano-2.4.0-r1 (11 Feb 2010) + + 11 Feb 2010; Samuli Suominen <ssuominen@gentoo.org> + +soprano-2.4.0-r1.ebuild, +files/soprano-2.4.0-socketMutex.unlock.patch: + Apply upstream "unlock the mutex before deleting it" patch. Also, 2.4.0.1 should be out soon. Let me know if things improve with this.
Shortly after the release of 2.4.0.1, there appeared soprano-2.4.0-r1.ebuild, applying the patch. :D Great to see such a fast fix!
The patch seems to work fine here. Thanks!
Confirm too : 2.4.0-r1 fixes the issue Thanks !
ok, thanks for verifying, closing then
*** Bug 304331 has been marked as a duplicate of this bug. ***
*** Bug 304749 has been marked as a duplicate of this bug. ***
*** Bug 304371 has been marked as a duplicate of this bug. ***
