Package Details: telegram-desktop 1.0.6-1

Git Clone URL: https://aur-dev.archlinux.org/telegram-desktop.git (read-only)
Package Base: telegram-desktop
Description: Official desktop version of Telegram messaging app.
Upstream URL: https://desktop.telegram.org/
Licenses: GPL3
Submitter: eduardosm
Maintainer: eduardosm
Last Packager: eduardosm
Votes: 101
Popularity: 8.830557
First Submitted: 2015-07-09 21:43
Last Updated: 2017-02-02 08:42

Dependencies (44)

Required by (1)

Sources (8)

Latest Comments

hexchain commented on 2017-02-04 04:14

@eduardosm: That's a bit strange, since I don't have any problems with emoji (because tdesktop replaces all emojis with their custom sprite sheet).

And, +1 for a separate package for now.

@hobarrera: tdesktop have their custom patches[1] to Qt and some 3rd party libraries. Those patches are very dirty, most of them are used to access private constructors or hardcode font settings. And because of this they need to build Qt statically into the binary instead of using the system version.

The patches I post is from a Debian contributor. From what I see, these patches 1) have some modifications into the build process (to compensate for the original GYP patches) 2) have some behavioral difference from the original client[2], so I don't expect them to be accepted upstream.

[1] https://github.com/telegramdesktop/tdesktop/tree/master/Telegram/Patches/
[2] https://github.com/mymedia2/tdesktop/tree/debian/1.0.6-1/debian

hobarrera commented on 2017-02-03 18:27

@hexchain What are the changes in telegram resulting from building with those patches? Why haven't they been accepted upstream?

eduardosm commented on 2017-02-03 17:54

@hexchain Thanks for the PKGBUILD! I could build and run it successfully, but emojis don't show. So, I think we could create a separate package (named telegram-desktop-dynqt for example) and mark it as experimental.

hexchain commented on 2017-02-03 12:10

I've tried integrating the patches, and with some modifications to both the patch and the PKGBUILD here is the result srcball: https://paste.xinu.at/09kfBH/

hexchain commented on 2017-02-02 17:13

A great guy made some patches to build telegram-desktop without building Qt. Patches here: https://github.com/mymedia2/tdesktop/tree/debian/1.0.6-1/debian/patches

Any chances we can adopt them?

eduardosm commented on 2017-01-13 19:11

@baudlord I am aware wayland-egl does not work, but I don't know how to get it working with static linking.

baudlord commented on 2017-01-13 17:09

Under sway and using QT_QPA_PLATFORM=wayland, it is very laggy.
Also it does not work with QT_QPA_PLATFORM=wayland-egl, and upon execution with QT_DEBUG_PLUGINS=1 it shows the following output, which leads me to think maybe it's not linking the wayland-egl plugin properly?

QFactoryLoader::QFactoryLoader() ignoring "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3" since plugins are disabled in static builds
QFactoryLoader::QFactoryLoader() ignoring "org.qt-project.Qt.QPA.QPlatformThemeFactoryInterface.5.1" since plugins are disabled in static builds
QFactoryLoader::QFactoryLoader() ignoring "org.qt-project.Qt.QStyleFactoryInterface" since plugins are disabled in static builds
loaded library "appindicator3"
loaded library "appindicator3"
loaded library "appindicator"
loaded library "gtk-x11-2.0"
loaded library "notify"
connect(2) call to /dev/shm/jack-1000/default/jack_0 failed (err=No such file or directory)
attempt to connect to server failed

(telegram-desktop:15371): libnotify-WARNING **: Failed to connect to proxy
QFactoryLoader::QFactoryLoader() ignoring "org.qt-project.Qt.QImageIOHandlerFactoryInterface" since plugins are disabled in static builds
QFactoryLoader::QFactoryLoader() ignoring "org.qt-project.Qt.QIconEngineFactoryInterface" since plugins are disabled in static builds
QFactoryLoader::QFactoryLoader() ignoring "org.qt-project.Qt.WaylandClient.QWaylandClientBufferIntegrationFactoryInterface.5.3" since plugins are disabled in static builds
Failed to load client buffer integration: wayland-egl

QFactoryLoader::QFactoryLoader() ignoring "org.qt-project.Qt.QBearerEngineFactoryInterface" since plugins are disabled in static builds
loaded library "crypto"
loaded library "ssl"
QFactoryLoader::QFactoryLoader() ignoring "org.qt-project.Qt.QAccessibleFactoryInterface" since plugins are disabled in static builds
QFactoryLoader::QFactoryLoader() ignoring "org.qt-project.Qt.QAccessibleBridgeFactoryInterface" since plugins are disabled in static builds
The Wayland connection broke. Did the Wayland compositor die?
QLibraryPrivate::unload succeeded on "appindicator" (faked)
QLibraryPrivate::unload succeeded on "crypto" (faked)
QLibraryPrivate::unload succeeded on "gtk-x11-2.0" (faked)
QLibraryPrivate::unload succeeded on "notify" (faked)
QLibraryPrivate::unload succeeded on "ssl" (faked)
AL lib: (EE) alc_cleanup: 1 device not closed

gimiki commented on 2017-01-12 15:50

@cippaciong : yes, I'll try it. Thanks.

EDIT: It works!

cippaciong commented on 2017-01-12 15:45

gimki: are you using Infinality? The reason is probably that you have an old version of freetype2.
You can find more info here: https://gist.github.com/cryzed/e002e7057435f02cc7894b9e748c5671

gimiki commented on 2017-01-12 15:42

https://ghostbin.com/paste/vrthz

All comments