Bug 888721

Summary:	Setting font to latarcyrheb-sun16 doesn't work as expected
Product:	[Fedora] Fedora	Reporter:	Vratislav Podzimek <vpodzime>
Component:	systemd	Assignee:	systemd-maint
Status:	CLOSED WORKSFORME	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	18	CC:	atigro, johannbg, lnykryn, metherid, msekleta, notting, plautrba, systemd-maint, vpavlin
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-01-14 17:47:59 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	869233

Description Vratislav Podzimek 2012-12-19 10:42:02 UTC

Description of problem:
When I have:

KEYMAP="cz"
FONT="latarcyrheb-sun16"

in /etc/vconsole.conf and type non-ascii characters, they are not correclty displayed.

Version-Release number of selected component (if applicable):
systemd-195-10.fc18.x86_64

How reproducible:
100 %

Steps to Reproduce:
1. change /etc/vconsole.conf contents to the two lines mentioned in the description 
2. reboot
3. type non-ascii characters
  
Actual results:
wrong characters displayed and line-editing of the terminal mangled

Expected results:
characters that were typed are displayed

Additional info:
Maybe this is not a systemd issue, because when I run 

setfont latarcyrheb-sun16

nothing changes and the font is still wrong. On F17 this works as expected.

Comment 1 Vratislav Podzimek 2013-01-07 11:00:00 UTC

Maybe this is a completely different problem, please see bug #889710

Comment 2 Lennart Poettering 2013-01-13 22:48:35 UTC

which characters are this, specifically?

Comment 3 Vratislav Podzimek 2013-01-14 11:23:09 UTC

It seems to be fixed now (with the same version of systemd). I don't know what the reason was, but this bug can be closed.

Comment 4 Lennart Poettering 2013-01-14 17:47:59 UTC

OK, closing.