-
Notifications
You must be signed in to change notification settings - Fork 5.3k
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 on Flatpak unexpectedly closes after a short time #25215
Comments
plz try downloading official version from https://desktop.telegram.org |
Flatpak is shown directly on that page you just linked, too. I used the command given there, and I don't believe I modified any of the settings. I'm still a bit unclear on what's the criteria for an "official" Flatpak, but the biggest contributor to telegram-desktop (John Preston) is among the contributors to the Flatpak, and the third biggest contributor to telegram-desktop (ilya-fedin) is the biggest contributor to the Flatpak. Sounds "official enough" to me, and it was also listed on the new issue page under the Installation source. I've successfully used the telegram-desktop package of my distribution before trying out this Flatpak. I did a system update after that, though. |
i mean the non-flatpak non-snap version. |
It doesn't appear to be crashing in the kind of short time period that I described. Yeah, I don't think it's a total inability in any way to use Telegram that's an issue for me. Just that sandboxed version of it. |
Maybe you've prohibited tdesktop to run in background once? flatpak remembers that and gives no way to reset that in any other way than CLI AFAIK: |
Yeah, it asked that at one point. I think I was looking into the setting of launching Telegram at startup. That's when it asked me, but I figured I could do the autostarting from Plasma's side without going into giving Telegram additional permissions, and didn't end up giving that permission. If it's such a crucial setting that can cause a lot of crashing without, maybe something should be done to make it so other users don't end up in this kind of a situation (unless maybe if they manually tamper with the sandbox settings). I do believe I even turned off the setting of autostarting afterwards, yet still apparently there were such problems. After putting in that command, I've not had such a crash. Such a toggle is also available in Flatseal. |
I don't think we have the right to alter the UI, sorry. You can try to submit an issue to https://github.com/flatpak/xdg-desktop-portal to separate autostart from background (currently you have to ask background permission in order to get autostart). |
Steps to reproduce
Expected behaviour
Telegram doesn't crash
Actual behaviour
$ flatpak run --branch=stable --arch=x86_64 --command=telegram-desktop --file-forwarding org.telegram.desktop --
Gtk-Message: 19:29:03.255: Failed to load module "canberra-gtk-module"
error: : cannot open
error: : cannot open
error: : cannot open
code 137
I did not notice substantial increase in memory usage.
I do believe it complained something about OpenGL not being available or something, but I pressed the option for it to not bother me about it.
There was a little bit of effort trying to get to debug this, but:
$ flatpak install org.telegram.desktop.Debug org.freedesktop.Platform.Debug
Looking for matches…
error: Nothing matches org.freedesktop.Platform.Debug in remote flathub
$ flatpak run --command=sh --devel org.telegram.desktop
error: runtime/org.freedesktop.Sdk/x86_64/21.08 not installed
Operating system
Arch Linux, Plasma
Version of Telegram Desktop
4.2.4
Installation source
Flatpak
Logs
The text was updated successfully, but these errors were encountered: