Comment 6 for bug 1512332

Revision history for this message
Pascal Krause (krapas) wrote :

I have same issue on Aquaris E5 OTA-9.1, Telegram 2.0.8.1.
Issue was present. After some time it worked again but now it is broken again.
My assumption here, it depends on received messages. It got broken again, right after I received a message on secure chat.
Here the ~/.cache/upstart log:
[20160307 19:41:42.736 CET ASSERT: "x == (qint32)DecryptedMessageAction::typeDecryptedMessageActionSetMessageTTL || x == (qint32)DecryptedMessageAction::typeDecryptedMessageActionReadMessages || x == (qint32)DecryptedMessageAction::typeDecryptedMessageActionDeleteMessages || x == (qint32)DecryptedMessageAction::typeDecryptedMessageActionScreenshotMessages || x == (qint32)DecryptedMessageAction::typeDecryptedMessageActionFlushHistory || x == (qint32)DecryptedMessageAction::typeDecryptedMessageActionResend || x == (qint32)DecryptedMessageAction::typeDecryptedMessageActionNotifyLayer || x == (qint32)DecryptedMessageAction::typeDecryptedMessageActionTyping" in file ../secret/decrypter.cpp, line 424