-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No authentication dialogue in Empathy #60
Comments
Authentication works with KDE Telepathy and it is used to work with Empathy, but for some reason it does not work on Sailfish OS. Next week I'll check how the current version work with Empathy; maybe it is the same issue with Sailfish OS. |
I tried reproducing it in a virtual computer and the authentication dialogue was displayed correctly even with Polari running. I tried running it on my profile and the same log as “Output of telepathy-morse on subsequent attempts” was produced. The only difference is that on my profile, Empathy and telepathy-morse are installed in a non-standard location (not on system path). Interestingly, no authentication code is sent, either by SMS or through Telegram. |
I have the same problem. Running KDE on Arch. |
Same, I wonder if there are any updates on this? So far I had to use the official telegram client. |
Same issue. |
It looks like Empathy is no longer maintained according to the GNOME wiki:
and the project repos are at archive group: I guess this repositories could be helpful debugging Empathy auth handling logic. |
I am running master branch of telepathy-morse (175dfa4a6d8fea959ac2f02254da4ffbb3cf7f5c) & telegram-qt (75dfa4a6d8fea959ac2f02254da4ffbb3cf7f5and). After adding an account in Empathy, no authentication dialogue is displayed.
Running telepathy-morse in a console, I saw something about
ServerAuthenticationChannel1
do not have the logs, though. On further connections, I am gettingAUTH_KEY_UNREGISTERED
:Output of telepathy-morse on subsequent attempts
I have output from
dbus-monitor --session --monitor
from the initial connection:Monitor of session bus
Could polari been intercepting the authentication request?
I cannot perform any more actions at the moment because I have been blocked for repeated authentication attempts.
The text was updated successfully, but these errors were encountered: