Bug 163558

Summary:	/etc/X11/prefdm splits xdm/gdm/etc. params with embedded space
Product:	Red Hat Enterprise Linux 4	Reporter:	Bill Nottingham <notting>
Component:	initscripts	Assignee:	Bill Nottingham <notting>
Status:	CLOSED ERRATA	QA Contact:	Brock Organ <borgan>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.0	CC:	rvokal
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	RHBA-2005-607	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-10-05 15:47:57 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:
Bug Depends On:	154312
Bug Blocks:	156322

Description Bill Nottingham 2005-07-18 21:01:47 UTC

+++ This bug was initially created as a clone of Bug #154312 +++

Description of problem:
/etc/X11/prefdm, a shell script and a part of initscripts, used to launch
X11 display manager from /etc/inittab, doesn't pass parameters containing
spaces to *dm correctly - it splits such parameters using whitespace as
a delimiter. This behavious breaks things like:

   /etc/X11/prefdm -server ":0 local /usr/X11R6/bin/X ...

Version-Release number of selected component (if applicable):
7.93.7-1 (i.e., current FC3 update)

How reproducible:
Run the following by hand, with no xserver running. Observe parameters passed
to xdm (gdm, kdm etc.) or, for example, xdm output.

Steps to Reproduce:
1. /etc/X11/prefdm -server ":0 local /usr/X11R6/bin/X"
2. tail /var/log/xdm-errors

Actual results:
"xdm error (pid 9491): Missing display type for :0"
Xserver doesn't started

Expected results:
Xserver stdout and/or stderr output, Xserver running

OTOH it would be nice if prefdm sends *dm output to a different than /dev/null
location. These is a bug report about that open for few years, I think.

Comment 3 Bill Nottingham 2005-07-21 17:44:04 UTC

Fixed in 7.93.14.EL-1.

Comment 4 Red Hat Bugzilla 2005-10-05 15:47:58 UTC

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2005-607.html