[Fedora-i18n-bugs] [Bug 1648825] Split and update smc-fonts to match upstream release
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1648825
--- Comment #8 from Nicolas Mailhot <nicolas.mailhot(a)laposte.net> ---
If you can build from sources please do so. That's the only way to make sure
our font building infra is sane and we will be able to use it the day someone
needs a fix in the font files and upstream is busy somewhere else. (and that
also makes sure Fedora is something upstream can rely on should it need to).
DejaVu for example builds fine from source in Fedora, that's the result of a
cooperation between us and the font project to fix the required Makefile parts.
--
You are receiving this mail because:
You are on the CC list for the bug.
5 years, 1 month
[Fedora-i18n-bugs] [Bug 1679619] New: Undefined symbol in libfontconfig prevents any graphical activity (booting also).
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1679619
Bug ID: 1679619
Summary: Undefined symbol in libfontconfig prevents any
graphical activity (booting also).
Product: Fedora
Version: 29
Hardware: x86_64
OS: Linux
Status: NEW
Component: fontconfig
Severity: urgent
Assignee: tagoh(a)redhat.com
Reporter: artu72(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: ajax(a)redhat.com, caillon+fedoraproject(a)gmail.com,
fonts-bugs(a)lists.fedoraproject.org,
gnome-sig(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org,
john.j5live(a)gmail.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
Target Milestone: ---
Classification: Fedora
Description of problem:
While booting the system, gdm-wayland-session complains undefined symbol
FT_Done_MM_Var in libfontconfig, the same behaviour occurs issuing a startx
from a textual console in a system started without graphical level.
Version-Release number of selected component (if applicable):
fontconfig-2.13.1-3.fc29.x86_64.rpm
How reproducible:
Always.
Steps to Reproduce:
1. Boot the system with default settings.
2.
3.
Actual results:
Booting hangs on a blank screen with a steady cursor.
Expected results:
Plymouth screen with fedora logo, then a X session.
Additional info:
I am providing journal and boot logs links on fedora paste:
https://paste.fedoraproject.org/paste/oWkRwE6zFksSwcw4RDPFSA
--
You are receiving this mail because:
You are on the CC list for the bug.
5 years, 1 month