[Fedora-i18n-bugs] [Bug 1577234] New: Telegram hangs with fontconfig

https://bugzilla.redhat.com/show_bug.cgi?id=1577234

            Bug ID: 1577234
           Summary: Telegram hangs with fontconfig
           Product: Fedora
           Version: 28
         Component: fontconfig
          Assignee: tagoh(a)redhat.com
          Reporter: lukasz.wojnilowicz(a)gmail.com
        QA Contact: extras-qa(a)fedoraproject.org
                CC: ajax(a)redhat.com, alexl(a)redhat.com,
                    fonts-bugs(a)lists.fedoraproject.org,
                    i18n-bugs(a)lists.fedoraproject.org,
                    john.j5live(a)gmail.com, mbarnes(a)fastmail.com,
                    mclasen(a)redhat.com, pnemade(a)redhat.com,
                    rhughes(a)redhat.com, rstrode(a)redhat.com,
                    sandmann(a)redhat.com, tagoh(a)redhat.com



Created attachment 1434939
  --> https://bugzilla.redhat.com/attachment.cgi?id=1434939&action=edit
Terminal output

Description of problem:
Telegram hangs

Version-Release number of selected component (if applicable):
tsetup.1.2.17.tar.xz

How reproducible:
always

Steps to Reproduce:
1. start Telegram
2.
3.

Actual results:
Hang up.

Expected results:
No hang up.

Additional info:

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Fedora-i18n-bugs] [Bug 1577234] Telegram hangs with fontconfig

https://bugzilla.redhat.com/show_bug.cgi?id=1577234

Akira TAGOH <tagoh(a)redhat.com&gt; changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |CLOSED
         Resolution|---                         |NOTABUG
        Last Closed|                            |2018-05-16 08:58:06



--- Comment #1 from Akira TAGOH <tagoh(a)redhat.com&gt; ---
This is basically NOTOURBUG because Telegram statically links older fontconfig.
what you have options so far is to ask Telegram to update Telegram with
fontconfig 2.13 at least or ideally stop statically linking fontconfig in their
application.

If you can't wait for their action, you could do take this workaround, copy
fonts.conf to $HOME/.config/fontconfig and update the line like '<include
ignore_missing="yes">conf.d</include>' to the location where you
put the older
config files shipped in 2.12.6 or before. e.g. <include
ignore_missing="yes">/path/to/fontconfig-2.12.6/conf.d</include>

-- 
You are receiving this mail because:
You are on the CC list for the bug.