Closed JazzTp closed 10 months ago
latest requires GLIBC-2.28 which is unavailable on this pretty old Ubuntu system
Was about to say, it appears Ubuntu 18.04 reached end of life in May of this year (2023), approximately 8 months ago. Pretty unlikely to have apps support an unsupported OS re: libraries and whatnot, as you mentioned.
EOL source: https://ubuntu.com/about/release-cycle
latest requires GLIBC-2.28 which is unavailable on this pretty old Ubuntu system
Was about to say, it appears Ubuntu 18.04 reached end of life in May of this year (2023), approximately 8 months ago. Pretty unlikely to have apps support an unsupported OS re: libraries and whatnot, as you mentioned.
EOL source: https://ubuntu.com/about/release-cycle
Yes long due upgrade, plenty of things to do and plenty of stuff I'm still using on this PC as it is.
But that's what flatpak normally overcomes, as I said I have other programs requiring GLIBC-2.28 and their flatpak distribution works just fine.
Anyways, you certainly have priorities, I reported just in case it serves (no problems for me, I've already connected another disk to put a new OS on it, a few others I know might not sort it out as quickly but as I said you certainly have priorities).
I have the same problem on Fedora 39 and Nvidia 545.29.06. I don't see the OpenGL notification though. When I open Telegram, its window is glitched first ~10 seconds. Then I type in my phone number, press next and nothing happens.
I downloaded Telegram from telegram.org and it works fine. Only Flathub and Arch builds are broken.
Snap package also appears to be broken with the same behaviour, on Ubuntu 23.10, with Nvidia 525/535.
Note that, after a few tries, it'll eventually hang for 30 seconds and then appear, and proceed to do absolutely nothing (no QR shows up, phone number input does nothing, etc). Launching the Snap or flatpak package from command line shows the same behaviour.
The not-containerized version of Telegram works perfectly, but also I'm a bit too lazy to set up a .desktop
for it.
Folks, please stop mixing various issues here. The first post of the issue is about non-working 'keep disabled' button. If your problem is not with the button, you don't have this issue.
The not-containerized version of Telegram works perfectly, but also I'm a bit too lazy to set up a
.desktop
for it.
This is done automatically, you don't have to do that.
From Flatseal Enable D-Bass System Bus and it will work
I don't think this can really help cause tdesktop doesn't use the system bus
Steps to reproduce
Expected behaviour
I'd expect it to start just fine.
I have non-flatpak Telegram desktop ver 4.4.1 running fine (but the latest requires GLIBC-2.28 which is unavailable on this pretty old Ubuntu system).
I have other flatpak programs running fine (which wouldn't run as normal binaries because they also require GLIBC-2.28).
Actual behaviour
If I click on "Keep Disabled" nothing happens, "action" only starts again by clicking "Enable".
Console output:
As for "Could not open network socket": I am online, I opened for output to any destination IP (I opened the firewall to the most permissive settings, everything else is working fine; non-flatpak Telegram desktop also works fine with my usual firewall settings).
As for OpenGL (see screenshot above): no other program is complaining about that here, including the ones I have installed as flatpak.
Operating system
Linux Ubuntu 18.04.6 LTS - NVidia driver ver 390.157
Version of Telegram Desktop
4.12.2 ("Changes in version 4.12.2" I'm reading here https://flathub.org/apps/org.telegram.desktop)
Installation source
Flatpak
Crash ID
I don't see how to enter Settings to enable beta versions and issue a cheat code, since I can't launch the GUI at all.
Also, I don't find anything related with Telegram under ~/.config/
Could anybody please point me to a settings file, specifically the one the flatpak version would use, where I could enable beta versions, and to an alternative command line interface, if any, through which I might issue the necessary cheat codes, if necessary?
Logs
Please see the above section "Crash ID".