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#73252 - telegram-desktop latest (3.4.3) refuses to start under Wayland
Attached to Project:
Community Packages
Opened by Pato05 (pato05) - Tuesday, 04 January 2022, 12:47 GMT
Last edited by Antonio Rojas (arojas) - Tuesday, 04 January 2022, 18:01 GMT
Opened by Pato05 (pato05) - Tuesday, 04 January 2022, 12:47 GMT
Last edited by Antonio Rojas (arojas) - Tuesday, 04 January 2022, 18:01 GMT
|
DetailsDescription:
The telegram-desktop client refuses to start natively under Wayland, even with the QT_QPA_PLATFORM=wayland environment flag set. Running GNOME 41.2 under Wayland. Additional info: * package version(s): 3.4.3 * config and/or log files etc.: there is no particular log entry suggesting the program has ignored the flag for any reason. * link to upstream bug report, if any Steps to reproduce: Start telegram-desktop with the QT_QPA_PLATFORM=wayland flag. |
This task depends upon
Closed by Antonio Rojas (arojas)
Tuesday, 04 January 2022, 18:01 GMT
Reason for closing: Not a bug
Additional comments about closing: Intentional behavior
Tuesday, 04 January 2022, 18:01 GMT
Reason for closing: Not a bug
Additional comments about closing: Intentional behavior
Comment by q rty (q234rty) -
Tuesday, 04 January 2022, 16:17 GMT
Seems to be intentionally disabled upstream: https://github.com/telegramdesktop/tdesktop/commit/102c0a96ed5cbc1288e1654b7e12811f1ea378b5
Comment by q rty (q234rty) -
Tuesday, 04 January 2022, 16:20 GMT
For native wayland on qt with GNOME on arch, personally I think the main blocker is https://bugreports.qt.io/browse/QTBUG-87303.