all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Diego Nicola Barbato <dnbarbato@posteo.de>
To: 38990@debbugs.gnu.org
Subject: bug#38990: Update of tdlib to 1.5.4 breaks emacs-telega
Date: Mon, 06 Jan 2020 15:08:08 +0100	[thread overview]
Message-ID: <87zhf0fzjr.fsf@GlaDOS.home> (raw)

Hi Guix,

emacs-telega doesn't work with version 1.5.4 of tdlib (last known good
commit: df23842; first known bad commit: 70848cd).

After starting telega (M-x telega RET) the *Telega Root* buffer looks
like this:

--8<---------------cut here---------------start------------->8---
Status: Ready                 Fetching chats..
[2:All               ]  [0:Secrets           ]  [0:Bots              ]  
[0:Groups            ]  [2:Private           ]  [0:Channels          ]  

--------------------------------(all)---------------------------------
{Alice                       }  Last message from Alice       05.01.20
{Bob                         }  Last message from Bob         04.01.20
--8<---------------cut here---------------end--------------->8---

The dot animation after "Fetching chats" keeps looping and the following
error message is displayed (2 times, according to the *Messages* buffer)
in the minibuffer:

--8<---------------cut here---------------start------------->8---
error in process filter: Wrong type argument: stringp, nil
--8<---------------cut here---------------end--------------->8---

Deleting the ~/.telega directory and logging in again results in the
same error.

The state in ~/.telega seems to get corrupted too: Trying to run the
known good telega from before the tdlib update afterwards fails because
the server seems to crash.

Regards,

Diego

             reply	other threads:[~2020-01-06 14:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-06 14:08 Diego Nicola Barbato [this message]
2020-01-17  7:47 ` bug#38990: Update of tdlib to 1.5.4 breaks emacs-telega Diego Nicola Barbato

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zhf0fzjr.fsf@GlaDOS.home \
    --to=dnbarbato@posteo.de \
    --cc=38990@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.