Yast fonts horrible on cli server mode.

manwichmakesameal · November 19, 2011, 5:41pm

Ok, I decided to try out OpenSuSE on a vm. Problem is, it’s only cli (which I chose and is going to stay that way) and yast looks horrible. Here’s what I get:
Bad Fonts

Are there other packages I need to install? I installed Yast2-ncurses…to no avail. I’ve searched for answers to this, but the only thing I get is something from 12-2009 regarding the same issue with an upgrade from 11.1 to 11.2. Is this not fixed yet?

martin_helm · November 19, 2011, 6:14pm

Am 19.11.2011 17:46, schrieb manwichmakesameal:
>
> Ok, I decided to try out OpenSuSE on a vm. Problem is, it’s only cli
> (which I chose and is going to stay that way) and yast looks horrible.
> Here’s what I get:
> ‘Bad Fonts’ (http://imageshack.us/photo/my-images/254/yastbadfonts.png)
>
> Are there other packages I need to install? I installed
> Yast2-ncurses…to no avail. I’ve searched for answers to this, but the
> only thing I get is something from 12-2009 regarding the same issue with
> an upgrade from 11.1 to 11.2. Is this not fixed yet?
>
>
This seems to be a wrong mapping of the characters not a bad font. You
can change console font and mapping with the command “setfont”, btw waht
output does the command “locale” give you?

manwichmakesameal · November 19, 2011, 6:30pm

locale gives:


LANG=POSIX
LC_CTYPE=en_US.UTF-8
LC_NUMERIC="POSIX"
LC_TIME="POSIX"
LC_COLLATE="POSIX"
LC_MONETARY="POSIX"
LC_MESSAGES="POSIX"
LC_PAPER="POSIX"
LC_NAME="POSIX"
LC_ADDRESS="POSIX"
LC_TELEPHONE="POSIX"
LC_MEASUREMENT="POSIX"
LC_IDENTIFICATION="POSIX"
LC_ALL=

setfont didn’t fix it, but it did seem to “sharpen” the fonts.

martin_helm · November 19, 2011, 6:45pm

Am 19.11.2011 18:36, schrieb manwichmakesameal:
>
> setfont didn’t fix it, but it did seem to “sharpen” the fonts.
>
Your locale looks good, with setfont I did not mean to just type the
command but to inspect the man page. The -m option gives you the
possibility to play with unicode mappings until you have it right.
You may try something like setfont -m 8859-1 (I do not have your problem
it is correct on my machine so you have to try several options).

hcvv · November 20, 2011, 10:27am

To me it looks also if somewhere your UTF-8 characters are interpreted as something else. Could it be the terminal simulator? What software is the terminal simulator?

nrickert · November 20, 2011, 3:00pm

Yes, I got that yesterday.

I just completed an install.
Booting gave me the kdm login screen.
I hit CTL-ALT-F1 to get a virtual terminal.
I logged into the virtual terminal as root.
I ran “yast”.

My plan had been to set the system hostname and domain to what I want, before a GUI login. Scrap that. It was a struggle just to work out how to get out of Yast with that funky screen.

hcvv · November 20, 2011, 3:02pm

When you have that immediatly after install and in fact nothing else, that looks like a bug to me.

And, like Martin Heml, think it is not a font, but an encoding problem.

martin_helm · November 20, 2011, 3:38pm

Am 20.11.2011 10:36, schrieb hcvv:
>
> To me it looks also if somewhere your UTF-8 characters are interpreted
> as something else. Could it be the terminal simulator? What software is
> the terminal simulator?
>
There is no terminal emulator involved it is the text console.

hcvv · November 20, 2011, 3:59pm

Yes, that is clear to me now. But I still think somewhere the UTF-8 encoding is interpreted as if it were Latin-1 or even ASCII.

robin_listas · November 20, 2011, 4:18pm

On 2011-11-20 15:06, hcvv wrote:
>
> When you have that immediatly after install and in fact nothing else,
> that looks like a bug to me.

It works alright for me. But mine is an RC2 updated.

–
Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

martin_helm · November 20, 2011, 4:38pm

Am 20.11.2011 16:18, schrieb Carlos E. R.:
> On 2011-11-20 15:06, hcvv wrote:
>>
>> When you have that immediatly after install and in fact nothing else,
>> that looks like a bug to me.
>
> It works alright for me. But mine is an RC2 updated.
>
I started now the machine I installed yesterday (12.1 fresh install no
upgrade, was done from the KDE Live CD). And also there is no corruption
visible for the graphic characters when starting yast in a virtual
console (I have chosen first the first one [CTRL][ALT][F1] which has
framebuffer).
The second one [CTRL][ALT][F2] which has no framebuffer also shows yast
correct. I also tried logging in as root vs. login as user and calling
yast with sudo and su -c, in no case a corruption of the graphics
characters is shown.
I cannot find any combination which shows the corruption.

nrickert · November 20, 2011, 5:52pm

Interesting.

I booted up the same system today, use CTL-ALT-F1, logged in as root, started yast, and everything was fine.

Something has changed between the initial try and now. Perhaps the system comes with yast incompletely configured, and it configures itself later, but not in time for that first attempt.

Addendum: The situation leading to the funky screen yesterday - the “kexec” reboot during install had failed (an expected fail). I rebooted. Then the final stages of the installation completed. That’s when the login screen appeared, and when I went to a virtual console to use yast and got a mess. So it was before any reboot on the fully installed system. It’s possible that something done in those final installation stages don’t get picked up until the next full reboot.

robin_listas · November 20, 2011, 9:08pm

On 2011-11-20 17:56, nrickert wrote:

> Something has changed between the initial try and now. Perhaps the
> system comes with yast incompletely configured, and it configures itself
> later, but not in time for that first attempt.

The first attempt after install is different, yes.

I don’t know if it is still done via kexec, there were doubts.

–
Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

hcvv · November 20, 2011, 10:57pm

Thus we like to hear from the OP @manwhichmakesameal if it persists after a reboot.