-
Notifications
You must be signed in to change notification settings - Fork 5.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash on Debian 11 #26472
Comments
Yeah, that's totally expected, please read the instruction more carefully |
If you know the reason, why didn't you mention it? |
Because I'm tired by repeating the same thing over and over... If you don't like my answers, I can avoid to answer you, are you ok with that? If you'd create an issue that explains the expected behavior next time, I'll avoid to answer you and @Aokromes may just close it with not a bug label with no further explanation. Or just no any reaction at all... |
And where are the links to these supposedly frequent answers of yours??? Anyway I |
Your magic is to search by name for errors that I don`t have? So there are millions of them, start with the letter I only had this error, and all over the internet this is the answer for it: And you also newer answered it, even though you write that you are tired of repeating. |
Steps to reproduce
Build from master
Start Telegram
Expected behaviour
Start
Actual behaviour
Crash
Operating system
Debian 11, xfce
Version of Telegram Desktop
git clone --recursive https://github.com/telegramdesktop/tdesktop.git
Installation source
Static binary from official website
Crash ID
No response
Logs
The text was updated successfully, but these errors were encountered: