Native Telegram stopped working after last week's updates

elfprince

I am on Solus running Budgie. This Monday I tried to start Telegram from my panel, with no response, aside from initial bouncing of the icon.
Then I tried to run from the terminal, with the following results:

~ $ telegram-desktop &
[1] 15429
017:27:24: ~ $ <jemalloc>: Error in dlsym(RTLD_NEXT, "pthread_create"). Cannot enable background_thread

(telegram-desktop:15429): Telegram-WARNING **: 17:27:25.435: Application was built without embedded fonts, this may lead to font issues.

[1]+ Aborted (core dumped) telegram-desktop

My guess is that the update broke something, and it has to do with fonts?

For now, I switched to flatpak Telegram. Would be nice to get back to Solus native one.

Any help is appreciated. Thanks.

brent

elfprince
a mystery.
*see nothing in dev tracker at all thats related
*internet shows the core dump is common error and fonts is usually one of many factors (in terminal error reports) and not really the cause. no SOLVEDS either just guesses
*"Error in dlsym(RTLD_NEXT, "pthread_create"). Cannot enable background_thread" this in threads alludes to "The dlsym() function allows a process to obtain the address of a symbol that is defined within a shared object or executable. The handle argument is either the value returned from a call to dlopen(), or one of a family of special handles. The name argument is the symbol's name as a character string." Not a lot of bulletin board stuff but many say it's related to broken links or syms.
*most peculiar is hovering a mouse of "0127:27:24" which says at the bottom of my browser: https://discuss/getsol.us/d/sasha@bunux. Click on that and this "The page you requested could not be found.
Return to Solus Forum" is on the page. Its possible it hyperlinked strangely when you cut and paste it.

Feels like a full moon for sure🙂.
I'm waiting for that one smart guy (always not me) to tell you in one sentence "oh yeah, someone just reported this at the telegram dev forum (make believe name) and it's related to a broken binding upstream and will be patched this weekend."

edit: word

prestocaso

you might try running the command "sudo eopkg check," and that will inform you of the status of your telegram install, if you haven't uninstalled.

WetGeek

prestocaso you might try running the command "sudo eopkg check"

Or try sudo eopkg check | grep Broken to display any lines that contain the word "Broken." Be patient with that one ... it takes a while to examine all those packages. If any broken ones are found, you can try reinstalling them with sudo eopkg it --reinstall pkg_name, where pkg_name is the name of the broken package. And if there's no problem with that command, you can quickly re-check just the one package with sudo eopkg check pkg_name.

Even better, someone once posted a macro that would search for broken packages and then fix anythat were found by reinstalling them. I no longer remember who that was, but perhaps somebody will.

brent

WetGeek Even better, someone once posted a macro that would search for broken packages and then fix anythat were found by reinstalling them. I no longer remember who that was, but perhaps somebody will.

sudo eopkg check | grep Broken | awk '{print $4}' | xargs sudo eopkg it --reinstall
or
sudo eopkg check | tee /dev/stderr | grep Broken | awk '{print $4}' | xargs sudo eopkg it --reinstall

both similar

elfprince

Thanks for your help guys. There are no broken packages. The situation persists even after uninstalling, and then reinstalling telegram-desktop. The error message does say that the package was built without embedded fonts.
The fact that this happened right after last Friday's updates makes me inclined to think that it was the cause.

drama

The same issue happened to me. I'm trying to use @WetGeek's command.

brent

https://bugs.telegram.org/c/8899 there was an old launch issue here
https://bugs.telegram.org/c/9438 and a font warning issue here
---devs say all things fixed with an update.
may join the choir here with check packages--your own hunch was something broke. its peculiar.
eopkg rmo or dc?

WetGeek

brent sudo eopkg check | grep Broken | awk '{print $4}' | xargs sudo eopkg it --reinstall

Thanks, Brent. This time I added to my bashrcAdditions file as an alias called "fixBroken". It could come in handy here some day.

gnomo223

Maybe delete cache and try to download again, i'm also not the smart guy 😃. It's weird that is something broken but there are no accused packages to be broken, maybe is a thing with the package itself

elfprince

check this out, weird

$ sudo eopkg check telegram-desktop
Password:
Package telegram-desktop not installed
012:04:23: ~ $ which telegram-desktop
/usr/bin/telegram-desktop

brent

elfprince the hyperlinked material refers back to this thread......way. too. weird.
sudo eopkg check however would show you if telegram had a broken run dependency.
eopkg info telegram might reflect a name change?

pomon

The package is called Telegram without Desktop. So sudo eopkg check telegram

elfprince

pomon The system found telegram-desktop, but NOT telegram. There is no Telegram or telegram installed. The binary is called telegram-desktop and is located in /usr/bin/telegram-desktop . This does not make sense at all.

And yet, it shows telegram-desktop NOT installed.

$ sudo eopkg check telegram-desktop
Package telegram-desktop not installed

nathanpainchaud

elfprince The name of the binary program you'll need to run to launch the program can be different from the name of the package to install. As pomon said, the package is named telegram, even if the executable is called telegram-desktop.

brent

if it was me and it was this weird (sometimes things get weird) I'd
remove program like geek said, purge dc and rmo, reboot, reinstall

elfprince

brent I will try that, thanks!

elfprince

brent @WetGeek , I followed the purge, dc, rmo and reboot. All is well now and Telegram is working again.

Thanks to all who pitched in. And, yes, I knew from start that telegram is the name of package and telegram-desktop is the name of the binary. 😆

Case closed.

elfprince

nathanpainchaud $ sudo eopkg it telegram
Password:
The following package(s) are already installed and are not going to be installed again:
telegram
No packages to install.

pomon

aquila@solus ~ $ sudo eopkg it telegram
Hasło: 
Following packages will be installed:
abseil-cpp  double-conversion  jemalloc  libb2        md4c      postgresql  qt6-5compat 
qt6-base    qt6-declarative    qt6-svg   qt6-wayland  telegram  tslib       zlib-minizip
Total size of package(s): 44.39 MB
There are extra packages due to dependencies. Do you want to continue?(Tak / nie)

$ sudo eopkg check telegram Hasło: Checking integrity of telegram OK

$ telegram-desktop

brent

pomon so telegram-desktop is a component/dep/part of telegram? Is that what I'm seeing?
I thought binary=telegram-desktop and package name=telegram but they were, you said, identical entities. Unless I'm seeing all wrong

nathanpainchaud

brent telegram-desktop is indeed the name of the binary program that is installed when you install the package telegram. So they're not really the same thing, but one comes with the other. But really at this point it's just semantics.