Community Packages

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!
Tasklist

FS#58453 - telegram-desktop: Font scanning on startup delays opening several minutes

Attached to Project: Community Packages
Opened by Javier Domingo Cansino (txomon) - Friday, 04 May 2018, 11:17 GMT
Last edited by Eli Schwartz (eschwartz) - Monday, 07 May 2018, 21:31 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Community package telegram-desktop is not the official distributed binary, and whilst the official binary has statically linked fontconfig, the community distributed one causes https://github.com/telegramdesktop/tdesktop/issues/4543#issuecomment-386289195

Additional info:
* package version(s): 1.2.17-1
* config and/or log files etc.


Steps to reproduce:

Details on the issue
This task depends upon

Closed by  Eli Schwartz (eschwartz)
Monday, 07 May 2018, 21:31 GMT
Reason for closing:  Upstream
Additional comments about closing:  The issue you linked explains exactly why this is not a distribution bug, but a telegram bug.
Comment by Eli Schwartz (eschwartz) - Monday, 07 May 2018, 21:31 GMT
That upstream ticket basically says that Telegram takes a lot of time to reindex the font cache, which makes no sense because that's what a cache is for and telegram should not be doing that.

The prebuilt binaries "get around this" by using an outdated static fontconfig, with the result that telegram cannot do any font detection at all -- so, skipping the fonts makes it load faster, but I'd hardly call that a solution.

Telegram should fix their code to not take several minutes to process fonts on startup. This is not a bug, it's a lack of performance optimization in the upstream codebase...

Loading...