Program crashes immediately after startup

[outa]

Hi, since a few days I have the problem that cutegram crashes 1 second or so after the GUI is loaded:

$ cutegram 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 Abgebrochen (Speicherabzug geschrieben)

"Abgebrochen (Speicherabzug geschrieben)" means something like Aborted (Core dumped). I use version 2.7.1 on Kubuntu 15.10, kernel 4.2.0-34-generic.

[Self-Perfection]

I have the same issue on Debian 8.5.

I got notification about new message on secret chat and immediately Cutegram crashed. After that message cutegram crashes after start just like @outa described (with the same message).

I was using 2.5.0-2aseman-utopic when these crashes started. I tried upgrading to cutegram_2.7.1-1-amd64.deb but it did not help.

Is there a workaround to fix this without full cutegram configuration purge?

[Self-Perfection]

I don't know why, but now my cutegram does not crash anymore. The package was not updated, I have not tried purging profile/config directories and suddenly cutegram just started to work properly.

[condatek]

Same issue here in Linux Mint 17.3 KDE, Kernel 4.4.0-34-generic .

The GUI starts and after a couple of seconds it crashes for some reason. (Same error message as @outa )

Tried with 2.7.1-2aseman-trusty from Launchpad PPA and also by manually installing cutegram_2.7.1-1-amd64.deb

$ cutegram 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 Annullato

I can say additionally that it was working before, then a couple of days ago I've tried the Telegram Web application (https://web.telegram.org) after opening cutegram again the bug started to present but I can not be sure it's related.

@Self-Perfection: can you tell us if you removed any chats or did anything particular externally to cutegram ? (eg. by official client or web app)

[Self-Perfection]

@condatek: I have nothing to add to my previous comment. Here is whole story in other words:

1. I started to get this crash
2. I tried to fix by upgrading cutegram - with no visible effect. Still the same crash and error message with 2.7.1
3. I left the issue as is. I had cutegram in autostart on event of session unlock. So for several days whenever I unlocked my PC I saw cutegram window appearing for a second
4. Then after about of week without any special intervention cutegram have not crashed after start and was working fine ever since.

So here is an advice: try to leave the issue for a week to rest. It may resolve itself.

My guess is that something malicious gets cached but in time cache expires.

[Captain-Rage]

Same here. Cutegram was working the other day and now this appeared:

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 Aborted (core dumped)

The only thing I can think of is that I created a secret chat on another device running Telegram (Android) and upgraded some packages on the system that Cutegram is running (Arch Linux x86_64 Linux 4.4.30-1-lts). Also tried to delete the secret chat from the other device and to reinstall Cutegram but with no improvement.

[mostafa88]

I also have this problem. I download prebuild version of Cutegram 2.7.1 for windows and install it on windows 7 Professional, SP1. Graphic Device: Mobile Intel 945 Express Chipset Familiy Driver: igdumd32.dll, Vesion: 8.15.10.1930 with support OpenGL 1.4 Processor: Intel Atom N270,1.6GHz Memory:2GB Here is a screen shot of crash.

[nomorebugs]

ASSERT: "x == (qint32)DecryptedMessage::typeDecryptedMessage_level8 || x == (qint32)DecryptedMessage::typeDecryptedMessageService_level8 || x == (qint32)DecryptedMessage::typeDecryptedMessage || x == (qint32)DecryptedMessage::typeDecryptedMessageService" in file ../libqtelegram-aseman-edition/secret/decrypter.cpp, line 271 /usr/bin/cutegram: Zeile 19: 30947 Abgebrochen (Speicherabzug geschrieben) "$ASEMAN_DATA_PATH/cutegram" "$@"

For me too. Is this project even alive any more?

[nomorebugs]

+1

[VoxLight]

I am running Win10 on a pretty low-end PC, had this issue for about an hour. Would open up Cutegram, touch something, and then it would crash. Eventually, I just opened it up, and let it sit on the welcome screen, didn't touch anything for around 1min~ or so, and then when I poked stuff, it stopped crashing.