Bug 286017 - Authentication failed for jabber and facebook account
Summary: Authentication failed for jabber and facebook account
Status: RESOLVED NOT A BUG
Alias: None
Product: telepathy
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: git-latest
Platform: Ubuntu Linux
: NOR normal
Target Milestone: 0.4.0
Assignee: Telepathy Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-07 16:29 UTC by Robby Engelmann
Modified: 2012-07-06 12:47 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
bash script to download kde-telepathy sources and comile them (5.26 KB, text/plain)
2011-11-12 09:13 UTC, Robby Engelmann
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Robby Engelmann 2011-11-07 16:29:36 UTC
Version:           git-latest (using KDE 4.7.2) 
OS:                Linux

I set up my jabber account according to kopete settings. In kopete jabber works fine, but for kde-telepathy I am not able to connect. The same is true for facebook-chat.
On the other side, if I try to set up ICQ, I get an error message saying, that my account details are wrong.

Reproducible: Always

Steps to Reproduce:
-Create a new jabber account
-set up name like thatsme@draugr.de and your password
-put in draugr.de as server in advanced settings

Actual Results:  
-can not connect

Expected Results:  
-should be able to connect
Comment 1 Martin Klapetek 2011-11-07 16:44:58 UTC
Do you have telepathy-auth-handler installed?
Comment 2 Robby Engelmann 2011-11-07 17:01:13 UTC
There is no such package available from there: ppa:telepathy-kde/daily-builds
But I will check whether it is available on my Plasma-Active Tablet, as there I have the very same problem.
Comment 3 Martin Klapetek 2011-11-07 17:03:52 UTC
The daily builds are currently broken and I'm afraid you need this package to make it work.

