Skip to content
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

tgl/queries.c:470: tglq_query_result: Assertion `0' failed #144

Open
kenorb opened this issue Apr 6, 2019 · 8 comments
Open

tgl/queries.c:470: tglq_query_result: Assertion `0' failed #144

kenorb opened this issue Apr 6, 2019 · 8 comments

Comments

@kenorb
Copy link

kenorb commented Apr 6, 2019

$ telegram-cli -D
 *** 1554554018.940353 Skipped 8292 int out of 62378 (type updates.Difference) (query type get difference)
 *** 1554554018.940387 0x00000000 0xa8fb1981 0x1cb5c415 0x000000e3
> telegram-cli: tgl/queries.c:470: tglq_query_result: Assertion `0' failed.
SIGNAL received
h/snap/telegram-cli/25/bin/telegram-cli(print_backtrace+0x2f)[0x46ef1f]
/snap/telegram-cli/25/bin/telegram-cli(termination_signal_handler+0x64)[0x46efb4]
/lib/x86_64-linux-gnu/libc.so.6(+0x354b0)[0x7fc70cbb64b0]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x38)[0x7fc70cbb6428]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7fc70cbb802a]
/lib/x86_64-linux-gnu/libc.so.6(+0x2dbd7)[0x7fc70cbaebd7]
/lib/x86_64-linux-gnu/libc.so.6(+0x2dc82)[0x7fc70cbaec82]
/snap/telegram-cli/25/bin/telegram-cli(tglq_query_result+0x44c)[0x498b5c]
/snap/telegram-cli/25/bin/telegram-cli[0x49157f]
/snap/telegram-cli/25/bin/telegram-cli[0x4b5d5b]
/snap/telegram-cli/25/usr/lib/x86_64-linux-gnu/libevent-2.0.so.5(event_base_loop+0x819)[0x7fc70e0654c9]
/snap/telegram-cli/25/bin/telegram-cli(net_loop+0xa7)[0x470557]
/snap/telegram-cli/25/bin/telegram-cli(loop+0x183)[0x4718c3]
/snap/telegram-cli/25/bin/telegram-cli(main+0x2e5)[0x46d745]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0)[0x7fc70cba1830]
/snap/telegram-cli/25/bin/telegram-cli(_start+0x29)[0x46d859]

Related: GH-139

@nohimx
Copy link

nohimx commented May 16, 2019

Similar issue. It work for sometime, but from this morning only ONE of numbers doesnt work. Another few numbers work fine.
*** 1558006150.054209 Secret chat in ok state
*** 1558006150.055502 Sent query #2613107180365892 of size 144 to DC 4
*** 1558006150.118311 outbound rpc connection from dc #4 becomed ready
*** 1558006150.118458 Sent query #2613107450599100 of size 132 to DC 4
*** 1558006150.183031 restarting query 2613107450599100
*** 1558006150.183110 Alarm query 2613107450599100 (type 'get config')
*** 1558006150.247114 bad_msg_notification: msg_id = 6691585461217615872, seq = 2, error = 64
*** 1558006150.247180 bad_msg_notification: msg_id = 6691585461217615872, seq = 2, error = 64
*** 1558006150.247266 failing session -6645897589392539388
*** 1558006150.310904 outbound rpc connection from dc #4 becomed ready
*** 1558006150.311023 Sent query #6691585461766524928 of size 132 to DC 4
*** 1558006150.375407 adjusting CLOCK_MONOTONIC delta to 0.192370
*** 1558006150.375462 work_new_session_created: msg_id = 6691585462737859585, dc = 4
*** 1558006150.375545 regen query from old session 2613107180365892
*** 1558006150.375604 regen query from old session 2613107450599100
*** 1558006150.381416 Alarm query 2613107450599100 (type 'get config')
*** 1558006150.381549 Resent query #2613107450599100 as #6691585461766524932 of size 132 to DC 4
*** 1558006150.387633 DC1 '' update: 2001:0b28:f23d:f001:0000:0000:0000:000a:443
*** 1558006150.387720 DC2 '' update: 149.154.167.51:443
*** 1558006150.387778 DC2 '' update: 2001:067c:04e8:f002:0000:0000:0000:000a:443
*** 1558006150.387855 DC3 '' update: 2001:0b28:f23d:f003:0000:0000:0000:000a:443
*** 1558006150.387914 DC4 '' update: 2001:067c:04e8:f004:0000:0000:0000:000a:443
*** 1558006150.387999 DC4 '' update: 149.154.164.250:443
*** 1558006150.388086 DC4 '' update: 2001:067c:04e8:f004:0000:0000:0000:000b:443
*** 1558006150.388174 DC5 '' update: 2001:0b28:f23f:f005:0000:0000:0000:000a:443
*** 1558006150.388261 DC5 '' update: 91.108.56.132:443
*** 1558006150.480346 Alarm query 2613107180365892 (type 'get difference')
*** 1558006150.480455 Resent query #2613107180365892 as #6691585461766524936 of size 144 to DC 4
*** 1558006150.699366 Skipped 11 int out of 8696 (type updates.Difference) (query type get difference)
*** 1558006150.699443 0x00000000 0x00f49ca0 0x1cb5c415 0x000000da

telegram-cli: tgl/queries.c:470: tglq_query_result: Assertion `0' failed.
SIGNAL received
htelegram-cli(print_backtrace+0x2f)[0x55ac27ee68af]
telegram-cli(termination_signal_handler+0x64)[0x55ac27ee6944]
/lib/x86_64-linux-gnu/libc.so.6(+0x3ef20)[0x7f0070b3df20]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7f0070b3de97]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x7f0070b3f801]
/lib/x86_64-linux-gnu/libc.so.6(+0x3039a)[0x7f0070b2f39a]
/lib/x86_64-linux-gnu/libc.so.6(+0x30412)[0x7f0070b2f412]
telegram-cli(+0x9ecc3)[0x55ac27f0fcc3]
telegram-cli(+0x9792b)[0x55ac27f0892b]
telegram-cli(+0xbb9de)[0x55ac27f2c9de]
/usr/lib/x86_64-linux-gnu/libevent-2.1.so.6(+0x1e8f8)[0x7f00720228f8]
/usr/lib/x86_64-linux-gnu/libevent-2.1.so.6(event_base_loop+0x53f)[0x7f007202333f]
telegram-cli(net_loop+0xa7)[0x55ac27ee7ee7]
telegram-cli(loop+0x183)[0x55ac27ee9263]
telegram-cli(main+0x24c)[0x55ac27ee501c]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x7f0070b20b97]
telegram-cli(_start+0x2a)[0x55ac27ee51ca]

