RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1533050 - xinit script unbound variable
Summary: xinit script unbound variable
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: imsettings
Version: 7.5
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: 7.7
Assignee: Akira TAGOH
QA Contact: QE Internationalization Bugs
URL:
Whiteboard:
Depends On: 1532647 1533040
Blocks: 1533079 1549949 1640542
TreeView+ depends on / blocked
 
Reported: 2018-01-10 11:07 UTC by Tomas Pelka
Modified: 2019-08-06 13:00 UTC (History)
8 users (show)

Fixed In Version: imsettings-1.6.3-11.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1533040
: 1533079 (view as bug list)
Environment:
Last Closed: 2019-08-06 13:00:32 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:2164 0 None None None 2019-08-06 13:00:36 UTC

Description Tomas Pelka 2018-01-10 11:07:04 UTC
Description of problem:
Adding set -u to a user's .profile does not allow a them to log in on the graphical console.

Version-Release number of selected component (if applicable):
dbus-1.10.24-3.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Add 'set -u' in user's $HOME/.profile
2. Login as same user in runlevel 3
3. Execute startx.

Actual results:
/etc/X11/xinit/xinitrc.d/10-qt5-check-opengl2.sh: line:41: IMSETTINGS_DISABLE_USER_XINPUTRC: unbound variable

Expected results:
no error

Additional info:

I think the same issue is on lines 87,90 and 94

Comment 1 Tomas Pelka 2018-01-10 11:08:17 UTC
I beleieve something like

[ -z ${IMSETTINGS_DISABLE_USER_XINPUTRC-} ] ....

could do the trick

Comment 2 Michal Odehnal 2018-04-16 11:58:59 UTC
Following files are also having the issue Tom has mentioned:
/etc/X11/xinit/xinitrc.d/50-xinput.sh: line <number: variable_name>: unbound variable
/usr/libexec/imsettings-functions: line <number: variable_name>: unbound variable
/etc/X11/xinit/xinitrc-common: line <number: variable_name>: unbound variable

Once the workaround is applied to all parts in listed files. Graphical session is successfully loaded.

Comment 3 Tomas Pelka 2018-04-16 12:09:47 UTC
We would need another bz for /etc/X11/xinit/xinitrc-common against xorg-x11-xinit.

Michale would you please do it?
Thanks
-Tom

Comment 4 Michal Odehnal 2018-04-16 12:35:23 UTC
Done bz<1567918>

Comment 5 Jens Petersen 2018-04-18 02:44:11 UTC
bug 1567918

Comment 6 Akira TAGOH 2018-06-21 06:36:33 UTC
fixed in imsettings-1.6.3-10.el7

Comment 19 errata-xmlrpc 2019-08-06 13:00:32 UTC
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.

https://access.redhat.com/errata/RHBA-2019:2164


Note You need to log in before you can comment on or make changes to this bug.