TelegramDesktop from flatpack do not starting after latest update on Ubuntu 22.04.3 LTS #27134
Comments
|
Same on Fedora 39: |
|
After reinstall from cli: |
|
$ echo $? |
successfully started |
Message log The package containing /app/bin/telegram-desktop was not found. System: |
|
Downgrading to the previous flatpak release fixes the issue for now. How to do it: $ sudo flatpak update --commit="b340f0a01083a73773c1be5edfb9ce6e28cd8002c027ab72f8c6b93a2e5c28ce" org.telegram.desktop
|
|
I can confirm this issue. The flatpak app doesn't open anymore after the latest update. Workaround for those having the same issue (downgrade to previous working version): First we gonna check for what commits have been made by Telegram to Flathub with this command: Then we look for the second newest commit (usually at the top) and copy the string behind "Commit:", after which we downgrade to the version we want with: In this case we can use: (The reason I wrote a whole explanation rather than to just post a command, is because I'm a bit distrustful myself. So everyone who is like me, won't just have to trust my commands blindly that way.) Good luck everyone! |
|
I also confirm the issue, version 4.11.8 on Kubuntu 23.10, telegram flatpak edition. For dmesg : From journalctl : Seems to come from QT library here. Downgrading is the workaround, and working well, as mentioned in last comments... |
|
I have the same problem. Log:
|
|
#27134 (comment) |
|
flatpak downgrade apparently does not work anymore. F39 flatpak update --commit="b340f0a01083a73773c1be5edfb9ce6e28cd8002c027ab72f8c6b93a2e5c28ce" org.telegram.desktop
Vyhledávají se aktualizace…
chyba: Server returned status 404flatpak info org.telegram.desktop/`arch`/stable | tail -4
Commit: f911bd3768af01295dbebba7ad56ecb754dcd4525b8ceb5e8c777b6c4c21de43
Parent: b340f0a01083a73773c1be5edfb9ce6e28cd8002c027ab72f8c6b93a2e5c28ce
Subject: Try to pleasure the linter (d7b8020f)
Date: 2023-11-23 07:57:35 +0000 |
|
Same problem after update, my telegram wouldn't start on desktop, have to revert to mobile phone. what a mess Using Pop!_OS 22.04 LTS, Gawd damn it |
|
Flatpak update on Linux Mint. [2023.11.23 22:09:48] Launched version: 3006001, install beta: [FALSE], alpha: 0, debug mode: [FALSE] |
|
flatpak downgrade works for me: sudo flatpak update --commit=b340f0a01083a73773c1be5edfb9ce6e28cd8002c027ab72f8c6b93a2e5c28ce org.telegram.desktop |
|
@todoleza I'm afraid the problem is on the side of your network or ISP. I tried installing the latest version of Telegram flatpak and then downgrading it on a completely fresh Fedora 39 virtual machine, and everything went without issues. You should definitely check the resolve output for the $ nslookup flathub.org
Server: X.X.X.XX
Address: X.X.X.X#X
Non-authoritative answer:
Name: flathub.org
Address: X.X.X.X
Name: flathub.org
Address: X:X:X::347 |
|
Can confirm, doesn't start, Fedora workstation 39, flatpak, please find log in attachment. |
|
Confirming as well, Fedora workstation 39 KDE Spin, flatpak, latest Telegram update |
I can confirm this did allow the system to work, but doesn't directly resolve the issue. I'm not seeing anything unusual in the logs, so I will tinker with it after the holidays. Something similar happened to BitWarden's update. OS: Linux Mint 21.2 Cinnamon |
|
I get this error on
Solved with downgrade. |
|
(Note: Not a fix - see comments following this.) I'm using the flatpak version and the same issue happened to me after upgrading this morning. However, I just ended up getting it running although accidentally. I first downgraded telegram to the previous commit. When I started it it looked like a fresh install and wanted me to link to my phone again. This looked odd (I thought maybe because downgrading is done with sudo and so perhaps was treating it like a fresh install), so I ran the flatpak update again to get to the latest. When I started telegram after updating to the latest (4.11.8 ) it worked this time - no error about gz/svg. It wanted me to link to the phone but it's running without a problem. |
|
@philmalin This issue occurs again when loading media files (images, videos + gifs) into the client cache. Try scrolling through a few channels/chats with different media attachments and see how the app behaves. |
|
@maximilionus - Yep, that's what happens. It didn't crash with Telegram running but when I restart it gives the same error and crashes. It actually gets further than before in that it shows a few channels before blowing up. |
@maximilionus thanks for the tip, although the source of the absence must've been somewhere else. The command for commit installation started working few hours later.
Non-authoritative answer:
Name: flathub.org
Address: 199.232.57.91
Name: flathub.org
Address: 2a04:4e42:4b::347The addresses can be different per your geo where you query them or they can be anycast and you don't know whom you are talking to anyway :) HTH and cheers |
|
Re: #27134 (comment) |
|
Why is this marked completed? No new update has been pushed to Flathub, Telegram still doesn't start. |
There were 4 updates since broken one: |
|
And yet here is the broken version, with a fully resynced updated Flathub
|
it's marked as complete when a fix is pushed, not when release is made. |
|
Yes confirm that it is now working well |
Steps to reproduce
update from Discovery
Expected behaviour
started
Actual behaviour
do not started
Operating system
Ubuntu 22.04.3 LTS
Version of Telegram Desktop
4.11.8 stable
Installation source
Flatpak
Crash ID
No response
Logs
The text was updated successfully, but these errors were encountered: