Out of source compilation of Telepathy-Qt4 finishes and when I run the roster example it does not show any contacts. It was done on Linux vtheman-nb 2.6.35.11-83.fc14.x86_64 #1 SMP Mon Feb 7 07:06:44 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux And the output by TP is tp-qt4 0.5.7 DEBUG: Creating new DBusProxy tp-qt4 0.5.7 DEBUG: Creating new ConnectionManager: "org.freedesktop.Telepathy.ConnectionManager.gabble" tp-qt4 0.5.7 DEBUG: ReadinessHelper: new supportedStatuses = QSet(0) tp-qt4 0.5.7 DEBUG: ReadinessHelper: new supportedFeatures = QSet(QPair("Tp::ConnectionManager",0) ) tp-qt4 0.5.7 DEBUG: parsing manager file "/usr/share/telepathy/managers/gabble.manager" tp-qt4 0.5.7 DEBUG: ReadinessHelper::setIntrospectCompleted: feature: QPair("Tp::ConnectionManager",0) - success: true CM ready tp-qt4 0.5.7 DEBUG: Got reply to ConnectionManager.CreateConnection - bus name: "org.freedesktop.Telepathy.Connection.gabble.jabber.vtheman_40jabbim_2ecz_2f94ccd878" - object path: "/org/freedesktop/Telepathy/Connection/gabble/jabber/vtheman_40jabbim_2ecz_2f94ccd878" tp-qt4 0.5.7 DEBUG: Creating new DBusProxy tp-qt4 0.5.7 DEBUG: Connecting to ConnectionError() tp-qt4 0.5.7 DEBUG: Connecting to StatusChanged() tp-qt4 0.5.7 DEBUG: Connecting to SelfHandleChanged() tp-qt4 0.5.7 DEBUG: Creating new HandleContext for "/org/freedesktop/Telepathy/Connection/gabble/jabber/vtheman_40jabbim_2ecz_2f94ccd878" tp-qt4 0.5.7 DEBUG: ReadinessHelper: new supportedStatuses = QSet(0, 4294967295, 2) tp-qt4 0.5.7 DEBUG: ReadinessHelper: new supportedFeatures = QSet(QPair("Tp::Connection",6) , QPair("Tp::Connection",5) , QPair("Tp::Connection",4) , QPair("Tp::Connection",2) , QPair("Tp::Connection",1) , QPair("Tp::Connection",0) ) tp-qt4 0.5.7 DEBUG: Inserting to factory cache proxy for QPair(":1.166","/org/freedesktop/Telepathy/Connection/gabble/jabber/vtheman_40jabbim_2ecz_2f94ccd878") tp-qt4 0.5.7 DEBUG: New connection "/org/freedesktop/Telepathy/Connection/gabble/jabber/vtheman_40jabbim_2ecz_2f94ccd878" built Connection created tp-qt4 0.5.7 DEBUG: StatusChanged from 4294967295 to 1 with reason 1 I tried also on virtual Ubuntu 10.10 with the same result, as well as on another fedora 14. Always with same result.
The last debug line indicates the connection having moved to the Connecting status. In case it just stays there, either network error, or we're supplying insufficient parameters to the CM and it's expecting SASL authentication through an authentication channel to supply the password. In any case, yes, this is a bug in the example.
Andre has updated the roster example recently, and what we have now in master seems to work.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.