Red Hat Bugzilla – Bug 116050
gdm prevents xclock to run with explicit -display parameter
Last modified: 2007-11-30 17:10:36 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6)
Description of problem:
I am using an application that has a bit of an unusual design. It
systematically fails to start with the following error, no matter what
-display parameter I give it. Besides, I've run this app on all
versions of RedHat since 7.0 and I never had to specify the -display
Error: Can't open display: obiwan:0.0
I eventually found I could reproduce this exact same symptom with
xclock and other standard X programs.
This may be a xdm/gdm configuration problem of some sort, in which
case I apologize for disturbing you with this and also thank you for
telling me how to resolve this. I've poked around without success so far.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. init 5
2. xclock -display localhost:0
Actual Results: xclock never opens. Shell returns message:
"Error: Can't open display: localhost:0"
Expected Results: I see no reason why specifying the machine name as
the display parameter wouldn't work. If it wasn't of this limitation,
my app (and any other weird app) would run fine.
Happens on upgraded RH9 -> FC1.
Happens on fresh FC1 install.
Haven't played with my X config besides the usual XF86Config stuff. My
login manager is the default one (gdm).
Try the same xclock command in runlevel 3. It will open without a problem.
Just a quick note to let you know the culprit is really gdm.
Just a quick note for letting you know I have confirmed gdm is the
culprit. No problem occurs when opening a session with xdm or kdm. As
a matter of fact, the exact runlevel does not matter.
I have yet to find the exact root of the problem. Since Fedora's
default login manager, I would still like to adress this issue. Asking
all my users to change their login manager isn't an option for me.
Found the solution with the help of email@example.com list. All I add to
do was to edit gdm.conf and add this line:
Case closed. You may dispose of this issue.