tdesktop
tdesktop copied to clipboard
telegramdesktop
Unresponsive after connecting to network
Steps to reproduce
- The app is minimized to tray, no network connection
- Go to sleep/hibernation (not sure if this matters)
- Wake up, unlock user session
- Connect to the Internet
- Invoke Telegram from tray
Expected behaviour
Main window shows up.
Actual behaviour
No response.
This happens often, but not every time, and started about 2-3 months ago.
Configuration
Operating system: Windows 7 [Version 6.1.7600]
Version of Telegram Desktop: 2.7.1
Used theme: Default
Logs:
log_freeze.zip
Screenshot from Process Explorer:
This happens often, but not every time, and started about 2-3 months ago.
That's the time of Qt 5.12 -> Qt 5.15 update, so probably a Qt bug
Same here on W7. Are you sure it's related to connecting to network though? The title might be wrong. I'd say it has something to do with going out of sleep mode.
I hope I've fixed it, there was a deadlock in Qt 5.15 on Windows in thread management. We'll see in the next version.
Hey there!
This issue was inactive for a long time and will be automatically closed in 30 days if there isn't any further activity. We therefore assume that the user has lost interest or resolved the problem on their own.
Don't worry though; if this is an error, let us know with a comment and we'll be happy to reopen the issue.
Thanks!
![stale[bot] avatar](https://avatars.githubusercontent.com/in/1724?v=4 "Published by a pub.dev verified publisher"){kind=small}
Still an issue on my W7. I have to manually kill TelegramDesktop.exe each time I get out of sleep mode.
It started to manifest again, on 3.1.8. Log tail (note the wake-up moment):
[2021.10.23 00:26:32] RPC Error: request 73853 got fail with code 400, error CHAT_ADMIN_REQUIRED [2021.10.23 00:26:36] RPC Error: request 73857 got fail with code 400, error CHAT_ADMIN_REQUIRED [2021.10.23 00:26:38] RPC Error: request 73861 got fail with code 400, error CHAT_ADMIN_REQUIRED [2021.10.23 00:33:31] API Warning: not loaded minimal channel applied. [2021.10.23 10:48:45] Could not send ping for some seconds, restarting... [2021.10.23 10:49:08] TCP Error: error packet received, endpoint: '149.154.175.100:443', protocolDcId: 3, code = -404 [2021.10.23 10:49:08] MTP Info: -404 error received in 10003 with temporary key, assuming it was destroyed. [2021.10.23 10:49:53] Could not send ping for some seconds, restarting... [2021.10.23 10:50:03] Could not send ping for some seconds, restarting...
Same issue happens on 2 computers with Win7. Telegram stops getting any messages and stops updating channels after resuming from standby. It occurs maybe 1 time in 5-7 runs.
In Ubuntu this happens quite often for me. Not sure if this information helps at all, but I typically get it working again without needing to restart it by going into Settings->Advanced settings and switching from which ever proxy setting there is to the other (no proxy <-> system settings). After the switch it immediately starts working again.
MacOS ( MBP M1 ) same issue, every time (not sometime) after sleep, wont reconnect, unless manual switching in Network section "between proxy and go back."
As #17397 got closed and this was added as the duplicate issue - just wanted to +1 here.
M1 Macbook Air. After going to sleep and being woken up - Telegram is completely unresponsive unless I force close the application and open it again, after which it works just fine.
Same issue, MacOS version 12.5.1, Telegram 4.1.1. After sleep telegram wont connect until I restart the application.
Still have this issue on flathub version 4.6.2 on Linux. Restarting the app solves the issue though.
regarding to issue #25895, which is closed as duplicate of this one. mtp_19_00.txt mtp_success.txt I'm attaching two mtp logs. One (mtp_19_00.txt) is shown how Telegram tries to reconnect for some huge time after wake up computer from sleep and telegram fails to connect for 2 hours. I do not want to provide all later log files, because they contains same information. Second log (mtp_success.txt) is for succeed case - 2 minutes to reconnect was taken.
Having the same issue every time after putting my Macbook sleep overnight. Restarting Telegram becomes a daily routine of mine.
Telegram 4.7, MacOS 13.1.
Having the same problem behind an enterprise proxy. Connection type is "Use system proxy settings". During a normal operation (Telegram using the proxy) I disabled the wifi and turned back again. Telegram failed to reconnect, stuck "Connecting". Checking Sysinternals Process Monitor it seems so that Telegram forgot to use the proxy, but was trying a direct connection forever.
I'm experiencing the same. MacOS 13.3.1, Telegram 4.7
To restore the connection I either need to restart the entire application or go to Settings>Advanced>Connection>Toggle IPv6 to any state just to force the app into the reconnection.
Same issue Air M2 Venture 13.0.1 Telegram 4.8.1
I was about to become a premium user, but switched from Win (no issues for years) to Mac. Can't imagine paying voluntary money for the app I have to manually reset several times a day.
This bug exists for over 2 years now, other messaging apps on MacOS doesn't have this issue. Is there any good reason to ignore it for so long?
Seems that it got worse last few months. I remember I had to restart/change proxy settings once a week last year, but eventually, it became a daily routine :(
MacBook Pro M1 Mac OSX 13.3.1 Telegram 4.8.1
On my m2 any sleep, even 30 secs long, causes the disconnection. Hate it since so many work related chats are now in Telegram :(
On Wed, May 3, 2023, 14:33 allx @.***> wrote:
Seems that it got worse last few months. I remember I had to restart/change proxy settings once a week last year, but eventually, it became a daily routine :(
MacBook Pro M1 Mac OSX 13.3.1 Telegram 4.8.1
— Reply to this email directly, view it on GitHub https://github.com/telegramdesktop/tdesktop/issues/16093#issuecomment-1532576269, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAG7I7ATM6NOKGHN3GYBIE3XEIC3VANCNFSM42MITALQ . You are receiving this because you commented.Message ID: @.***>
@john-preston can you please check this issue? It is very annoying to restart client every time laptop is waking from sleep.
Same issue here, I have to restart Telegram each time connexion goes off and on (after computer goes to sleep for example)
Setup: MacBook Pro M1 macOS 13.4.1 (22F82) Telegram 4.8.3
Can you at least add some sort of button, (in side menu may be), aka refresh conenction button in more convenient way pls? So we don't need to restart or search proxy setting every time :(
Doesn't disconnecting and reconnecting to network via system work as such button?
Nope. It requires a lot more click actions rather than a single button click. And again, that a 100% bug. Being ignored by the team with no explanation given. All other messenger apps (WhatsApp, FB, Slack, Line)on my m2 air are capable of reconnection. Yet Telegram is the only one with a Premium option, that can't do it.
Nope. It requires a lot more click actions rather than a single button click. And again, that a 100% bug. Being ignored by the team with no explanation given. All other messenger apps (WhatsApp, FB, Slack, Line)on my m2 air are capable of reconnection. Yet Telegram is the only one with a Premium option, that can't do it.
not ignored, a fix atempt was pushed. (but failed)
It requires a lot more click actions rather than a single button click.
Well, I have internet connection applet on my panel and I can enable/disable airplane mode with 2-3 clicks. I thought it's the same in any modern system.
It requires a lot more click actions rather than a single button click.
Well, I have internet connection applet on my panel and I can enable/disable airplane mode with 2-3 clicks. I thought it's the same in any modern system.
I think that problem in this solution that we have to do it system-wide, but there could be playing video/music stream, active downloads/uploads and etc. in other applications that we do not want to stop (in some cases such system-wide reboot of network connection may fail processes in other applications)
In most cases, I for example, and I believe other users the same - may notice that telegram is unresponsive in a lot of time after launch of computer.
Just imagine a streamer who already "On Air" - he cannot stop streaming just to "Fix telegram bug"
