tdesktop
tdesktop copied to clipboard
telegramdesktop
crash
Steps to reproduce
When the channel is added to the folder, an emergency completion of the program occurs
Expected behaviour
.
Actual behaviour
.
Operating system
debian 11 xfce
Version of Telegram Desktop
4.2
Installation source
Static binary from official website
Logs
No response
The same issue while adding Telegram group to the folder. Telegram Desktop 4.2 for Linux (Fedora 36)
@ilya-fedin Your Report Tag: 350868f5-aca8-4019-abdbe399-078921b1 Your User Tag: 70c3fed4d9431184
@vsile Nothing can be read from there, sorry :( It shows one stack frame without any source information.
It shows some corrupted string as the binary name, specifically "~/Загрузки/Telegram/Telegram^@^@^@^@^@^@^@^@".
Is it possible you move and rename it to something like "~/Tmp/Telegram"? And then send one more crash report and post one more tag here.
I doubt this is the reason of a bad crash dump, but who knows.
I moved Telegram directory (with Telegram and Updater files) to ~/go/Telegram and launched it from the terminal. After adding the Telegram group to the folder it crashed again.
Your Report Tag: f5a4d09d-2033-455d-44525b8b-a297b64d
Your User Tag: 70c3fed4d9431184
In the terminal I got this error:
vera@fedora:~/go/Telegram$ ./Telegram
Ошибка сегментирования (стек памяти сброшен на диск)
upvoting: crash after trying to delete the empty folder, maybe incorrect folder limitation for free account?
ApiId: 2040 Binary: Telegram Launched: 22.09.2022 04:14:44 OpenGL: Enabled OpenGL Renderer: [not-initialized] Platform: Linux Version: 4002000
Caught signal 11 (SIGSEGV) in thread 139828772494848
Backtrace omitted.
Google Breakpad caught a crash, minidump written in thread 139828772494848 Minidump: ~/.local/share/TelegramDesktop/tdata/dumps/8837ae65-d1da-46b6-0c7a3394-436a990e.dmp
Backtrace omitted.
steps: open tg, open folder settings, remove all groups from folder, delete folder. click to popup close button or outside popup window
BTW, please, add in FAQ section how to make crash tag report and where the logs placed
That's a question for @john-preston, only he has access to debug symbols