Hide Forgot
Description of problem: When newt is invoked from a start-up script that runs prior to user login (e.g. firstboot) it ignores ENTER key. Other keys - LEFT, RIGHT, SPACE and F12 - are processed just fine. But ENTER key is ignored in all dialogs. The problem exists both in python bindings and in whiptail. Version-Release number of selected component (if applicable): newt-0.52.11 How reproducible: always Steps to Reproduce: 1. create a simple /etc/init.d startup script that uses whiptail, e.g.: #!/bin/bash # # chkconfig: 3 99 95 # case "$1" in start) /usr/bin/whiptail --msgbox "Some text" 8 50 ;; stop) ;; esac exit 0 2. install new script into chkconfig chkconfig --add test chkconfig test on 3. Run this script from a regular shell and verify that ENTER key works correctly 4. Reboot the machine (at init level 3). The script will run automatically in the end of the reboot. Verify that ENTER key doesn't work. Actual results: ENTER key doesn't work. Expected results: ENTER key should work. Additional info:
This looks more like a plymouth or systemd issue.
You were absolutely right - adding rd_NO_PLYMOUTH to kernel parameters solved the problem.
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. If you would like it considered as an exception in the current release, please ask your support representative.
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available. The official life cycle policy can be reviewed here: http://redhat.com/rhel/lifecycle This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL: https://access.redhat.com/