@ferz
Copy link

ferz commented Jun 28, 2019

$ pidgin
(Pidgin:31586): libnotify-WARNING **: 11:39:49.663: Failed to connect to proxy
pidgin: queries.c:470: tglq_query_result: assert "0" failed.

@MartinX3
Copy link

MartinX3 commented Jul 22, 2019

$ pidgin
(Pidgin:31586): libnotify-WARNING **: 11:39:49.663: Failed to connect to proxy
pidgin: queries.c:470: tglq_query_result: assert "0" failed.

Getting a similar error since today without updating pidgin.
Weird.

$ pidgin
pidgin: queries.c:470: tglq_query_result: Zusicherung »0« nicht erfüllt.
Abgebrochen (Speicherabzug geschrieben)

@psychosys
Copy link

at this moment that I am writing this message telegram killed this app completely because SCHEMA is very old

@BenWiederhake
Copy link
Contributor

@psychosys What are you talking about? Still works for everyone else. Also, MTProto is backwards compatibile, so in theory tgl should continue to work indefinitely. (Without support for new stuff like animated stickers, but still.)

@MiroslavVitkov
Copy link

This is the code around the assert:

      vlogprintf (E_DEBUG, "in_ptr = %p, end_ptr = %p\n", in_ptr, in_end);
      if (skip_type_any (q->type) < 0) {
        vlogprintf (E_ERROR, "Skipped %ld int out of %ld (type %s) (query type %s)\n", (long)(in_ptr - save), (long)(in_end - save), q->type->type->id, q->methods->name);
        vlogprintf (E_ERROR, "0x%08x 0x%08x 0x%08x 0x%08x\n", *(save - 1), *(save), *(save + 1), *(save + 2));
        assert (0);
      }

But I can't even trace the definition of that function, let alone fix it.

@monarrk
Copy link

monarrk commented Feb 7, 2022

at this moment that I am writing this message telegram killed this app completely because SCHEMA is very old

does this mean telegram won't work with this anymore? I'm still getting this error on NetBSD 9.2

@BenWiederhake
Copy link
Contributor

Around December 2021, Telegram enforced 64-bit user IDs, and disabled access to most (all?) old schemas. You could try your luck with this version of libtgl: https://github.com/majn/tgl/
It has been maintained for longer, but it is also abandoned, and probably not new enough (= not high enough schema version).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants