https://bugzilla.redhat.com/show_bug.cgi?id=840885
--- Comment #14 from Bill Nottingham <notting(a)redhat.com> ---
I've added langinstall, langremove, and langlist commands to
yum-langpacks-0.3.0, and am pushing it to F-18 and F-17. Please let me know how
this works for you.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=570712
--- Comment #17 from mohammad.nayeem(a)gmail.com ---
I have completed step 1 above.
Do I have to wait until I see it in the translation link of step 2?
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=570712
Pravin Satpute <psatpute(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Comment #16 is|1 |0
private| |
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=845480
Bug ID: 845480
QA Contact: extras-qa(a)fedoraproject.org
Severity: unspecified
Version: 17
Priority: unspecified
CC: i18n-bugs(a)lists.fedoraproject.org,
petersen(a)redhat.com, pnemade(a)redhat.com,
psatpute(a)redhat.com
Assignee: pnemade(a)redhat.com
Summary: autohint improves rendering lot
Regression: ---
Story Points: ---
Classification: Fedora
OS: Unspecified
Reporter: psatpute(a)redhat.com
Type: Bug
Documentation: ---
Hardware: Unspecified
Mount Type: ---
Status: NEW
Component: madan-fonts
Product: Fedora
Created attachment 602080
--> https://bugzilla.redhat.com/attachment.cgi?id=602080&action=edit
image without autohint
Description of problem:
without autohint, rendered image outline is not smooth
Version-Release number of selected component (if applicable):
madan-fonts-2.000-6.fc17.noarch
How reproducible:
everytime
Steps to Reproduce:
1.
2.
3.
Actual results:
outline looks broken, inconsistent thickness.
Expected results:
outline should be smooth
Additional info:
In F18 we are going to have default autohint, but might be good have this
enabled in fontconf file as well
--
You are receiving this mail because:
You are on the CC list for the bug.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: [ru_RU] Not displayed Russian symbols in console again
https://bugzilla.redhat.com/show_bug.cgi?id=700971
Summary: [ru_RU] Not displayed Russian symbols in console again
Product: Fedora
Version: 15
Platform: Unspecified
OS/Version: Unspecified
Status: NEW
Keywords: i18n
Severity: unspecified
Priority: unspecified
Component: dracut
AssignedTo: harald(a)redhat.com
ReportedBy: lpoetter(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: notting(a)redhat.com, harald(a)redhat.com,
rstrode(a)redhat.com, aalam(a)redhat.com, atigro(a)ya.ru,
mschmidt(a)redhat.com, vcrhonek(a)redhat.com,
jonathan(a)jonmasters.org, lpoetter(a)redhat.com,
i18n-bugs(a)lists.fedoraproject.org,
plautrba(a)redhat.com, iarlyy(a)gmail.com,
elemc(a)atisserv.ru, metherid(a)gmail.com,
johannbg(a)gmail.com
Depends on: 699282
Classification: Fedora
Story Points: ---
Clone Of: 699282
+++ This bug was initially created as a clone of Bug #699282 +++
Description of problem:
After system boot up, I've switched to console (Ctrl-Alt-F2), login and run mc
(Midnight Commander) or another application with Russian symbols.
Russian symbols not displayed, again. Like this was in Fedora 12.
Version-Release number of selected component (if applicable):
initscripts-9.29
How reproducible:
always
Steps to Reproduce:
1. Boot system
2. switch to console
3. run application with Russian symbols, as example LANG=ru_RU.UTF-8 mc
Actual results:
White squares instead Russian symbols.
Expected results:
Russian symbols displayed correctly.
Additional info:
I've find workaround or patch.
If I change this line in /lib/udev/rules.d/10-console.rules:
KERNEL=="tty0",><------>RUN+="/lib/udev/console_init %k"
like this:
KERNEL=="tty*",><------>RUN+="/lib/udev/console_init %k"
then Russian symbols displayed correctly.
--- Additional comment from atigro(a)ya.ru on 2011-04-24 23:34:08 CEST ---
In earlier dracut (in F14) initramfs image contained system binary
/lib/udev/console_init from initscripts. Maybe it is the second way to fix this
problem:
https://github.com/RussianFedora/dracut/blob/f15%2Ffixes/dracut-009-console…
--- Additional comment from lpoetter(a)redhat.com on 2011-04-27 02:30:00 CEST ---
systemd-vconsole should be responsible for setting that up.
Does invoking /lib/systemd/systemd-vconsole-setup manually make things work for
you?
What is the content of /etc/sysconfig/i18n?
--- Additional comment from elemc(a)atisserv.ru on 2011-04-27 19:59:39 CEST ---
Yes, after run /lib/systemd/systemd-vconsole-setup in console Russian symbols
displayed correctly.
cat /etc/sysconfig/i18n
LANG="ru_RU.UTF-8"
--- Additional comment from lpoetter(a)redhat.com on 2011-04-28 00:39:26 CEST ---
Which systemd version is this?
Normally /lib/systemd/systemd-vconsole-setup should run at boot.
Can you do "systemctl --full | grep vconsole" after boot when the problem
happened and paste the output here?
--- Additional comment from elemc(a)atisserv.ru on 2011-04-28 08:31:27 CEST ---
# yum list installed systemd*
systemd.x86_64 25-1.fc15 @updates-testing
systemd-units.x86_64 25-1.fc15 @updates-testing
I've booted and checked what problem still persist.
# systemctl --full | grep vconsole
systemd-vconsole-setup.service loaded active exited Setup Virtual
Console
--- Additional comment from mschmidt(a)redhat.com on 2011-04-28 10:52:30 CEST ---
Can you boot with "rd.plymouth=0"? Do the fonts appear correctly then?
--- Additional comment from elemc(a)atisserv.ru on 2011-04-28 11:05:39 CEST ---
Yes, with rd.plymouth=0 kernel parameter the fonts appear correctly.
--- Additional comment from lpoetter(a)redhat.com on 2011-04-28 16:54:36 CEST ---
Hmm, Ray, have you heard of such a problem with font loading and Plymouth
colliding?
--- Additional comment from lpoetter(a)redhat.com on 2011-04-28 16:59:20 CEST ---
OK, my guess is that this might be related to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/554172/comments/245
i.e. setfont should probably retry opening /dev/tty0 a couple of times.
--- Additional comment from lpoetter(a)redhat.com on 2011-04-28 17:06:38 CEST ---
Tentatively reassigning this to kbd. The EIO loop is definitely necessary in
kbd. It might fix this problem. If it doesn't feel free to reassign back.
kbd maintainers, can you please beef up open_a_console() in src/getf_fd.c to
loop a couple of times if you get EIO when opening the device? Since the BKL
was dropped in the kernel this is unfortunately necessary in userspace to make
things work race-freely, see the linked ubuntu bug.
We do a similar loop in systemd:
http://cgit.freedesktop.org/systemd/tree/src/util.c#n2326
--- Additional comment from notting(a)redhat.com on 2011-04-28 18:38:23 CEST ---
(In reply to comment #8)
> Hmm, Ray, have you heard of such a problem with font loading and Plymouth
> colliding?
vconsole setup needs done before plymouth sets the terminal to graphics
mode/the framebuffer driver is loaded, IIRC.
(font/unicode state is per-VT, but inherited from the prior existing console)
--- Additional comment from lpoetter(a)redhat.com on 2011-04-30 03:45:44 CEST ---
OK, will duplicate against dracut then, which apparently dropped the font
loading.
Harald, please add an invocation of systemd-vconsole-setup to dracut, before
you run plymouth, as discussed on IRC the other day.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=699282
--- Comment #14 from Fedora End Of Life <endoflife(a)fedoraproject.org> ---
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.
(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=699282
Fedora End Of Life <endoflife(a)fedoraproject.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |CLOSED
Resolution|--- |WONTFIX
Last Closed| |2012-08-07 16:06:50
--
You are receiving this mail because:
You are on the CC list for the bug.