Upgrade to latest TpQt4.
Note: qdbus-qt4 on your system may be qdbus
This shouldn't be an issue, but apparently has come up. It is a critical bug in Nepomuk.
qdbus-qt4 org.kde.nepomuk.services.nepomukontologyloader /nepomukontologyloader org.kde.nepomuk.OntologyManager.updateAllLocalOntologies
Option1: turn off Nepomuk. restart contact list
Option2: rm /usr/share/kde4/services/nepomuktelepathyservice.desktop log out + log in
Do you use Ubuntu? If so look in ~/.cache for a folder called dconf. If it doesn't exist create it.
It's a bug in Ubuntu's packaging of a shared component, please pester someone about this: https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/939126
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 and telepathy-haze which provide access to jabber and libpurple(MSN, ICQ etc) respectively.
Make sure you have telepathy-auth-handler installed.
Do you have Empathy installed? If so remove it.
Also check all the steps in the following section.
It could be one of three causes.
Have you installed the telepathy-text-ui? If not install it.
Do you compile and install your programs to a non standard directory (anywhere but /usr)? The text-ui (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.
Therefore, 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 or /usr/lib/mission-control-5).
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.
Jabber/Gmail/Facebook : Telepathy-gabble
+ Plenty more.
You need to check if your avatar (user picture) is small enough. Maximum file size allowed is 8192 bytes, maximum allowed dimensions for avatars are 96x96.
We switched the library we use for MSN, make sure you have telepathy-haze installed, delete your MSN account and add it again. If you are up to date it will now use Haze as a backend.
Microsoft is pushing all users over to Skype for instant messaging, so access via the XMPP protocol is not possible after October 2013, and access via the MSP protocol is not possible after March 2014.
Source: Microsoft statement via Telepathy mailing list (archive)
This is a known bug in kde and the way in which dbus-activated applications start.
Run qtconfig (or qtconfig-qt4 in some distros) and in the first tab select the oxygen style (or whatever style you are using in kde) then save the changes and exit.
Alternatively, if you don't have qtconfig, edit ~/.config/Trolltech.conf, look for the [qt] section (and if there is none, create one) and add or change the "Style" variable like this:
[qt] ... Style=Oxygen ...
You can replace oxygen with your favourite style.
GABBLE_LOGFILE=/tmp/gabble.log GABBLE_PERSIST=1 GABBLE_DEBUG=all G_MESSAGES_DEBUG=all /usr/lib/telepathy-gabble
the executable may be in a different path
start kdebugdialog and be sure that kded4 is activated, then kquitapp kded ; sleep 2; kded4 check for errors in ~/.xsession-errors
You need telepathy-gabble >= 0.16.1