Hide Forgot
+++ This bug was initially created as a clone of Bug #431556 +++ +++ This bug was initially created as a clone of Bug #172059 +++ Description of problem: Running "BASH_ENV=~/.bashrc TERM=linux /bin/unicode_start" on physical console will not return. Version-Release number of selected component (if applicable): kbd-1.12-21.el5 How reproducible: 100% Steps to Reproduce: 1. Switch to a real virtual terminal (i.e. not ssh or virsh console). 2. Run "TERM=linux BASH_ENV=~/.bashrc /bin/unicode_start" Actual Results: Command never returns. Expected Results: Command should return. Additional info: The problem is that setting BASH_ENV=~/.bashrc runs /etc/profile, which sources /etc/profile.d/lang.sh. If TERM=linux, lang.sh runs /bin/unicode_start sending the whole process into an infinite loop. The resolution is to change the first line of /etc/unicode_start from "#!/bin/bash" to "#!/bin/sh". This seems to be the way upstream (Fedora 12, at least) is written.
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux release for currently deployed products. This request is not yet committed for inclusion in a release.
For reproducer take a look at #c0 new version: $ TERM=linux BASH_ENV=~/.bashrc /bin/unicode_start &>/dev/null && echo $? $ 0
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: No Documentation needed
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-0015.html