Package Details: telegram-desktop 1.0.2-1

Git Clone URL: https://aur.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: 99
Popularity: 9.181804
First Submitted: 2015-07-09 21:43
Last Updated: 2017-01-22 10:58

Dependencies (44)

Required by (1)

Sources (8)

Latest Comments

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

eduardosm commented on 2017-01-12 15:21

Add "-v" to the Qt5 configure command in the PKGBUILD and post the output again.

gimiki commented on 2017-01-12 15:05

I'm trying to update telegram but i get the following error:
HarfBuzz system library support cannot be enabled due to functionality tests!
Turn on verbose messaging (-v) to ./configure to see the final report.
If you believe this message is in error you may use the continue
switch (-continue) to ./configure to continue.
==> ERROR a failure occured in build().

console output: https://ghostbin.com/paste/4fnw4

How can i do?

sudokamikaze commented on 2017-01-11 23:59

Please update to 1.0.0

LKHN commented on 2016-12-19 15:30

@eduardosm Thank You Very Much updated and working fine!

eduardosm commented on 2016-12-19 13:18

@LKHN It is building right now

All comments