-
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
Telegram in Ubuntu not showing images #28404
Comments
This means you haven't upgraded your system in some time and have a GNOME bug that was fixed in latest Ubuntu. |
I have Ubuntu 24.04 up-to-date, Telegram stopped working on the last update. No gnome updates are pending in my installation. |
24.04.1? |
No, just 24.04. Should I upgrade to 24.04.1 in order for Telegram to work correctly? The operating system has only five months out! |
It's the same operating system so I don't understand. You have to have latest update for your OS for it to work properly. |
Which gnome version should I be using? So I can check. |
Any that doesn't have https://gitlab.gnome.org/GNOME/mutter/-/issues/3229 |
Well, it seems upgrade to Ubuntu 24.04.1 is broken for some reason. I will wait for it to restore to a sane state, meanwhile I will check out about what gnome version is kosher, but all of this seems rather odd. What about someone using any previous Ubuntu version? |
None of still supported Ubuntu versions with latest bugfix updates is affected. |
24.04 is supposed to be supported! The bugfix you mention was included in Gnome 46, which is the version I am using right now. |
But you don't have latest bugfix updates for it.
It's not since first 46 version so you could use the version that doesn't have the fix. The only guarantee is only if you had all bugfix updates installed. |
In the logs of dpkg I have: 2024-08-16 15:23:16 configure gnome-shell:amd64 46.0-0ubuntu6~24.04.3 So my gnome version seems recent enough for a bug that was fixed four months ago. It must be something else. |
The bug is not in gnome-shell, it's in mutter. |
According to Ubuntu, I have the latest 46.0 version (installed in April), and there were no further updates. The only Ubuntu version that has a newer version is 24.04.1, with version 46.2, but it cannot be installed now because Ubuntu fucked up the upgrade a couple of days ago. So I assume no Ubuntu version besides Ubuntu 24.04.1 has this bugfix. How is Telegram working for all the rest? And why it stopped working only this week with the last Telegram updates? |
I consider it the same version as patch update is just a bugfix update. If it was the other way around and you had a really supported version, then you had a way to request the bugfix to your version from Ubuntu.
They don't disable installation of bugfix updates in Ubuntu?
The toolkit Telegram uses started to use the API that is bugged in old GNOME versions. |
Well, it seems the only way out is to update to Ubuntu 24.04.1 whenever that is possible again, bummer. Mutter 46.2 is from July 31, so at this point if there was a possibility of 24.04 to have it, it would have landed by now. |
Maybe you have broke your sources.list? The update is still on noble-updates and noble-updates exists in sources.list out of the box. |
You were right, thank you. Ubuntu by default sets the server for updates to the server in the country you live in, so in this case it was not up to date. I switched to the main Ubuntu server and I got the last mutter release, which fixed the Telegram problem. Thank you again, and sorry for the noise. |
Steps to reproduce
Expected behaviour
A popup should appear with a bigger image
Actual behaviour
An invisible window is triggered but no image appears. I know there is an invisible window because the Ubuntu Desktop shows two dots in the window count for Telegram in the left vertical application bar, and because if you alt-tab you can see a black Telegram window among the current opened thumbnail windows, but you can't switch effectively to it.
Operating system
Ubuntu 24.04
Version of Telegram Desktop
5.5.4 rev 6168
Installation source
Snap
Crash ID
No response
Logs
No response
The text was updated successfully, but these errors were encountered: