Bug 103007

Summary:	yast2 sw_single does not work on console
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Andreas Klein <asklein>
Component:	Basesystem	Assignee:	Lukas Ocilka <locilka>
Status:	RESOLVED FIXED	QA Contact:	Klaus Kämpf <kkaempf>
Severity:	Normal
Priority:	P5 - None	CC:	locilka, roger, vetter
Version:	Beta 1
Target Milestone:	---
Hardware:	Other
OS:	All
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	yast sw_single screenshot on console

Description Andreas Klein 2005-08-09 12:34:15 UTC

- Switch to console with Ctrl+Alt+F2
- start yast2 sw_single
- press alt+f alt+s for search
- there are packages visible "through" the search mask. (See screenshot).
- You can't type into the fields. I even didn't manage to quit yast.

- yast sw_single works fine in a xterm, the problem only exists on a console.

Comment 1 Andreas Klein 2005-08-09 12:36:08 UTC

Created attachment 45310 [details]
yast sw_single screenshot on console

Comment 2 Stanislav Visnovsky 2005-08-09 13:19:59 UTC

*** Bug 103018 has been marked as a duplicate of this bug. ***

Comment 3 Lukas Ocilka 2005-08-09 21:22:35 UTC

I'll test it

Comment 4 Lukas Ocilka 2005-08-10 10:02:23 UTC

It seems that all consoles (F1 - F6) presents broken YaST.
There are some unprintable characters marked "?" in (almost?) every YaST module
(dialog).
Might be font-realted problem.

Comment 5 Lukas Ocilka 2005-08-10 12:19:26 UTC

The problem is somewhere in the /sbin/yast2 script setting ENV variables:
     LANG and LC_CTYPE to "POSIX.UTF-8"

It works well when they are set to "en_US.UTF-8", for instance.
But it doesn't help to set it before running the `yast2` script.

Comment 6 Lukas Ocilka 2005-08-10 12:58:11 UTC

OK, I've found that...
The difference between SL 9.3 and SL 10.0 is in the $LANG variable
LANG in console was "" (empty) on 9.3 but now it is set to "POSIX"

Unset it to get working UI...
`LANG="" yast2 sw_single` works well
`LANG="es_ES" yast2 sw_single` works well too

How is the language-adjusting handled?
starting /sbin/yast2
importing functions from /usr/lib/YaST2/bin/yast2-funcs
calling function set_lang_from_sysconfig from /usr/lib/YaST2/bin/yast2-funcs

setting ENV variables to POSIX because LANG is not empty...

It is a base-system bug

Comment 7 Lukas Ocilka 2005-08-10 13:00:13 UTC

Base system - please, have a look at it
Thanks

Comment 8 Dr. Werner Fink 2005-08-10 13:16:11 UTC

Wrong usage!  There is NO such beast like "POSIX.UTF-8"

Comment 12 Lukas Ocilka 2005-08-12 11:14:04 UTC

Fixed for Beta2

Comment 13 Mike Fabian 2005-08-12 12:27:30 UTC

LANG="" is a problematic value, see #102328.

Maybe better

   unset LANG

instead of

   LANG=""

?

Comment 14 Lukas Ocilka 2005-08-12 12:34:01 UTC

Mike, thanks a lot, but rather not. That could change more than only one thing
or wouldn't do anything.

YaST-starting-script allways sets the LANG and LC_CTYPE

My fix only sets "POSIX" to "" for the next checking (and deciding whether to
use the RC_LANG value from sysconfig or not).
I rather don't want to change more than is needed - that's the YaST backward
compatibility :)

Comment 15 Mike Fabian 2005-08-12 15:24:06 UTC

If it is only for the next check than it is probably OK.