TL_BadMsgNotification crashes Telegram

Bug #1437246 reported by Michał Karnicki
26
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_BadMsgNotification. karni has the log file.

Moving .config directory works around the problem reason.

See comment #3 for details.

Tags: v2-verify
Michał Karnicki (karni)
Changed in libqtelegram:
importance: Undecided → Critical
assignee: nobody → Michał Karnicki (karni)
description: updated
Revision history for this message
Alberto Mardegan (mardy) wrote :

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.

Revision history for this message
Alberto Mardegan (mardy) wrote :

More logs. So, it seems I can reliably crash it by sending the app to the background and then bringing it to the foreground again. These logs might be more useful, as there's an assertion with a file name and line number.

Revision history for this message
Alberto Mardegan (mardy) wrote :
Revision history for this message
Michał Karnicki (karni) wrote :

Lowering priority since it doesn't crash since last OTA, neverneless needs fixing.

Changed in libqtelegram:
importance: Critical → High
Michał Karnicki (karni)
Changed in libqtelegram:
status: New → Confirmed
Revision history for this message
ed (ed-stranger) wrote :

First app start : everything is normal, functions as expected.
--Shut down app

Second start: (with wifi) the app shows a black screen with loading icon and Telegram header title. Crashes within approx 10sec of launch // (without wifi) Same behaviour

After reinstall (without fiddling w/ config files) : the app shows a black screen with loading icon and Telegram header title. Crashes within approx 10sec of launch.

After reinstall and removing /.config/com.ubuntu.telegram completely : app starts, shows expected behaviour. Haven't tested sending messages. App seems to work. Wifi was enabled and could connect to account/add number

After restarting app: App shows a loading screen for approx 5sec , then shows the message inbox screen with annotation "no chats". This screen is displayed for about 5secs before the app crashes. Relaunch of the app shows same behaviour.

After turning wifi off/on and 3G data off/on, the app shows the blank screen + loading icon + crash behaviour again.

device : bq 4.5 , up to date

logs : http://paste.ubuntu.com/12012113/

I also posted in the crash thread : [bq 5] Telegram crashes

Didnt know which w

Revision history for this message
Michał Karnicki (karni) wrote :

Hi Ed,

Thank you for the report. Would you be willing to attach more verbose logs? You would need to run the following command in either adb shell or Terminal application:

touch /home/phablet/.config/com.ubuntu.telegram/.debug

Then reproduce the crash and send the log my way. Thank you in advance!

Michał Karnicki (karni)
tags: added: v2
Michał Karnicki (karni)
description: updated
Michał Karnicki (karni)
tags: added: v2-verify
removed: v2
Michał Karnicki (karni)
Changed in telegram-app:
assignee: Michał Karnicki (karni) → nobody
Michał Karnicki (karni)
Changed in telegram-app:
milestone: none → beta1
Michał Karnicki (karni)
Changed in telegram-app:
milestone: beta1 → beta2
status: Confirmed → Fix Committed
Revision history for this message
Ethan Chang (ethan.chang) wrote :

Not able to reproduce this issue on v2.0.2 (2 beta-2)

Michał Karnicki (karni)
Changed in telegram-app:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.