Native Telegram stopped working after last week's updates

brent

elfprince WetGeek add me to the desktop-is-king user. Most of the world is happy with something tiny as their control center (a member of my family sold her laptop and cancelled her internet service claiming "my whole life is on my phone anyway"). I'm the opposite. I am not of the generation where I could watch a tv show or movie on a cell phone that is for sure.

WetGeek

brent "my whole life is on my phone anyway"

I know what you mean. My granddaughter eats lunch with her phone in one hand and a sandwich in the other. She's gotten really good at that. And her phone is tiny, even by smartphone standards.

elfprince

WetGeek Did she ever get confused and tried to take a chunk out of the phone? 🤣

WetGeek

elfprince Did she ever get confused and tried to take a chunk out of the phone?

Not yet, but one of these days ...

George

if i'm not mistaken, this commit help to resolve this issue https://github.com/telegramdesktop/tdesktop/pull/23897/commits/8ad7497b17d32e28c363a4babf116f83f397fca0

elfprince

George Are you saying that fix is on the way?

noise617

I have the same problem on Budgie Solus:

user@m700 ~ $ telegram
bash: telegram: command not found
user@m700 ~ $ telegram-desktop
<jemalloc>: Error in dlsym(RTLD_NEXT, "pthread_create"). Cannot enable background_thread

(telegram-desktop:35056): Telegram-WARNING **: 17:22:31.633: Application was built without embedded fonts, this may lead to font issues.
Aborted (core dumped)

brent

elfprince my impression was it was a known issue by telegram. maybe. team solus probably knows but I don't know that. that link is hard to interpret especially dev commentary but it mentioned a qt patch (I think) affecting telegram-desktop and launcher. no one came out and said 'the app can't launch'. see what @George says or a dev.
Good question.

elfprince

brent Yes, I wonder if he meant I need to install telegram from the net and then edit a file to add the patch. Not user level activity, I think. 😆

George

elfprince no, I just wanted to say that the bug was fixed in release 3.4.4 (current 3.5.2), In solus repo Telegram version 3.4.3

elfprince

George So that means, I need to wait until that version (3.4.4) comes to solus repo. 😃

brent

elfprince https://dev.getsol.us/D12614 looks like it was updated to 3.4.3 on Jan 6 of last month, so maybe Friday or next Friday. Likely they know.

tp199911

Hello,

I just installed a clean Solus 4.3 install, and my Telegram seems to have the same (or similar) issue. Not sure if I need to make a new post for this or if here is appropriate.
Running in Budgie gives nothing. Running in terminal outputs:
Aborted (core dumped)

~/.local/share/TelegramDesktop\log.txt reads:

 [2022.05.06 12:27:52] Launched version: 3007000, install beta: [FALSE], alpha: 0, debug mode: [FALSE]
[2022.05.06 12:27:52] Executable dir: /usr/bin/, name: telegram-desktop
[2022.05.06 12:27:52] Initial working dir: /home/thomas/
[2022.05.06 12:27:52] Working dir: /home/thomas/.local/share/TelegramDesktop/
[2022.05.06 12:27:52] Command line: telegram-desktop
[2022.05.06 12:27:52] Executable path before check: /usr/bin/telegram-desktop
[2022.05.06 12:27:52] Logs started
[2022.05.06 12:27:52] Launcher filename: telegramdesktop.desktop
[2022.05.06 12:27:52] IBus portal is present! Using it.
[2022.05.06 12:27:52] Getting DE, XDG_CURRENT_DESKTOP: 'Budgie:GNOME'
[2022.05.06 12:27:52] Getting DE, XDG_SESSION_DESKTOP: 'budgie-desktop'
[2022.05.06 12:27:52] Getting DE, DESKTOP_SESSION: 'budgie-desktop'
[2022.05.06 12:27:52] Getting DE via WM: 'Mutter(Budgie)'
[2022.05.06 12:27:52] Getting DE, GNOME_DESKTOP_SESSION_ID: ''
[2022.05.06 12:27:52] Getting DE, KDE_FULL_SESSION: ''
[2022.05.06 12:27:52] DE: Gnome
[2022.05.06 12:27:52] Connecting local socket to /run/user/1000/bca6c9e1ae6c20a82164739507ce3e29-{87A94AB0-E370-4cde-98D3-ACC110C5967D}...
[2022.05.06 12:27:52] Socket connect error 0, starting server and app...
[2022.05.06 12:27:52] Moved logging from '/home/thomas/.local/share/TelegramDesktop/log_start0.txt' to '/home/thomas/.local/share/TelegramDesktop/log.txt'!
[2022.05.06 12:27:52] Primary screen DPI: 120
[2022.05.06 12:27:52] Font: from ':/gui/fonts/DAOpenSansRegular.ttf' loaded 'DAOpenSansRegular'
[2022.05.06 12:27:52] Font: from ':/gui/fonts/DAVazirRegular.ttf' loaded 'DAVazirRegular'
[2022.05.06 12:27:52] Font: from ':/gui/fonts/DAOpenSansRegularItalic.ttf' loaded 'DAOpenSansRegularItalic'
[2022.05.06 12:27:52] Font: from ':/gui/fonts/DAVazirRegular.ttf' loaded 'DAVazirRegular'
[2022.05.06 12:27:52] Font: from ':/gui/fonts/DAOpenSansSemiboldAsBold.ttf' loaded 'DAOpenSansSemibold'
[2022.05.06 12:27:52] Font: from ':/gui/fonts/DAVazirMediumAsBold.ttf' loaded 'DAVazirMedium'
[2022.05.06 12:27:52] Font: from ':/gui/fonts/DAOpenSansSemiboldItalicAsBold.ttf' loaded 'DAOpenSansSemiboldItalic'
[2022.05.06 12:27:52] Font: from ':/gui/fonts/DAVazirMediumAsBold.ttf' loaded 'DAVazirMedium'
[2022.05.06 12:27:52] Font: from ':/gui/fonts/DAOpenSansSemiboldAsBold.ttf' loaded 'DAOpenSansSemibold'
[2022.05.06 12:27:52] Font: from ':/gui/fonts/DAVazirMediumAsBold.ttf' loaded 'DAVazirMedium'
[2022.05.06 12:27:52] Font: from ':/gui/fonts/DAOpenSansSemiboldItalicAsBold.ttf' loaded 'DAOpenSansSemiboldItalic'
[2022.05.06 12:27:52] Font: from ':/gui/fonts/DAVazirMediumAsBold.ttf' loaded 'DAVazirMedium'
[2022.05.06 12:27:52] Icon theme: Papirus
[2022.05.06 12:27:52] Fallback icon theme: 
[2022.05.06 12:27:52] Assertion Failed! "index < _sprites.size()" emoji_config.cpp:447

I have tried all suggestions above, including purge, dc, rmo + reboot. Nothing works.
Any suggestions?

Thanks in advance!

algent

tp199911 This problem is fixed in the Unstable repository. Next sync you will have it with the updates. I guess the sync with be today.

« Previous Page