Telegram app not opening

The bug is also present in bq E5 for more than a month.

Even bq E5 is affected

First, please attach this log to the bug: /home/phablet/.cache/upstart/application-click-com.ubuntu.telegram_<version>.log

Then please check the following:

Do you have a folder named /home/phablet/.cache/QML/Apps/com.ubuntu.telegram_<version>/ ?
If so, does deleting that solve the problem?

If not, can you try deleting /home/phablet/.cache/com.ubuntu.telegram/ and see if that resolves the issue (this will delete secret chats)?

If that doesn't help either, lets wipe the complete config (you need to re-login to telegram after this). Delete the folder /home/phablet/.config/com.ubuntu.telegram/

Then please report back if it started working again, and if so, after which step it started working again.

Have the same problem with an E5.

In the log file I get the message

ubuntumirclient: Got invalid serialized mine data. Ignoring it

I do have the first mentioned folder but deleting it did not solve the problem as neither did deleting the whole other configuration files.

maybe this workarounds help.
resetting the phone (System settings>Reset>Erase and Reset Everything....)
then updates (System settings>Updates)
and log in your Telegram, it should work. ***do not log in your Telegram before you update your system and app***
Hope it helps.

This worked for me:

1) uninstall telegram
2) delete all folders (see post from michael zanetti)
i.e. anything that is related to telegram in:
.cache/QML
.cache
.config
3) install telegram, run update
Done

It didn't work for me...

Can you please post the output of:

find ~ -name *.lock

/home/phablet/.cache/thumbnailer-service.lock
/home/phablet/.config/com.ubuntu.docviewer/libreoffice/4/.lock
/home/phablet/.lock/share/webbrowser-add/session.json.lock

OK, so you don't have any .lock files related to telegram either...

So the app still crashes immediately after opening? In other words, does the app close itself after the splash screen, or does it keep hanging around just being white all over?

I am running out of ideas here to be honest... So summarizing all the things I have found so far once more here:

rm ~/.cache/QML -rf
rm ~/.local/share/com.ubuntu.reminders/ -rf
rm ~/.cache/com.ubuntu.reminders/ -rf
rm ~/.config/com.ubuntu.reminders -rf

If this doesn't help, then I really have no clue... I could not reproduce this issue on any of my devices so far.

The device does not crash. After I enter the phone number, it asks for the verification code, and when I enter it, it keeps trying to authenticate it until the countdown ends. The same happens endlessly. It is an authentication problem (which might have to do with an external process)

Ok. So this is something completely unrelated to this bug report. Please open a new bug report for your problem instead.