Arch Linux User Repository

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: https://github.com/ItachiSan/linux_packaging/issues If your issue is application-related, please report it upstream: https://github.com/telegramdesktop/tdesktop/issues

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

@ItachiSan If you want, I can be a contribuitor. I know how to update the hashes (did it manually on my desktop so the update telegram button goes away) even though I don't have too much knowledge in PKGBUILD files and in AUR itself (don't know how to write changes here).

@ItachiSan thank you for explanation. So it seems I haven't spotted those differences. So the only downside is that "update telegram" won't work if you use telegram-desktop-bin

@jakub the binary is the same; this package offer also the proper .desktop file, icons and more niceties packaged where they are supposed to be.

What's the benefit by using this package over tsetup*.tar.xz (updatable version) from https://desktop.telegram.org/?

@Feresey everyone was on holiday, no one asked to contribute :P Working on this ASAP (today I guess)

please add someone as contributor to update packages more promptly

Hi @everyone, Was on a business trip until Saturday. Will update the package ASAP.

@lybin now the protocol file is available for both KDE4 and KDE5 ;)

Please, change:

# KDE4 protocol file
install -d "$pkgdir/usr/share/kde4/services"
install -m644 "$srcdir/tg.protocol" "$pkgdir/usr/share/kde4/services/tg.protocol"

on

install -d "$pkgdir/usr/share/kservices5"
install -m644 "$srcdir/tg.protocol" "$pkgdir/usr/share/kservices5/tg.protocol"

Sorry guys, I'm moderate at best in the linux Community. can anyone tell me the difference between a a bin version (static binary) and a regular version of a package? i.e. what makes this different than telegram-desktop package?

Thanks!