Native Telegram stopped working after last week's updates

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.

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.

brent

nathanpainchaud I got it thank you. I always strive for accuracy so I always want to know.
elfprince yay! at the end of the day some debris got in your way

elfprince

UPDATE: As of this morning's (Saturday), the same issue resurfaced. Native telegram refuses to start up. Same error message in terminal as above. I am not going to keep chasing my tail, but instead will use the flatpak version until native telegram is fixed. Lucky we have options. 😄

nathanpainchaud

elfprince I suspect your issues with Telegram are specific to your setup, because I have native Telegram installed here, and it's been running fine in the last few days.

pomon

There is still a download option wget -O telegram.tar.xz https://telegram.org/dl/desktop/linux
Unpack tar xf telegram.tar.xz
Use: Double-click Telegram
Alternatively, add through menuelibre to the Start menu

elfprince

nathanpainchaud That is good to hear.

brent

nathanpainchaud could be. i have camera/location/microphone forced off in budgie system settings. but zoom can get around it. other things cannot. some apps have to ask and get exceptions because of my policy and some apps just hit the wall and won't function. elfprince maybe its something like that I wonder? "lucky we have options" I say that all the time, too🙂

elfprince

brent It just stopped working, got 'fixed' using steps described above, and stopped again the next day (today) on a fresh boot with the same symptoms. I use it all the time, so for me it is more important to find another working good source, than bang my head against the wall trying to fix the native one.
My 2 cents: ALWAYS have a backup plan, because you never know.. 😀

brent

elfprince oh yes. when flatpak zoom died (a necessary part of my life) I grabbed the appimage and built from targz source so I had two backups. You never know is right

« Previous Page Next Page »