Robert Echlin [EMAIL PROTECTED] writes:
# DISPLAY=:0.0 XAUTHORITY=/var/gdm/:0.Xauth vncconfig -list
I am not running VNC on :0, as confirmed by variations of your command:
Sorry if I misunderstood the question.
(sudo did not work - it assumed that DISPLAY was an executable)
For what it's
Adding on Robert's suggestion,
This seems to be required for the shell to start stuff in the :0.0
display.
At least, when I changed XAUTHORITY to point at ~/.Xauthority, I
found I
could then run stuff in :1, but not in :0.
Presumably your setup is different, but normally Fedora 3 running
-Original Message-
From: Dave Love [mailto:[EMAIL PROTECTED]
Sent: Monday, April 18, 2005 1:41 PM
To: Robert Echlin
Cc: vnc-list@realvnc.com
Subject: Re: X authentication
Robert Echlin [EMAIL PROTECTED] writes:
every copy of bash that I run generates a different XAUTHORITY
be the default
value anyway.
Vamsi
Robert Echlin [EMAIL PROTECTED] 04/19/05 7:06 PM
-Original Message-
From: Dave Love [mailto:[EMAIL PROTECTED]
Sent: Monday, April 18, 2005 1:41 PM
To: Robert Echlin
Cc: vnc-list@realvnc.com
Subject: Re: X authentication
Robert Echlin [EMAIL PROTECTED
Hi,
I am having what looks like an X authentication error.
When I run a program from my desktop, telling it to run in :1, where my
vncserver is running, I get error messages. I can see the vnc server
with a vncviewer. The vnccconfig and xterms are running, and the usual
grey background
Robert Echlin [EMAIL PROTECTED] writes:
every copy of bash that I run generates a different XAUTHORITY
environment variable pointing to a different file like ~/.xauth9txPiW
- the part of the name after .xauth appears to be a random string
I don't know where that's coming from...
This seems
