Re: mysterious change in X authorization behavior

2005-11-01 Thread s. keeling
Marty <[EMAIL PROTECTED]>: > On one of my Sarge systems, if X access control is enabled, i.e. > "xhost" yields the following output: > > access control enabled, only authorized clients can connect Short answer: don't use xhost. You can replace it with the much better xauth: # ---

Re: Update on mysterious change in X authorization behavior

2005-11-01 Thread s. keeling
Marty <[EMAIL PROTECTED]>: > Marty wrote: > > On one of my Sarge systems, if X access control is enabled, i.e. > > "xhost" yields the following output: > > > > access control enabled, only authorized clients can connect > > Acting on a hunch, I replaced gdm with kdm and the problem seems to

Update on mysterious change in X authorization behavior

2005-10-31 Thread Marty
Marty wrote: On one of my Sarge systems, if X access control is enabled, i.e. "xhost" yields the following output: access control enabled, only authorized clients can connect then if I su to root, X apps now start normally, as if I had previously executed "xhost +". All my sarge systems ar

mysterious change in X authorization behavior

2005-10-31 Thread Marty
On one of my Sarge systems, if X access control is enabled, i.e. "xhost" yields the following output: access control enabled, only authorized clients can connect then if I su to root, X apps now start normally, as if I had previously executed "xhost +". All my sarge systems are up to date, b

Re: Xvfb and X authorization

2004-11-18 Thread Matt Price
Matt Price wrote: hi, I have a script that opens Openoffice in an X session managed by Xvfb. I initiate the X session with: Xvfb :86 -screen scrn 800x600x32 & This used to work fine. But sometime in the recent past, presumably since an unobserved update or something, I get this error when tryin

Xvfb and X authorization

2004-11-16 Thread Matt Price
hi, I have a script that opens Openoffice in an X session managed by Xvfb. I initiate the X session with: Xvfb :86 -screen scrn 800x600x32 & This used to work fine. But sometime in the recent past, presumably since an unobserved update or something, I get this error when trying to connect

Re: X authorization

1996-09-17 Thread Susan G. Kleinmann
Hi Derek -- You asked: > How is the X authorization set up in Debian? Lukas Nellen provided a nice answer to this a while ago. I'm just repeating it here: > > I am running xdm and I discovered that only the login user can > start an X window. There are 2 situations when I ca

Re: X authorization

1996-09-16 Thread Boris Beletsky
-BEGIN PGP SIGNED MESSAGE- On Sat, 14 Sep 1996 [EMAIL PROTECTED] wrote: dkklee>(1) when I try to start a window after 'su' to root. I discovered this dkklee>can be fixed if I do 'xhost +mymachinename'. How to this automatically? dkklee>A line in Xaccess or some /etc/X11/X???.hos

Re: X authorization

1996-09-15 Thread Stephen Early
In article <[EMAIL PROTECTED]> you write: >How is the X authorization set up in Debian? > >I am running xdm and I discovered that only the login user can >start an X window. The 'MIT-MAGIC-COOKIE' authentication method is being used; only X clients with access to

Re: X authorization

1996-09-15 Thread Kazuhiro Sasayama
> "dkklee" == dkklee <[EMAIL PROTECTED]> writes: dkklee> (1) when I try to start a window after 'su' to root. I dkklee> discovered this can be fixed if I do 'xhost dkklee> +mymachinename'. How to this automatically? A line in dkklee> Xaccess or some /etc/X11/X???.hosts file?

X authorization

1996-09-14 Thread dkklee
How is the X authorization set up in Debian? I am running xdm and I discovered that only the login user can start an X window. There are 2 situations when I cannot start a X window: (1) when I try to start a window after 'su' to root. I discovered this can be fixed if I