There should be some openSUSE daily builds (if you're running PA on top of it), which should work just fine.
Comment 4 Robby Engelmann 2011-11-07 17:10:57 UTC
I checked the kde-telepathy website (http://community.kde.org/Real-Time_Communication_and_Collaboration/Packaging_Guide#Experimental_Components) and saw some other dependencies, that are not met in my Kubuntu Oneiric. Do you think it is worth to post the ppa-maintainer of the daily builds?
Comment 5 Frederik Schwarzer 2011-11-07 19:05:29 UTC
Not sure if it is related, but I cannot connect either. I only tried Jabber and I have telepathy-auth-handler installed from Git.

Started on a terminal it says:

telepathy-kde-contactlist(9102) MainWidget::onAccountConnectionStatusChanged: Connection status is 1
telepathy-kde-contactlist(9102) MainWidget::monitorPresence:
telepathy-kde-contactlist(9102) MainWidget::onAccountConnectionStatusChanged: Connection status is 2

Does not look too helpful, but maybe you can see something essential missing, or so?
Comment 6 Martin Klapetek 2011-11-07 19:09:32 UTC
Which Gabble version are you using?
Comment 7 Frederik Schwarzer 2011-11-07 19:20:59 UTC
0.13.7
Comment 8 Martin Klapetek 2011-11-07 19:59:29 UTC
Ok, I'll need some more debug.

Please disconnect all your accounts, close contact list and check if there is no process telepathy-gabble running. Then open a terminal and type this:

GABBLE_PERSIST=1 GABBLE_DEBUG=all /usr/libexec/telepathy-gabble

In case that says that the file does not exist, you have to find the correct telepathy-gabble path (might be /usr/bin or /usr/lib) and use that path with the command above.

Then open up the contact list and try connecting your jabber account (if possible just one). After it fails, copy the output and create an attachment here (don't use pastebins).

Also check if the log does not contain any sensitive data, if so, remove them ;)
Comment 9 Frederik Schwarzer 2011-11-07 20:32:17 UTC
I do not have that file, so I used the closest I could find.

% GABBLE_PERSIST=1 GABBLE_DEBUG=all /usr/lib/telepathy/telepathy-gabble  
(process:16223): tp-glib/proxy-DEBUG: tp_proxy_dispose: 0x830e408
(process:16223): tp-glib/proxy-DEBUG: tp_proxy_invalidate: 0x830e408: Proxy unreferenced
(process:16223): tp-glib/proxy-DEBUG: tp_proxy_finalize: 0x830e408
(process:16223): gabble-DEBUG: gabble_plugin_loader_probe (plugin-loader.c:124): probing /usr/lib/telepathy/gabble-0
** (process:16223): DEBUG: gabble_plugin_create: loaded
(process:16223): gabble-DEBUG: plugin_loader_try_to_load (plugin-loader.c:99): loaded 'Gateway registration plugin' version 0.13.7 (/usr/lib/telepathy/gabble-0/gateways.so), implementing these sidecars: org.freedesktop.Telepathy.Gabble.Plugin.Gateways
(telepathy-gabble:16223): tp-glib-DEBUG: started version 0.13.7 (telepathy-glib version 0.16.1)
Comment 10 Frederik Schwarzer 2011-11-07 20:34:05 UTC
Oops, ok, here is the output of telepathy-contact-list:

telepathy-kde-contactlist(16258) KPixmapSequence::Private::loadSequence: Invalid framesize. 
telepathy-kde-contactlist(16258) GlobalPresence::onCurrentPresenceChanged: Current presence changed
telepathy-kde-contactlist(16258) MainWidget::onAccountConnectionStatusChanged: Connection status is 1
telepathy-kde-contactlist(16258) MainWidget::monitorPresence:
telepathy-kde-contactlist(16258) MainWidget::onAccountConnectionStatusChanged: Connection status is 2

So, still the same.
Comment 11 Martin Klapetek 2011-11-07 20:48:27 UTC
I actually need the gabble output after you try to connect. Sorry if I didn't make it clear :)

So please run it again and then include the whole telepathy-gabble output. Thanks.
Comment 12 Frederik Schwarzer 2011-11-07 21:01:28 UTC
Ok, sorry, Gabble ran in another tab so I did not notice its output.

(telepathy-gabble:16407): tp-glib/params-DEBUG: tp_base_protocol_sanitize_parameters: using specified value for account: "[[user]]@jabber.org"
(telepathy-gabble:16407): gabble-DEBUG: gabble_connection_class_init (connection.c:920): Initializing (GabbleConnectionClass *)0xa1b0e98
(telepathy-gabble:16407): tp-glib/presence-DEBUG: tp_presence_mixin_class_init: called.
(telepathy-gabble:16407): gabble-DEBUG: gabble_connection_init (connection.c:519): Initializing (GabbleConnection *)0xa1b5080
(telepathy-gabble:16407): gabble-DEBUG: gabble_capabilities_init (capabilities.c:233): 0xa1b5080
(telepathy-gabble:16407): gabble-DEBUG: gabble_roomlist_manager_constructed (roomlist-manager.c:210): 0xa197600
(telepathy-gabble:16407): gabble-DEBUG: gabble_signal_connect_weak (util.c:966): connecting to 0xa1b5080:status-changed with context 0xa196dc0
(telepathy-gabble:16407): gabble-DEBUG: gabble_signal_connect_weak (util.c:966): connecting to 0xa1b5080:status-changed with context 0xa196dd0
(telepathy-gabble:16407): gabble-DEBUG: gabble_server_tls_manager_constructed (server-tls-manager.c:418): Server TLS Manager constructed
(telepathy-gabble:16407): gabble-DEBUG: gabble_signal_connect_weak (util.c:966): connecting to 0xa1b5080:status-changed with context 0xa196e60
(telepathy-gabble:16407): gabble-DEBUG: gabble_signal_connect_weak (util.c:966): connecting to 0xa1b5080:status-changed with context 0xa196e20
(telepathy-gabble:16407): gabble-DEBUG: gabble_signal_connect_weak (util.c:966): connecting to 0xa1b5080:porter-available with context 0xa196e40
(telepathy-gabble:16407): gabble-DEBUG: gabble_connection_constructor (connection.c:390): Post-construction: (GabbleConnection *)0xa1b5080
(telepathy-gabble:16407): tp-glib/presence-DEBUG: tp_presence_mixin_init: called.
(telepathy-gabble:16407): gabble-DEBUG: gabble_signal_connect_weak (util.c:966): connecting to 0xa1bb6a0:item-found with context 0xa1ba330
(telepathy-gabble:16407): gabble-DEBUG: gabble_signal_connect_weak (util.c:966): connecting to 0xa1b5080:status-changed with context 0xa196eb0
(telepathy-gabble:16407): gabble-DEBUG: gabble_connection_constructed (connection.c:502): defaulted resource to 77c6605f
(telepathy-gabble:16407): tp-glib/connection-DEBUG: tp_base_connection_register: 0xa1b5080: bus name org.freedesktop.Telepathy.Connection.gabble.jabber.[[user]]_40jabber_2eorg_2f77c6605f; object path /org/freedesktop/Telepathy/Connection/gabble/jabber/[[user]]_40jabber_2eorg_2f77c6605f
(telepathy-gabble:16407): tp-glib/connection-DEBUG: tp_presence_mixin_get_contacts_dbus_property: called.
(telepathy-gabble:16407): tp-glib/presence-DEBUG: tp_presence_mixin_get_simple_presence_dbus_property: called.
(telepathy-gabble:16407): gabble-DEBUG: gabble_connection_update_capabilities (connection.c:3393): enter
(telepathy-gabble:16407): gabble-DEBUG: gabble_presence_set_capabilities (presence.c:336): about to add caps to resource 77c6605f with serial 1
(telepathy-gabble:16407): gabble-DEBUG: gabble_presence_set_capabilities (presence.c:347): found resource 77c6605f
(telepathy-gabble:16407): gabble-DEBUG: gabble_presence_set_capabilities (presence.c:352): new serial 1, old 0, clearing caps
(telepathy-gabble:16407): gabble-DEBUG: gabble_presence_set_capabilities (presence.c:360): updating caps for resource 77c6605f
(telepathy-gabble:16407): gabble-DEBUG: gabble_connection_refresh_capabilities (connection.c:2478): not emitting self-presence stanza: not connected yet
(telepathy-gabble:16407): tp-glib/presence-DEBUG: tp_presence_mixin_simple_presence_set_presence: called.
(telepathy-gabble:16407): tp-glib/presence-DEBUG: check_for_status: Found status "available", checking if it's available...
(telepathy-gabble:16407): gabble-DEBUG: gabble_connection_update_capabilities (connection.c:3393): enter
(telepathy-gabble:16407): gabble-DEBUG: gabble_presence_set_capabilities (presence.c:336): about to add caps to resource 77c6605f with serial 2
(telepathy-gabble:16407): gabble-DEBUG: gabble_presence_set_capabilities (presence.c:347): found resource 77c6605f
(telepathy-gabble:16407): gabble-DEBUG: gabble_presence_set_capabilities (presence.c:352): new serial 2, old 1, clearing caps
(telepathy-gabble:16407): gabble-DEBUG: gabble_presence_set_capabilities (presence.c:360): updating caps for resource 77c6605f
(telepathy-gabble:16407): gabble-DEBUG: gabble_connection_refresh_capabilities (connection.c:2469): nothing to do
(telepathy-gabble:16407): gabble-DEBUG: _gabble_connection_connect (connection.c:2150): letting SRV lookup decide server and port
(telepathy-gabble:16407): gabble-DEBUG: _gabble_connection_connect (connection.c:2200): Start connecting
(telepathy-gabble:16407): tp-glib/connection-DEBUG: tp_base_connection_change_status: was 4294967295, now 1, for reason 1
(telepathy-gabble:16407): tp-glib/connection-DEBUG: tp_base_connection_change_status: emitting status-changed to 1, for reason 1
(telepathy-gabble:16407): gabble-DEBUG: connection_status_changed_cb (im-factory.c:428): adding callbacks
(telepathy-gabble:16407): gabble-DEBUG: gabble_signal_connect_weak (util.c:966): connecting to 0xa1bb6a0:item-found with context 0xa1c4910
(telepathy-gabble:16407): gabble-DEBUG: gabble_signal_connect_weak (util.c:966): connecting to 0xa1bb6a0:done with context 0xa1ba6c0
(telepathy-gabble:16407): gabble-DEBUG: connection_status_changed_cb (server-tls-manager.c:121): Connection status changed, now 1
(telepathy-gabble:16407): gabble-DEBUG: connection_status_changed_cb (muc-factory.c:945): adding callbacks
(telepathy-gabble:16407): tp-glib/connection-DEBUG: tp_presence_mixin_get_contacts_dbus_property: called.
(telepathy-gabble:16407): tp-glib/connection-DEBUG: tp_presence_mixin_get_contacts_dbus_property: called.
(telepathy-gabble:16407): gabble-DEBUG: gabble_server_tls_manager_verify_async (server-tls-manager.c:284): verify_async() called on the GabbleServerTLSManager.
(telepathy-gabble:16407): gabble-DEBUG: gabble_server_tls_channel_constructed (server-tls-channel.c:208): Server TLS channel constructed at /org/freedesktop/Telepathy/Connection/gabble/jabber/[[user]]_40jabber_2eorg_2f77c6605f/ServerTLSChannel
(telepathy-gabble:16407): tp-glib/channel-DEBUG: tp_base_channel_close_dbus: called by :1.50
(telepathy-gabble:16407): gabble-DEBUG: gabble_server_tls_channel_close (server-tls-channel.c:305): Close() called on the TLS channel 0xa19d728
(telepathy-gabble:16407): gabble-DEBUG: server_tls_channel_closed_cb (server-tls-manager.c:138): Server TLS channel closed.
(telepathy-gabble:16407): gabble-DEBUG: server_tls_channel_closed_cb (server-tls-manager.c:143): Channel closed, but unhandled, falling back...
(telepathy-gabble:16407): gabble-DEBUG: gabble_server_tls_channel_dispose (server-tls-channel.c:146): Dispose TLS channel
(telepathy-gabble:16407): gabble-DEBUG: gabble_server_tls_channel_finalize (server-tls-channel.c:129): Finalize TLS channel
(telepathy-gabble:16407): gabble-DEBUG: gabble_server_sasl_channel_start_auth_async (server-sasl-channel.c:814): Starting authentication
(telepathy-gabble:16407): tp-glib/channel-DEBUG: tp_base_channel_close_dbus: called by :1.50
(telepathy-gabble:16407): gabble-DEBUG: gabble_server_sasl_channel_close (server-sasl-channel.c:965): called on 0xa1a1960
(telepathy-gabble:16407): gabble-DEBUG: gabble_server_sasl_channel_close (server-sasl-channel.c:971): closed channel
(telepathy-gabble:16407): gabble-DEBUG: connector_error_disconnect (connection.c:1699): connection failed: WOCKY_AUTH_ERROR_FAILURE (#6): Client aborted authentication.
(telepathy-gabble:16407): tp-glib/connection-DEBUG: tp_base_connection_change_status: was 1, now 2, for reason 3
(telepathy-gabble:16407): tp-glib/connection-DEBUG: tp_base_connection_change_status: emitting status-changed to 2, for reason 3
(telepathy-gabble:16407): gabble-DEBUG: gabble_roster_close_all (roster.c:1674): closing channels
(telepathy-gabble:16407): gabble-DEBUG: gabble_im_factory_close_all (im-factory.c:410): removing callbacks
(telepathy-gabble:16407): gabble-DEBUG: connection_status_changed_cb (roomlist-manager.c:193): disconnected, closing room lists
(telepathy-gabble:16407): gabble-DEBUG: gabble_roomlist_manager_close_all (roomlist-manager.c:87): 0xa197600
(telepathy-gabble:16407): gabble-DEBUG: gabble_search_manager_close_all (search-manager.c:100): closing channels
(telepathy-gabble:16407): gabble-DEBUG: gabble_auth_manager_close_all (auth-manager.c:89): called
(telepathy-gabble:16407): gabble-DEBUG: connection_status_changed_cb (server-tls-manager.c:121): Connection status changed, now 2
(telepathy-gabble:16407): gabble-DEBUG: gabble_muc_factory_close_all (muc-factory.c:887): closing channels
(telepathy-gabble:16407): gabble-DEBUG: gabble_muc_factory_close_all (muc-factory.c:924): removing callbacks
(telepathy-gabble:16407): gabble-DEBUG: gabble_private_tubes_factory_close_all (private-tubes-factory.c:357): closing 1-1 tubes channels
(telepathy-gabble:16407): gabble-DEBUG: gabble_media_factory_close_all (media-factory.c:428): closing channels
(telepathy-gabble:16407): gabble-DEBUG: connection_shut_down (connection.c:2297): neither porter nor connector is alive: clean up the base connection
(telepathy-gabble:16407): tp-glib/params-DEBUG: connection_shutdown_finished_cb: dereferenced connection
(telepathy-gabble:16407): gabble-DEBUG: gabble_connection_dispose (connection.c:1189): called
(telepathy-gabble:16407): gabble-DEBUG: gabble_bytestream_factory_dispose (bytestream-factory.c:663): dispose called
(telepathy-gabble:16407): gabble-DEBUG: user_data_destroyed_cb (util.c:935): user_data for 0xa1ba330 destroyed; disconnecting
(telepathy-gabble:16407): gabble-DEBUG: user_data_destroyed_cb (util.c:935): user_data for 0xa196eb0 destroyed; disconnecting
(telepathy-gabble:16407): gabble-DEBUG: gabble_disco_dispose (disco.c:229): dispose called
(telepathy-gabble:16407): gabble-DEBUG: instance_destroyed_cb (util.c:922): instance for 0xa1ba6c0 destroyed; cleaning up
(telepathy-gabble:16407): gabble-DEBUG: instance_destroyed_cb (util.c:922): instance for 0xa1c4910 destroyed; cleaning up
(telepathy-gabble:16407): gabble-DEBUG: gabble_disco_finalize (disco.c:256): called with 0xa1bb6a0
(telepathy-gabble:16407): gabble-DEBUG: gabble_request_pipeline_dispose (request-pipeline.c:275): disposing request-pipeline
(telepathy-gabble:16407): gabble-DEBUG: gabble_vcard_manager_dispose (vcard-manager.c:576): 0xa1b9798
(telepathy-gabble:16407): gabble-DEBUG: gabble_vcard_manager_finalize (vcard-manager.c:607): 0xa1b9798
(telepathy-gabble:16407): gabble-DEBUG: gabble_jingle_factory_dispose (jingle-factory.c:447): dispose called
(telepathy-gabble:16407): gabble-DEBUG: user_data_destroyed_cb (util.c:935): user_data for 0xa196e20 destroyed; disconnecting
(telepathy-gabble:16407): gabble-DEBUG: user_data_destroyed_cb (util.c:935): user_data for 0xa196e40 destroyed; disconnecting
(telepathy-gabble:16407): gabble-DEBUG: gabble_presence_cache_dispose (presence-cache.c:578): dispose called
(telepathy-gabble:16407): gabble-DEBUG: gabble_presence_cache_finalize (presence-cache.c:609): called with 0xa19d4f8
(telepathy-gabble:16407): gabble-DEBUG: gabble_roster_dispose (roster.c:206): dispose called
(telepathy-gabble:16407): gabble-DEBUG: gabble_roster_close_all (roster.c:1674): closing channels
(telepathy-gabble:16407): gabble-DEBUG: gabble_roster_finalize (roster.c:238): called with 0xa1a80b8
(telepathy-gabble:16407): gabble-DEBUG: gabble_im_factory_dispose (im-factory.c:125): dispose called
(telepathy-gabble:16407): gabble-DEBUG: gabble_roomlist_manager_dispose (roomlist-manager.c:129): running
(telepathy-gabble:16407): gabble-DEBUG: gabble_roomlist_manager_close_all (roomlist-manager.c:87): 0xa197600
(telepathy-gabble:16407): gabble-DEBUG: gabble_search_manager_dispose (search-manager.c:214): dispose called
(telepathy-gabble:16407): gabble-DEBUG: gabble_search_manager_close_all (search-manager.c:100): closing channels
(telepathy-gabble:16407): gabble-DEBUG: user_data_destroyed_cb (util.c:935): user_data for 0xa196dc0 destroyed; disconnecting
(telepathy-gabble:16407): gabble-DEBUG: gabble_auth_manager_dispose (auth-manager.c:158): dispose called
(telepathy-gabble:16407): gabble-DEBUG: gabble_auth_manager_close_all (auth-manager.c:89): called
(telepathy-gabble:16407): gabble-DEBUG: user_data_destroyed_cb (util.c:935): user_data for 0xa196dd0 destroyed; disconnecting
(telepathy-gabble:16407): gabble-DEBUG: gabble_server_tls_manager_dispose (server-tls-manager.c:379): 0xa1a18b0
(telepathy-gabble:16407): gabble-DEBUG: user_data_destroyed_cb (util.c:935): user_data for 0xa196e60 destroyed; disconnecting
(telepathy-gabble:16407): gabble-DEBUG: gabble_server_tls_manager_finalize (server-tls-manager.c:397): 0xa1a18b0
(telepathy-gabble:16407): gabble-DEBUG: gabble_muc_factory_dispose (muc-factory.c:158): dispose called
(telepathy-gabble:16407): gabble-DEBUG: gabble_muc_factory_close_all (muc-factory.c:887): closing channels
(telepathy-gabble:16407): gabble-DEBUG: gabble_private_tubes_factory_dispose (private-tubes-factory.c:178): dispose called
(telepathy-gabble:16407): gabble-DEBUG: gabble_private_tubes_factory_close_all (private-tubes-factory.c:357): closing 1-1 tubes channels
(telepathy-gabble:16407): gabble-DEBUG: gabble_media_factory_dispose (media-factory.c:164): dispose called
(telepathy-gabble:16407): gabble-DEBUG: gabble_media_factory_close_all (media-factory.c:428): closing channels
(telepathy-gabble:16407): gabble-DEBUG: gabble_connection_finalize (connection.c:1262): called with 0xa1b5080
(telepathy-gabble:16407): tp-glib/connection-DEBUG: tp_contacts_mixin_finalize: 0xa1b5080
(telepathy-gabble:16407): tp-glib/presence-DEBUG: tp_presence_mixin_finalize: 0xa1b5080
(telepathy-gabble:16407): gabble-DEBUG: gabble_capabilities_finalize (capabilities.c:316): 0xa1b5080
Comment 13 Martin Klapetek 2011-11-07 21:04:28 UTC
Ok, I have an idea now. Do you have telepathy-auth-handler installed in your own prefix? Or the standard /usr?
Comment 14 Frederik Schwarzer 2011-11-07 21:45:36 UTC
These packages are installed from Debian packages:
gir1.2-telepathyglib-0.12
libtelepathy-farsight0
libtelepathy-glib0
telepathy-gabble
telepathy-mission-control-5

The following packages are compiled into an own prefix:
telepathy-auth-handler
telepathy-kded-module
telepathy-qt4
telepathy-contact-list
telepathy-presence-applet
telepathy-accounts-kcm
telepathy-filetransfer-handler
telepathy-presence-dataengine
telepathy-text-ui
Comment 15 Robby Engelmann 2011-11-07 21:59:12 UTC
is there anywhere a good description how to compile all these packages by his own?
Comment 16 Martin Klapetek 2011-11-07 22:00:21 UTC
(In reply to comment #14)

 Ok, then check your custom prefix for share/dbus-1/* files and copy/link them to /usr/share/dbus-1/ and it should start working immediately.

The problem is that these are dbus activation files and dbus cannot find them and thus won't run the necessary services. You wouldn't be able to chat too, btw.
Comment 17 Martin Klapetek 2011-11-07 22:04:17 UTC
(In reply to comment #15)
> is there anywhere a good description how to compile all these packages by his
> own?

See http://community.kde.org/Real-Time_Communication_and_Collaboration/Getting_Set_Up

There is also a script for automated setup. While compiling your own stuff, please beware the dbus files mentioned in previous comment.
Comment 18 Frederik Schwarzer 2011-11-08 02:34:57 UTC
(In reply to comment #16)
> (In reply to comment #14)
> 
>  Ok, then check your custom prefix for share/dbus-1/* files and copy/link them
> to /usr/share/dbus-1/ and it should start working immediately.

If with "immediately" you mean "after a KDE restart", then yes. :)

> The problem is that these are dbus activation files and dbus cannot find them
> and thus won't run the necessary services. You wouldn't be able to chat too,
> btw.

I thought a /etc/dbus-1/session.local.conf with the following content would also do the trick, but it seems it does not. :(

<!DOCTYPE busconfig PUBLIC "-//freedesktop//DTD D-Bus Bus Configuration 1.0//EN"
"http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd">
<busconfig>
        <servicedir>/home/fs/usr/share/dbus-1/services/</servicedir>
</busconfig>


Thanks for your help.
Comment 19 Martin Klapetek 2011-11-08 09:27:37 UTC
Anytime :)

Robby, did you manage to solve your connection problems as well?
Comment 20 Robby Engelmann 2011-11-08 10:45:07 UTC
I had no time to give it a real try. I tried the script from the page you pointed my at, but there are some dependencies missing, that I could not find (telepathy-glib and another other one, in order to compile telepathy-qt4).
I am thinking of waiting until the ppa works again for ubuntu. For my PA-Wetab I did not check up to now. I will let you know here...

thanx for the advices :-)
Comment 21 Martin Klapetek 2011-11-08 10:48:47 UTC
Ok, I'm closing this bug now as it may be safely assumed, you had the same problem with auth-handler.

If this problem persist, feel free to reopen this bug or join #kde-telepathy on irc.freenode.net and we'll help you set up.

As for the ICQ issue, that's a different one and I think it should be solved in the latest code. If you'll see this problem too, please file a separate bug report.

Thanks :)
Comment 22 Robby Engelmann 2011-11-12 09:13:28 UTC
Created attachment 65542 [details]
bash script to download kde-telepathy sources and comile them
Comment 23 Robby Engelmann 2011-11-12 09:14:51 UTC
Using this script all worked fine after installing some missing dev-packages