Bug 86125

Summary: setsysfont does not load console map
Product: [Retired] Red Hat Linux Reporter: Péter, Soós <sp>
Component: initscriptsAssignee: Bill Nottingham <notting>
Status: CLOSED RAWHIDE QA Contact: Brock Organ <borgan>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.0CC: rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-03-14 16:06:00 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Péter, Soós 2003-03-14 15:40:45 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; hu-HU; rv:1.2) Gecko/20021206

Description of problem:
setsysfont (useing setfont) does not load the console map ($SYSFONTACM in
/etc/sysconfig/i18n).

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.define a console map in /etc/sysconfig/i18n (SYSFONTACM)
2.run setsysfont utility
3.
    

Actual Results:  console map setting is discarded since there is no consolechars
utility

Expected Results:  console map is loaded

Additional info:
Here is my patch:

<-- cut here -->
--- setsysfont.old      2003-03-14 14:08:52.000000000 +0100
+++ setsysfont  2003-03-14 16:27:01.000000000 +0100
@@ -24,12 +24,15 @@
     consolechars -f $ARGS
   fi
 elif [ -x /bin/setfont ]; then
-  if [ -n "$SYSFONT" -a -n "$UNIMAP" ]; then
-    /bin/setfont $SYSFONT -u $UNIMAP
-  elif [ -n "$SYSFONT" ]; then
-    /bin/setfont $SYSFONT
-#  else
-#    /bin/setfont
+  if [ -n "$SYSFONT" ]; then
+    ARGS=$SYSFONT
+    if [ -n "$UNIMAP" ]; then
+       ARGS="$ARGS -u $UNIMAP"
+    fi
+    if [ -n "$SYSFONTACM" ]; then
+       ARGS="$ARGS -m $SYSFONTACM"
+    fi
+    /bin/setfont $ARGS
   fi
 else
   echo $"can't set font"
<-- cut here -->

Comment 1 Bill Nottingham 2003-03-14 16:06:00 UTC
This was fixed in the Phoebe beta.