Bugzilla – Bug 103007
yast2 sw_single does not work on console
Last modified: 2005-08-12 15:24:06 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.
Created attachment 45310 [details] yast sw_single screenshot on console
*** Bug 103018 has been marked as a duplicate of this bug. ***
I'll test it
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.
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.
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
Base system - please, have a look at it Thanks
Wrong usage! There is NO such beast like "POSIX.UTF-8"
Fixed for Beta2
LANG="" is a problematic value, see #102328. Maybe better unset LANG instead of LANG="" ?
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 :)
If it is only for the next check than it is probably OK.