-
Notifications
You must be signed in to change notification settings - Fork 5.6k
snap telegram-desktop=5.14.3 doesn't run in KUbuntu 25.04 #29332
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
Comments
I don't have the possibility to test on each existing distro version out there but I can't reproduce on Ubuntu 24.04. I assume that's either a problem with your setup or a regression on Ubuntu side. |
Yeap. I've updated to latest 25.04 Plucky recently. And updated telegram version after that. |
I'm not sure you've reported it to the right place, this looks like a Qt bug |
I have the exact same issue kubuntu 25.04 and nvidia
|
While I have integrated AMD GPU (Ryzen 4700U). I think this might be KUbuntu specific. The strange behavior that previous snap stable version works perfectly in KUbuntu 25.04. The problem appears only after upgrading Telegram Desktop to the latest snap version |
I have the same problem here. I'm using Kubuntu 25.04 and updated Telegram yesterday. It worked fine before that. |
I have exact same issue at exact same circumstances. I downloaded latest github release linux binary v5.14.3 (not snap) and it work for me fine. Seems like this is snap specific. |
I have the exact same issue kubuntu 25.04 and intel GPU, wayland session. So it's not gpu specific either (nvidia and amd gpu were also reported above). Like others, it worked fine before the upgrade to 5.14.3 yesterday, and I have the same output as @Master811129. No upgrade to system packages at the same time, so it's not a recent upstream regression in kubuntu. |
Have same bug on Kubuntu 25.04 launched as guest OS via VMWare Workstation 17.6.3
|
Same issue here after update snap to 5.14.3. 5.14.2 worked fine. KDE Neon, Wayland, Intel. |
Are you sure you had 5.14.2? Snap version before 5.14.3 was 5.13.1. |
Ah, yes, I'm sorry, my bad. The old version was 5.13.1 $ snap list --all telegram-desktop Also, the workaround @ashl1 provided works for me:
|
Same problem for me. I reverted to the last working revision, If the snapshot is still in your pc then you can run
else
|
Same issue here on three different installation of Kubuntu 25.04, KDE, Wayland, Intel CPU/GPU (i5 5th, 7th an 10th gen) |
Same here, Kubuntu 25.04 after snap update Telegram stopped working. AMD GPU and CPU. After downgrading the app it started working again, just type: sudo snap refresh telegram-desktop --revision 6597 |
The downgrading method is just temporary ... when the snap refresh, it upgrades to the latest stable, and it breaks again. Any update on this issue is much appreciated. Currently, running using the upstream Linux binary. |
Nothing new sadly, I have only VMs with LTS flavours of Ubuntu and none of them reproduced this issue (the only one supporting Wayland of them is the GNOME flavour, though). The only things I can suggest is to either stick to LTS versions or use the non-snap versions. People liking to experiment could try to reinstall the snap with |
I just ran it in KDE Neon, the issue is same in Wayland.
You can hold the update using
To remove the hold,
|
Running into the same issue with the current snap on Kubuntu 25.04, Framework Ryzen AI. For what it's worth, the binary release works fine. |
Indeed, installing with --devmode telegram works fine. |
I have the same error on Kubuntu 25.04 after last update. |
This is the output of
For comparison, this is from the
|
@marcusboden both outputs look identical to me, only that the first one is longer due to apparently the app being run for a longer time. I don't see anything related, it seem to mention only dbus calls and real time priority, nothing related to mmap. |
Same problem 👍🏽 |
Does it work by forcing it to fallback to Xwayland? DISABLE_WAYLAND=1 telegram-desktop |
Checked, yes. Also works with these steps
|
Believe it or not that exact same command started not working on my system... Wow |
Edge build also suffering from issue. |
"DISABLE_WAYLAND=1 telegram-desktop" worked for me 2 times. Successful run: $ DISABLE_WAYLAND=1 telegram-desktop then I tried to run telegram-desktop without this option, and it failed (as was expected). But now DISABLE_WAYLAND=1 doesn't help anymore: $ DISABLE_WAYLAND=1 telegram-desktop qt.qpa.wayland: Could not create EGL surface (EGL error 0x3000) qt.qpa.wayland: Could not create EGL surface (EGL error 0x3000) qt.qpa.wayland: Could not create EGL surface (EGL error 0x3000) qt.qpa.wayland: Could not create EGL surface (EGL error 0x3000) qt.qpa.wayland: Could not create EGL surface (EGL error 0x3000) qt.qpa.wayland: Could not create EGL surface (EGL error 0x3000) qt.qpa.wayland: Could not create EGL surface (EGL error 0x3000) qt.qpa.wayland: Could not create EGL surface (EGL error 0x3000) The Wayland connection experienced a fatal error: Invalid argument |
DISABLE_WAYLAND likely works only since system startup and up to the first launch without DISABLE_WAYLAND |
Steps to reproduce
I've upgraded from previous stable snap version. Old version was worked but new one doesn't run.
This is not working:
This is working:
Expected behaviour
The app should open. Logs in console:
Actual behaviour
The app is not running. Logs in console
Operating system
KUbuntu 25.04
Version of Telegram Desktop
5.14.3
Installation source
Snap
Crash ID
No response
Logs
The text was updated successfully, but these errors were encountered: