-
Notifications
You must be signed in to change notification settings - Fork 82
unable to connect after "Terminate all sessions" #41
Comments
The same thing happens with telegram-cli too, which suggests that its a bug in libtgl. I will report this one upstream. |
I got a similar issue. After deleting the session, it is not possible to connect again. I deleted the complete account in pidgin, the path .purple/telegram-purple/ and reinstalled the plugin, but when I try to authenticate, it doesn't accept the authentification code. Here is the log:
I tried it multiple times, the code is absolutely correct. Is there a away, to solve it? |
Are you using some non-pidgin messenger with fallback chat for SMS authentication prompt and did you install some plugins like OTR? Cause that might be related... |
Thanks for your help. The strange thing is, that I didn't deactivate otr before. |
@kaputtnik, do you use telegram-purple with trillian? |
@ThiRaBrTNK: That doesn't make any sense, as Trillian doesn't support libpurple and is closed source anyway. Closing this issue since there seems to have been no activity for over half a year. (Silent-Hunter's reference is accidental due to a backtrace.) |
@BenWiederhake I was just googling for trillian telegram plugin and found this issue. I got confused by 'Trillian' in @kaputtnik 's log, and although I didn't find any mention of trillian using libpurple, neither I found the confirmation that it isn't. So I asked just to be sure. |
@ThiRaBrTNK that's because he's got the Log Reader plugin which reads in Trillian logs into Pidgin :) |
@EionRobb Thank you for clearing this thing up |
I used the plugin for a while but after issuing a "Terminate all sessions" from another client I was unable to reauth, I fixed it by deleting
~/.telegram-purple
directory, so telegram issued new auth code, I thinkauth
file should be deleted when it happensThe text was updated successfully, but these errors were encountered: