[Bug 1532523] New: [google-droid-fonts] rebase to latest version
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1532523
Bug ID: 1532523
Summary: [google-droid-fonts] rebase to latest version
Product: Fedora
Version: rawhide
Component: google-droid-fonts
Keywords: Improvement, Rebase
Severity: high
Priority: high
Assignee: nicolas.mailhot(a)laposte.net
Reporter: dkaspar(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: fonts-bugs(a)lists.fedoraproject.org,
nicolas.mailhot(a)laposte.net, paul(a)frixxon.co.uk,
tremble(a)tremble.org.uk
Description of problem:
Currently we are using outdated font versions (of google-droid-fonts) in
Fedora.
Version-Release number of selected component (if applicable):
google-droid-fonts-20120715-12.fc27
Expected results:
I would hereby like to request a rebase to latest version of
google-droid-fonts.
Additional info:
One of these fonts (DroidSansFallback.ttf) in the package is necessary for
Ghostscript to function correctly when rendering CJK glyphs.
And according to the Fedora Packaging Guidelines packages are forbidden to
bundle fonts inside them, therefore I am using the google-droid-fonts package.
But it's content is way older than what Ghostscript currently needs.
NOTE:
In case none of the maintainers is currently available, I'm able and willing to
do this rebase myself (I'm already maintainer of urw-base35-fonts) to help you.
You would just have to set commit right for me in the Pagure
(https://src.fedoraproject.org/rpms/google-droid-fonts).
--
You are receiving this mail because:
You are on the CC list for the bug.
6 years
[Bug 1515436] New: gnome-shell crashes with attached stacktrace:
FcConfigEvaluate at top of stack.
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1515436
Bug ID: 1515436
Summary: gnome-shell crashes with attached stacktrace:
FcConfigEvaluate at top of stack.
Product: Fedora
Version: 26
Component: fontconfig
Severity: high
Assignee: tagoh(a)redhat.com
Reporter: ndokos(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: ajax(a)redhat.com, alexl(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, 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 1356104
--> https://bugzilla.redhat.com/attachment.cgi?id=1356104&action=edit
stacktrace of gnome-shell crash.
Description of problem:
I run Fedora 26 on a Lenovo Thinkpad W541. I ran a "dnf update" last Friday
(2017-11-17) and after the update I could not login with any Gnome choice:
Gnome, Gnome Classic, or Gnome on X11 - after a couple of burps on the display,
it would return to the login prompt. I installed the cinnamon desktop and was
able to log in with that.
It turns out that gnome-shell crashes in FcConfigEvaluate - see attached
stacktrace.
Version-Release number of selected component (if applicable):
fontconfig.x86_64 2.12.6-4.fc26
@updates
How reproducible:
Always.
Steps to Reproduce:
1. dnf update
2. reboot
3. login
Actual results:
Churn a bit and then return to the login screen.
Expected results:
Successful login.
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
6 years
[Bug 1474257] New: fc-cache in multilib does not create 32bit cache
files
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1474257
Bug ID: 1474257
Summary: fc-cache in multilib does not create 32bit cache files
Product: Fedora
Version: rawhide
Component: fontconfig
Assignee: tagoh(a)redhat.com
Reporter: tagoh(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: fonts-bugs(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org, pnemade(a)redhat.com,
tagoh(a)redhat.com
Blocks: 1468978
Description of problem:
On 64bit env, there are no way to generate {be,le}32d{4,8} caches unless
removing 64bit version of packages because the 32bit version of fc-cache binary
is hidden by the package manager. need to have separate binary to address like
gtk does.
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1468978
[Bug 1468978] fc-cache in multilib does not create 32bit cache files
--
You are receiving this mail because:
You are on the CC list for the bug.
6 years
[Bug 1551221] New:
iso8859-2-100dpi-fonts fonts.alias wrongly claims the fonts are scalable
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1551221
Bug ID: 1551221
Summary: iso8859-2-100dpi-fonts fonts.alias wrongly claims the
fonts are scalable
Product: Fedora
Version: 27
Component: iso8859-2-fonts
Assignee: pnemade(a)redhat.com
Reporter: hdegoede(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: fonts-bugs(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org, pnemade(a)redhat.com
/usr/share/fonts/iso8859-2/100dpi/fonts.alias contains entries like:
-adobe-utopia-regular-i-normal--0-0-100-100-p-0-iso8859-2
-biznet-chimera-regular-i-normal--0-0-100-100-p-0-iso8859-2
-adobe-utopia-regular-r-normal--0-0-100-100-p-0-iso8859-2
-biznet-chimera-regular-r-normal--0-0-100-100-p-0-iso8859-2
etc.
These entries, with a "0" after the "--" cause apps to think that scalable
versions of these fonts are available, but the fonts installed by
iso8859-2-100dpi-fonts are not scalable at all.
This has caused my a great deal of problems while debugging bug 1523624.
Please remove the entries with "--0" in them from the fonts.alias file.
--
You are receiving this mail because:
You are on the CC list for the bug.
6 years
[Bug 1530846] gitk fails to start
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1530846
Paolo Bonzini <pbonzini(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |CLOSED
Resolution|--- |NOTABUG
Last Closed| |2018-03-20 07:22:17
--- Comment #5 from Paolo Bonzini <pbonzini(a)redhat.com> ---
Fixed by fontconfig-2.13.0-3.fc28.x86_64 (patch fontconfig-locale.patch).
--
You are receiving this mail because:
You are on the CC list for the bug.
6 years, 1 month