Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#58764 - [telegram-desktop] Alpha version in community
Attached to Project:
Community Packages
Opened by Thomas Avé (thomasave) - Monday, 28 May 2018, 19:07 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Tuesday, 05 June 2018, 08:46 GMT
Opened by Thomas Avé (thomasave) - Monday, 28 May 2018, 19:07 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Tuesday, 05 June 2018, 08:46 GMT
|
DetailsThe current version of the telegram-desktop package in the community repository is still in alpha (1.2.24-1).
I'm having problems with backticks for creating code blocks, which is quite logical in an alpha version. But what is not logical is that the only version available in the official repositories is an alpha version. The current stable version is 1.2.17. |
This task depends upon
Closed by Sven-Hendrik Haase (Svenstaro)
Tuesday, 05 June 2018, 08:46 GMT
Reason for closing: Fixed
Additional comments about closing: 1.3.0 in [community] is stable.
Tuesday, 05 June 2018, 08:46 GMT
Reason for closing: Fixed
Additional comments about closing: 1.3.0 in [community] is stable.
Comment by Eugenio M. Vigo (emvigo) -
Monday, 28 May 2018, 21:28 GMT
It's also barely usable under Wayland (it does works under X11, though). In fact, I went straight out to the upstream BTS to report it (https://github.com/telegramdesktop/tdesktop/issues/4750) and found out that the binaries they provide there don't have those problems under Wayland.
Comment by Antonio Rojas (arojas) -
Monday, 28 May 2018, 21:38 GMT
The Wayland issues have nothing to do with the Telegram version, but with Qt 5.11.
Comment by Eugenio M. Vigo (emvigo) -
Monday, 28 May 2018, 21:46 GMT
This is the only Qt5 application that's showing this behavior, AFAIK. (Of course, I'll be testing for others, just in case).