-
Notifications
You must be signed in to change notification settings - Fork 82
Pidgin Crashes: Assertion failed (M->id) #101
Comments
I have same problem on Ubuntu 15.04 |
Same for me. On Fedora 21 x86_64 |
I have the same problem (Using ubuntu 12.04 64): Linux lion 3.11.0-18-generic #32~precise1-Ubuntu SMP Thu Feb 20 17:52:10 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
Check out current master should be fixed. |
Until now no crash any more. |
But now the next crash: |
Send it please |
File send, I hope it will help. |
@tuxmaster I've looked at the backtrace and there doesn't seem to be any function from telegram-purple involved. Does it happen regularly? |
Until now only one time. |
Well, repeatedly. Or, let's say couple of times. |
@mcepl In the current master too? |
All day long telegram-purple works without crush. Thank you very much! |
But today only crashes as soon somebody write me an message. :( |
I have been doing fine today with f770abc |
I can reproduce it every time. |
Is it the same error? Can you try to debug it with gdb?
|
Here the backtrace of gdb: Thread 4 (Thread 0x7f22b2fd2700 (LWP 27755)): Thread 3 (Thread 0x7f22b1dfd700 (LWP 27756)): Thread 2 (Thread 0x7f22b0dfb700 (LWP 27758)): Thread 1 (Thread 0x7f22cd3c2a00 (LWP 27731)): |
@tuxmaster This is a separate issue, probably some corrupted secret chat, I moved it into a new ticket: #112 You can most likely circumvent this crashing by removing your current secret chats, or just starting a new session by deleting ~/.pidgin/telegram-purple/, but your secret chats will be lost :/ The current issue appears to be fixed. |
[pasha@pasha_bsd ~]$ pidgin
Assertion failed: (M->id), function tglm_message_insert_tree, file tgl/structures.c, line 2035.
Abort trap (core dumped)
[pasha@pasha_bsd ~]$ uname -a
FreeBSD pasha_bsd 10.0-RELEASE FreeBSD 10.0-RELEASE #0 r260789: Thu Jan 16 22:34:59 UTC 2014 root@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64
[pasha@pasha_bsd ~]$
[pasha@pasha_bsd ~]$ pkg info |grep teleg
telegram-purple-05222015 Libpurple plugin for Telegram messenger
The text was updated successfully, but these errors were encountered: