TL_BadMsgNotification crashes Telegram
Bug #1437246 reported by
Michał Karnicki
This bug affects 5 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Telegram app |
Fix Released
|
High
|
Unassigned |
Bug Description
mardy reported a log file indicating Telegram could crash when processing TL_BadMsgNotifi
Moving .config directory works around the problem reason.
See comment #3 for details.
Changed in libqtelegram: | |
importance: | Undecided → Critical |
assignee: | nobody → Michał Karnicki (karni) |
description: | updated |
Changed in libqtelegram: | |
status: | New → Confirmed |
tags: | added: v2 |
description: | updated |
tags: |
added: v2-verify removed: v2 |
Changed in telegram-app: | |
assignee: | Michał Karnicki (karni) → nobody |
Changed in telegram-app: | |
milestone: | none → beta1 |
Changed in telegram-app: | |
milestone: | beta1 → beta2 |
status: | Confirmed → Fix Committed |
Changed in telegram-app: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Some updates: first, moving the .config directory fixes the problem only until the next instance of telegram starts: that it, if you remove the .config directory you can start telegram, but once you've closed it won't start again.
Then, I now tried to move both the .config and the .cache directories, and got a slightly different behaviour: now crashes seem more random, but still happen in the first few tens of seconds when the program starts up. I'm attaching the new logs.