Why do two XMPP accounts get disabled by themselves?

asked 2016-06-11 12:59:50 +0200

Mikaela gravatar image

I have four XMPP accounts (legacy reasons) and two of them often get disabled by themselves saying that account information must be updated and requiring me to go to accounts and accept the username and password it already has and it gets connected without changes. Why does this happen? In case it's related to XEP support, here are compliance tester results for those servers:

By reading dukgo.com.txt I thought that the issue is missing XEP-0198: Stream Management, but jappix.com.txt says to have it. I also understood that SfOS Messaging doesn't have it so it cannot be the reason.

I think the issue happens when I lose connection, but logically it should take all accounts down instead of just these two.

edit retag flag offensive close delete

Comments

1

I believe that the Telepathy plugin which handles XMPP connections can sometimes wrongly detect various networking errors as authorization errors. This would explain why Google accounts sometimes also "sign themselves out" if people have the Google Chat service enabled.

In short, most likely it's a bug.

You can enable debugging by opening a few terminals and doing:

 killall telepathy-sasl-signon; G_MESSAGES_DEBUG=all G_DEBUG=all SASL_SIGNON_PERSIST=1 /usr/libexec/telepathy-sasl-signon
 killall mission-control-5; MC_DEBUG=1 G_MESSAGES_DEBUG=all G_DEBUG=ALL TP_MC_DEBUG=ALL /usr/libexec/mission-control-5
 killall telepathy-gabble; G_MESSAGES_DEBUG=all G_DEBUG=all GABBLE_PERSIST=1 /usr/libexec/telepathy-gabble

then use mc-tool to connect the different XMPP accounts, for example:

 mc-tool auto-connect gabble/jabber/chat_2exmppserver_2ecom0
 mc-tool reconnect gabble/jabber/chat_2exmppserver_2ecom0

Most likely the issue is in https://git.merproject.org/mer-core/telepathy-accounts-signon but it may also be in the telepathy-gabble component.

chris.adams ( 2016-06-13 06:34:03 +0200 )edit