unable to open X window on machine

2002-10-09 Thread David Cureton

Hi all,
Firstly I must confess, I have not spent much time trying to sort this one 
out. However, I have the latest stable Debian installed in my machine running 
KDE desktop.  However I find that I am unable to cause other machines on the 
network to open an X window on my machine by setting the DISPLAY variable on 
the other remote machine before invoking xeyes, xclock or any other X 
application.
 
What I have done/tried:

1) Have run 'xhost + ' on X server to disable access control.

2) Can ssh to/from X server machine, network connectivity OK

3) Checked the iptables rules.  (Default policy on all is ACCEPT. no other 
rules except the defaults)

4) route output looks ok with only two entries. The local network entry and 
the default route entry which appear ok. (step 2 confirms this)

5) if DISPLAY is set to the machines own IP address 192.168.150.150:0.0, 
calling an X application fails due to 'Error: Can't open display: 
192.168.150.150:0.'. X applications only work when display is set to :0.0 on 
the local machine.

Is there some other type of access control I  am overlooking??

Cheers
David

 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: x-session-manager overrides x-window-manager

2002-09-02 Thread matthew arnison

I think Hubert's idea below is a good one. Although it still seems a bit
of an odd thing to have to hack like this in order to give a window
manager priority over a session manager. Some of us just don't want to use
kde or gnome as window managers, even if we have them installed.

Anyway, a slight correction. I used the filename:

/etc/X11/Xsession.d/51local_force-x-window-manager

and it contains:

REALSTARTUP=x-window-manager

(not REALSETUP as below).

Time will tell whether it will withstand upgrades. I think it should be
fine. *.d folders are great.

Cheers,
Matthew.

Hubert Chan <[EMAIL PROTECTED]> wrote:
> Haven't tried this but... you could add a
> /etc/X11/Xsession.d/51force-x-window-manager which contains the line

> REALSETUP=x-window-manager

> That should force it to use x-window-manager instead of
> x-session-manager, and be persistent over all upgrades.





-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: unable to open X window on machine

2002-10-09 Thread Tom Cook

On  0, David Cureton <[EMAIL PROTECTED]> wrote:
> Hi all,
>   Firstly I must confess, I have not spent much time trying to sort this o
> ne 
> out. However, I have the latest stable Debian installed in my machine running 
> KDE desktop.  However I find that I am unable to cause other machines on the 
> network to open an X window on my machine by setting the DISPLAY variable on 
> the other remote machine before invoking xeyes, xclock or any other X 
> application.
>  
> What I have done/tried:
> 
> 1) Have run 'xhost + ' on X server to disable access control.
> 
> 2) Can ssh to/from X server machine, network connectivity OK
> 
> 3) Checked the iptables rules.  (Default policy on all is ACCEPT. no other 
> rules except the defaults)
> 
> 4) route output looks ok with only two entries. The local network entry and 
> the default route entry which appear ok. (step 2 confirms this)
> 
> 5) if DISPLAY is set to the machines own IP address 192.168.150.150:0.0, 
> calling an X application fails due to 'Error: Can't open display: 
> 192.168.150.150:0.'. X applications only work when display is set to :0.0 on 
> the local machine.
> 
> Is there some other type of access control I  am overlooking??

Not really.  The default is to have '-nolisten tcp' in
/usr/X11R6/lib/X11/xinit/xserverrc (I think this is where it is - I
changed it long ago).  If you use a display manager then that probably
is also set to use '-nolisten tcp' by default - I think that is done
in /etc/X11/xdm/Xservers.  Remove the '-nolisten tcp' from these
locations, use xhost to allow connections from the other machines, and
you should be fine.

Tom
-- 
Tom Cook
Information Technology Services, The University of Adelaide

"Beware of computer programmers that carry screwdrivers."
- Leonard Brandwein

Get my GPG public key: 
https://pinky.its.adelaide.edu.au/~tkcook/tom.cook-at-adelaide.edu.au



msg06293/pgp0.pgp
Description: PGP signature


Re: unable to open X window on machine

2002-10-10 Thread Shyamal Prasad

"David" == David Cureton <[EMAIL PROTECTED]> writes:

David> Is there some other type of access control I am
David> overlooking??

Debian starts the X server with the '-nolisten tcp' option by
default. You need to find where the X server is starting from and
change the command option.

In my case (I use gdm to login) the file is /etc/gdm/gdm.conf, and the
command is near the end of the file. In reality, I've stayed with the
nolisten option. I use ssh these days instead of setting my DISPLAY by
hand.

Cheers!
Shyamal


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Some keys do not work on X-Window 4.2

2002-10-24 Thread Luis Arocha
Hi,

After upgrading X-Window to version 4.2 the keys \ | @ # ~ ¬ ceased to
work. (I'm writing this on text console)

In my (spanish) keyboard this keys can be obtained pressing key [Alt Gr]
plus keys º 1 2 3 4 6 on the top left.

When I use AltGr+1 in a text console somthing like (Arg ) appears.

May somebody give me a hint? What program/configuration file/guide must
I look? I've tryed many but... finally I had to cry for help.

TIA
-- 
 _ o__o__  o__  O_   OO   Luis Arocha
   o/,>/  ,>/ ,//  ,/\ ,/|   Canary Islands,Spain
__()_\()__()_()_\(()_\()__()_\()___()_<()__()_<()_http://gix.berlios.de
Don't hit the keys so hard, it hurts.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]