Package Details: telegram-desktop-bin 2.2.0-1

Git Clone URL: (read-only, click to copy)
Package Base: telegram-desktop-bin
Description: Official desktop version of Telegram messaging app - Static binaries
Upstream URL:
Licenses: GPL3
Conflicts: telegram-desktop
Provides: telegram-desktop
Replaces: telegram-bin
Submitter: ItachiSan
Maintainer: ItachiSan
Last Packager: ItachiSan
Votes: 660
Popularity: 3.97
First Submitted: 2015-07-08 10:21
Last Updated: 2020-07-27 15:46

Dependencies (9)

Required by (1)

Sources (11)

Pinned Comments

ItachiSan commented on 2017-02-04 12:58

NOTICE: if one of your comment fall back in one of this entries, I will act without replying here in comment. If you have issues for that, write a comment down here and I might reply you. If the answer to a problem is here, though, don't expect any soon, as I believe you will read this first.

So, a few considerations to sum up most important stuff (FAQ-alike):

  • sorry to put this on top, but many users flag this package as outdated due to icons checksums. The checksums I do provide are the one of the pictures I downloaded and checked; if icon checksums fail, delete icon files and re-run makepkg.

  • This package tracks the stable releases; for the development version, check telegram-desktop-bin-dev. Every time this package will be marked as outdated because of a development release, it will just be unflagged.

  • the executable creates a custom, usually malformed, launcher, which is located at $HOME/.local/share/applications/telegramdesktop.desktop, so, you can either remove it or make it unreadable (kind of) with chattr +a $HOME/.local/share/applications/telegramdesktop.desktop. I personally suggest the second one. (thanks to @DragonX256, @lybin and @evilgnome for pointing this out)

  • this pre-built binary has no Wayland support. So, for working tray-icon, change the launcher using env GDK_BACKEND=x11 telegram as executable (thanks @nebulon for the suggestion). My suggestion is to copy the launcher inside the package in .local/share/applications and tweak your user copy. If you really want Wayland support, you can use the official package telegram-desktop.

  • The package is updated whenever the built binary is online AND I have time. So, reporting the outdated package HIGHLY helps me (it reminds me to do it), comments asking for updates ASAP... not really.

  • Feel free to report packaging bugs here in the comments or at my PKGBUILD repository: If your issue is application-related, please report it upstream:

I will add useful stuff to this comment when I notice it, with also proper credits.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 ... Next › Last »

ItachiSan commented on 2017-08-10 20:41

@levitsky not really a need to. Not really having that many holidays.

levitsky commented on 2017-08-09 19:27

The package is outdated for two weeks now. Maybe you could add a co-maintainer at least for simple stuff like version bumps. I, for example, would probably be able to do that on most days.

s13g3lb4um commented on 2017-08-07 03:38


sha256sums for x64 = 4ef097787f2ec3f4d9403fc7767a71c4f822b790c64eb9c23357040513f792f5

sha256sums for x86 = 11fcd4f55846bbc2dd844c8bd28c3a11bd8b5294e16f98ac081524a5d36f00b4

whit this changes the new version is available

zerezhka commented on 2017-08-01 09:27

If you want latest version, try it. It's works for me.

I replaced current strings in PKGBUILD:
(line 6)


(line 41, delete/comment with "#" all sha256..%blabla%
sorry that i don't understand how to generate sha256sums and use just mkpkg -g
and generate only md5sums)


ItachiSan commented on 2017-08-01 08:04

After 2 months without break (thanks exams) from university, I am on holiday, so please wait for the update. I will be back home next week and update the packages.

@fightcookie thank you indeed for the suggestion. That would make sure people read the proper info.

Plexcon commented on 2017-07-31 06:38

update v.1.1.18, please

xuiqzy commented on 2017-07-30 23:04

It would be extremely useful to have the explanation as to why we need to remove the created launcher .desktop file in the post install comments!
The other infos from the pinned comment are also really helpful and could benefit more people if they were in the post install section.

Thanks in advance! :)

aphirst commented on 2017-07-27 16:33

If there's a new version upstream (but not yet installed), Telegram auto-applies that update when I restart the application. This /appears/ to work, and displays a notification detailing the new version, BUT when restarting the application again the profile is entirely lost and needs to be re-authenticated from scratch, insodoing reverting the version again.

Is this a known bug?

lybin commented on 2017-07-27 09:22

5bbea3a914bb1a65ece2a2697ca7dcefee9e4b48e642df2ac214ed259ef91cf7 ./tsetup.1.1.17.tar.xz

snqlby commented on 2017-07-03 09:14

Just Do It, ItachiSan
Do It