KTp/Troubleshooting: Difference between revisions
| Line 31: | Line 31: | ||
If you have installed it since starting a telepathy component there is a good chance that the daemon (mission-control) will have started, any channel handlers installed since then are not recognised. | If you have installed it since starting a telepathy component there is a good chance that the daemon (mission-control) will have started, any channel handlers installed since then are not recognised. | ||
Simply log out and back in again to fix it (or restart mission-control-5) | Simply log out and back in again to fix it (or restart mission-control-5)''' | ||
'''Note:''' After you perform any of the above troubleshooting steps, it is necessary to restart mission-control-5( you can do this by killing the already running mission-control-5 process and then starting it from /usr/lib/telepathy/mission-control-5). | |||
====When I click on available accounts, I get an empty list==== | ====When I click on available accounts, I get an empty list==== | ||
Revision as of 16:18, 15 June 2011
TroubleShooting
I see the error message "--> tp-qt4 0.5.14 WARN: GetAll(AccountManager) failed with "org.freedesktop.DBus.Error.ServiceUnknown"
You have not installed all the dependencies correctly. KDE Telepathy relies on a daemon to be running called telepathy-mission-control-5. This should be available in your package manager already. You will also probably want telepathy-gabble, telepathy-butterfly, telepathy-haze which provide access to jabber/MSN/libpurple respectively.
My passwords aren't being saved.
You need to install gnome-keyring.
Q: Gnome Keyring???
Yes, it's not KDE that saves the passwords that's done by our backend daemon (telepathy) therefore it's the solution that makes sense.
Q: Something Something KWallet?
We have no plans to support it, it's not a viable thing to do. However: Gnome and KDE people are working on a shared storage solution called secretservice.
Nothing happens when I try and start a chat with someone from the contact list.
It could be one of three causes.
Have you installed the telepathy-chat-handler? If not install it.
Do you compile and install your programs to a non standard directory (anywhere but /usr)? The chat-handler (like other parts of Telepathy) is Dbus activated, when the dbus method is called dbus itself finds the correct application to handle it and launches it. However it cannot do this if dbus does not know about the application. You need to make sure the files in yourinstalldir/share/dbus-1/services/* is copied to /usr/share/dbus-1/services.
If you have installed it since starting a telepathy component there is a good chance that the daemon (mission-control) will have started, any channel handlers installed since then are not recognised. Simply log out and back in again to fix it (or restart mission-control-5)
Note: After you perform any of the above troubleshooting steps, it is necessary to restart mission-control-5( you can do this by killing the already running mission-control-5 process and then starting it from /usr/lib/telepathy/mission-control-5).
When I click on available accounts, I get an empty list
You need to install a 'connection manager'. These are upstream telepathy components that talk to the various IM networks. They should be available from your distribution.
You need.
Jabber/Gmail/Facebook : Telepathy-gabble MSN: Telepathy-butterfly + Plenty more.