| View previous topic :: View next topic |
| Author |
Message |
philip
Guru
Joined: 10 Jun 2003
Posts: 404
Location: Sweden
|
 Posted: Fri Jun 22, 2012 10:34 am Post subject: session D-Bus connection created before QCoreApplication |
 |
|
Several of my KDE applications (kmail, dolphin, ...) do not launch.
Example kmail:
| Code: | $ kmail
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave |
Two instances of kmail (PID 4452 and 4453) seem to be launched if looking at System Activity, while virtuoso-t is drawing 100% CPU power continoulsy, looking at top. But no application appear in the KDE windows environment.
| Quote: | | 3264 philip 39 19 817m 800m 7164 S 100 4.9 26:18.97 virtuoso-t |
I have searched the web for a root casue but have not really found anything that seem to lead to a solution.
My versions of SW:
| Quote: | kde-base/kdebase-meta
Latest version available: 4.8.3
Latest version installed: 4.8.3 |
| Quote: | kde-base/kmail
Latest version available: 4.8.3
Latest version installed: 4.8.3 |
| Quote: | dev-db/virtuoso-server
Latest version available: 6.1.4-r1
Latest version installed: 6.1.4-r1 |
_________________
/Phil
Last edited by philip on Tue Jun 26, 2012 9:04 pm; edited 1 time in total |
|
| Back to top |
|
 |
franzf
Advocate
Joined: 29 Mar 2005
Posts: 3562
Location: Irgendwo im Nirgendwo
|
| Posted: Fri Jun 22, 2012 11:09 am Post subject: |
|
|
What does
| Code: | | qdbus org.kde.nepomuk.services.nepomukqueryservice |
print, when virtuoso-t uses 100% of the cpu?
_________________
"der mac dennoch wesen geil"
Wolfram von Eschenbach, Parzival (Buch 1, Z. 7).
Ein frühes Statement gegen Windows.
My overlay |
|
| Back to top |
|
|
philip
Guru
Joined: 10 Jun 2003
Posts: 404
Location: Sweden
|
| Posted: Fri Jun 22, 2012 2:31 pm Post subject: |
|
|
This:
| Quote: | # qdbus org.kde.nepomuk.services.nepomukqueryservice
Could not connect to D-Bus server: 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. |
_________________
/Phil |
|
| Back to top |
|
|
Cynede
n00b
Joined: 30 Nov 2012
Posts: 20
|
| Posted: Mon Dec 03, 2012 6:05 am Post subject: |
|
|
Same here.
_________________
“Pain is inevitable. Suffering is optional.” ― Haruki Murakami, What I Talk About When I Talk About Running |
|
| Back to top |
|
|
|
Desktop Environments
