Hi,

I cannot seem to connect to any account since some weeks ago. I am running Debian sid, but apparently the problem is not reproducible everywhere, so it might or might not be an issue with Debian unstable.

Versions of related packages:

kde-telepathy 15.08.2
kaccounts-integration 15.08.1

I can add XMPP accounts, but connecting to them just makes KDE Telepathy say I am available, but it does not load a roster or anything. I also have to enter passwords over and over again, despite checking "Save passwrd".

Any hints?

Cheers,
Nik

Hi,

How recently did you upgrade?

Is this with a newly created account, or an account from a migration from KTP 0.9 to KTP 15.08?

Diane

Hi,

detrout wrote:How recently did you upgrade?

The last update I did was today, but this problem persists since a few months I think. I just didn't care about it before. But since there is an annoying bug with the i915 display driver, Plasma 5 and GTK applications which doesn't leave me with Gajim anymore either, I will have to fix KDE Tekepathy now .

detrout wrote:Is this with a newly created account, or an account from a migration from KTP 0.9 to KTP 15.08?

Both. It stopped working with the existing accounts, so I deleted and recreated them, but to no avail.

I suppose this has something to do with the migration to KAccounts or so?

-nik

Natureshadow wrote:I suppose this has something to do with the migration to KAccounts or so?

Or me forgetting to list a dependency... This is the list of all the packages needed. Unfortunately its by source package name and not binary name.

* kaccounts

signond
signon-kwallet-extension
signon-plugin-oauth2
libsignon-glib
libaccounts-glib
libaccounts-qt
kaccounts-integration
kaccounts-providers
signon-ui

* ktp

telepathy-qt
telepathy-logger-qt
telepathy-accounts-signon
ktp-common-internals
ktp-accounts-kcm
ktp-approver
ktp-auth-handler
ktp-common-internals
ktp-contact-list
ktp-contact-runner
ktp-desktop-applets
ktp-filetransfer-handler
ktp-kded-integration-module
ktp-send-file
ktp-text-ui

A big one to check is to make sure telepathy-accounts-signon is installed. you can use ag-tool from
libaccounts-glib-tools to see if the accounts are created correctly, and mc-tool from telepathy-mission-control-5 to check the IM account information.

E.g. on computer

"mc-tool list" shows resources like:
gabble/jabber/google_2dim_16
gabble/jabber/ktp_2djabber_2dim_15
gabble/jabber/ktp_2djabber_2dim_17

and "ag-tool list-accounts" shows:

ID Provider Name
-- -------- ----
17 ktp-jabber <redacted>
16 google <redacted>
15 ktp-jabber <redacted>

Odds are its something about the bridge between kaccounts and telepathy that's missing.

Diane

Hi,

Code: Select all

dgeorg@portux ~ % ag-tool list-providers

Provider Name
-------------
ktp-haze-icq
ktp-gadugadu
ktp-sipe-haze
ktp-kde-talk
ktp-haze-yahoo
ktp-haze-sametime
ktp-sipe
ktp-generic
ktp-morse-telegram
ktp-jabber
ktp-haze-aim
google

dgeorg@portux ~ % ag-tool list-enabled
ID         Provider                       Name
--         --------                       ----
7          ktp-jabber                     nik@naturalnet.de
6          ktp-jabber                     dgeorg@info.tarent.de
5          ktp-jabber                     nik@mercurius.teckids.org
4          ktp-jabber                     nik@naturalnet.de

dgeorg@portux ~ % ag-tool list-settings 4
auth/method =
username = dgeorg@info.tarent.de
auth/mechanism =
CredentialsId = 7
enabled = true
name = nik@naturalnet.de
                ktp-jabber-im
telepathy/param-account = nik@naturalnet.de
telepathy/AutomaticPresence = 0;;;
telepathy/mc-account-name = gabble/jabber/ktp_2djabber_2dim_4
enabled = true
telepathy/manager = gabble
telepathy/protocol = jabber
auth/mechanism = password
auth/method = password


What strikes me as odd is that there are two accounts for nik@naturalnet.de (I see only two in the GUI), and that it apparently got mixed with the dgeorg@info.tarent.de account.

Code: Select all

gabble/jabber/dgeorg_40info_2etarent_2ede0
gabble/jabber/ktp_2djabber_2dim_4
gabble/jabber/ktp_2djabber_2dim_5
gabble/jabber/ktp_2djabber_2dim_6
gabble/jabber/ktp_2djabber_2dim_7
gabble/jabber/nik_40mercurius_2eteckids_2eorg0
gabble/jabber/nik_40naturalnet_2ede0
salut/local_xmpp/account0


mc-tool lists a myriad of other, unknown accounts.

-nik

I deleted all the accounts, both in mc-tool and ag-tool, and recreated them from the GUI, which kind of worked. It fixed two accounts, but the third one remains broken (it even crashes the server thread in ejabberd, so I am not sure where the issue comes from ).

I see ejabberd on the server crash in an OAuth routine, but I do not see this for other clients. Is OAuth implemented in KTp?

-nik

Natureshadow wrote:I see ejabberd on the server crash in an OAuth routine, but I do not see this for other clients. Is OAuth implemented in KTp?

It should be. The current Google account support uses it. Is signon-ui-x11 and signon-plugin-oauth2 installed?

Diane

Yes, both.

Never mind that, I am pretty sure this is an ejabberd bug.

Let's concentrate on why the accounts got duplicated and mixed up .

(However, I really do not want to use OAuth in the account. Can I make KTp not use it?)

-nik

I think the configuration file that switches google to oauth is in /usr/share/accounts/providers/google.provider (provided by package kaccounts-providers).

Changing that might allow you to turn off oauth, though I'd strongly recommend backing up any files before altering them.

detrout wrote:I think the configuration file that switches google to oauth is in /usr/share/accounts/providers/google.provider (provided by package kaccounts-providers).

Changing that might allow you to turn off oauth, though I'd strongly recommend backing up any files before altering them.

Well, but… this is a plain simple XMPP account, on my own server, nothing to do with Google .

-nik

Natureshadow wrote:Well, but… this is a plain simple XMPP account, on my own server, nothing to do with Google .

Interesting, I didn't know that was implemented.

Maybe turn off OAuth authentication in ejabberd? (at least while creating the account) http://docs.ejabberd.im/admin/guide/oauth/

It does look like ktp-auth-handler is checking to see if X-OAUTH2 is being provided as a potential authentication method. I don't know how to disable OAUTH in the telepathy stack itself.

Diane

Thank you so much!

Your excellent help with KTp is one thing, but getting support for an upright server implementation bug is beyond all expectations ☺!