(Can someone make Planet KDE not show my old now-edited articles on top? Thanks)
Today our whole KDE Telepathy project was ported to Telepathy-Qt4 0.9, which is not backwards compatible. That means that for all KDE Telepathy code cloned from master today onwards, you need to update your Telepathy-Qt4 library to version 0.9 or newer first, otherwise it won't compile.
The released version 0.2 on the other hand needs Telepathy-Qt4 < 0.9, it won't work with version 0.9 and newer. So before posting bugs about not being able to compile our software set, please check if you're using the correct version of Telepathy-Qt4 library.
Some more about bugs and how to properly report them for KDE Telepathy. Our small project is still to be considered somewhere around alpha quality. There are bugs. Quite often we receive bug reports like "I can't connect". This really does not help us to see where the problem is. When you have connectivity issues, we need to know _exactly_ what's going on inside your Telepathy installation. And it's very easy to provide us with such info.
Here are the needed steps:
- Disconnect all accounts
- Disable all accounts in System Settings and leave only the one failing
- Make sure no process named telepathy-* is running, if it is, kill it
- The following step is different for different accounts:
- If you're using Jabber, GTalk or Facebook chat, put this line in terminal:
GABBLE_PERSIST=1 GABBLE_DEBUG=all /usr/lib/telepathy-gabble 2>&1 > ~/gabble.log
- If you're using MSN, AIM, ICQ, Yahoo! account or others, use this:
HAZE_PERSIST=1 HAZE_DEBUG=all /usr/lib/telepathy-haze 2>&1 > ~/haze.log
If it says that the file does not exist, please find your telepathy-gabble/telepathy-haze and replace the path with it. This will create the log file in your home directory, named either gabble.log or haze.log.
- Now connect.
- After you have obtained the log, please check it for sensitive data. If there are none, provide it to KDE Telepathy developers (either attach it to bugzilla or use paste.kde.org and post the link to developers in some other way)
So before you go to file a bug saying "I can't connect", be sure to have one (or both) logfiles ready and attach them with as much info as you can provide - which account is failing (the network name is enough, eg. gtalk, icq, yahoo etc), does it fail to connect every time (try connecting 10 times in a row), what are you using to connect (plasmoid, contact list etc) and which error exactly are you getting. Also very helpful is including your telepathy-* packages versions. These things will help us enormously to pinpoint your problem very quickly and possibly fix it.
As for other news from KDE Telepathy land - 0.3 release is quite near, it still won't have Nepomuk integration (but this is closer than ever), quite probably no audio/video call features (but there's still hope) and maybe (just maybe) also chatting right from Plasma!
We could still use some hands, so if you find yourself bored and with nothing to do (like, if you've finished Skyrim), just storm #kde-telepathy on freenode and we'll get you started (and you don't have to know C++/Qt4).