X-windows
12 August 2005
Summary
- KDM sets the wrong dpi (75) for Clitunno -- you can change it in the file /etc/kde3/kdm/kdmrc. Add "-dpi 100"
to the paramter "ServerArgsLocal=-nolisten tcp -dpi 100"
- Restart X11 (untested): CTRL+ALT+BACKSPACE
- Test resolution: "xdpyinfo | grep resolution"
- Consider implementing Terminal
Server
- Consider making use of Xdmx -- unified desktop from multiple X servers
Guides and resources
See also the ATS Beowolf
cluster, which can be accessed with X-Windows.
Commands
- glxinfo
- just reconfigure x11-common (reset permissions)
- xwininfo -- show the geometry and properties of a particular window
- xauth list -- show the contents of the .Xauthority file
- xset -q -- show variables available to the xset command? (keyboard, pointer, screen, fonts, etc.
- xrandr -d :0 -q
- xdpyinfo -display $HOST:0.0 -- show information about an x-windows server
- XFree86 -scanpci -- show the PCI address
- xlsclients -- show clients connected to the x-windows server specified (works on localhost at least)
- xlsclients -display remote-machine:0
- xman, xedit, xlogo, xlsfonts
- startx -- :1 -dpi 100 (start an x-session in a second window)
- test $DISPLAY && dcop kdesktop default logout -- shut down x-windows from the cli
Compiz and the 3D desktop
Configuration tools (none of these are any good at defining dual monitor setups)
- man xorg.conf
- xorgcfg -- configuration tool, can be used to tweak existing configuration
- Xorg -configure -- let x-windows create a configuration on its own
- xorgconfig -- text-based tool that works really well
- videogen -- X11 tool, generates modelines (needs parameters)
- xdpyinfo -- show characteristics of current display
- ddcprobe and xresprobe -- probes monitor properties and resolution (mainly for auto-config)
- xvidtune -- switch between screen sizes (hide desktop to
keep icons from shifting)
- dpkg-reconfigure xserver-xfree86 -- the Debian way
- dexconf -- beware, automatically overwrites /etc/X11/XF86Config-4!
- xresprobe (debian package)
- fglrxconfig -- for ATI's drivers
- /etc/vga/libvga.config -- configure graphics driver outside of X11
- /etc/X11/default-display-manager -- define "console" or "/usr/X11R6/bin/xdm"
- xplsprinters, xprehashprinterlist (xprint utilities in Xorg)
Configuring x-windows
For twinview, use the nvidia device driver, but use the nv driver if
you need to suspend; it may support xinerama. The fbdev driver supports
multihead, and likely xinerama, but I haven't tested it. The vesa driver
is likely less capable, but could be worth a spin. You need a new
file for graphics outside of x-windows -- it may be that you can use the
vesa driver without having to load a framebuffer.
Running remote applications through x-windows
- News in Debian
- Remote X-windows works like a dream through ssh on individual
applications, provided
- X11Forwarding yes in /etc/ssh/sshd_config on the remote box AND
- ForwardX11yes in /etc/ssh/ssh_config on the local box OR
- ssh is started with ssh -X <host> (see Procedure below)
- Xvideo doesn't work remotely, so with applications that can use
it or something else, pick something else for remote viewing.
kino works fine -- but a bit slow!
- It doesn't matter if X starts up with the -nolisten tcp option
-- in fact that's even a good idea, for security (details
below)
- The graphics quality is much higher than VNC, the response time
is as fast as the local machine
- You can even play video remotely, at least the compressed kind
(though see below)
- You can do file operations straight across systems -- including
between Windows disks and Linux disks -- as if it were a single
computer
- You can't get the kde desktop for some reason -- I don't know
what the conflict is
- There's some complicated permissions scheme that I haven't
figured out (magic cookies and beyond)
- Cygwin will let you run X-windows under Microsoft Windows; see separate
page
- For the Radeon 8500 driver, see below
- I'm considering setting up terminal servers, but it looks
like a fair amount of work
- In Debian, the default display manager is defined in
/etc/X11/default-display-manager -- it's currently set to gdm.
However, this value is overridden by ~/.xsession, which is set to
startkde (and could use icewm).
- xset -q -- get information from the x windows server
- To configure x-windows, try kxconfig (from the kdeadmin package?)
- X-windows through ssh currently works fine, but according to
this restrictions: you must be directly logged in as the current user -- no
su's are permitted
- you can ssh directly into another user's account and use x-windows from there
- In case it's not working, try this:
- xauth list (to see the magic cookies generated already)
- if you don't have a local one, create it on the local machine, in X11:
- xauth generate :0 . (that solved one level of the problem!)
- ssh -X trevi firefox (that was still needed)
- if ForwardX11yes in /etc/ssh/ssh_config on the local box, this is likely done automatically
- echo $DISPLAY (on remote computer)
- A method I tried successfully before:
- export DISPLAY=128.97.185.211:0.0
- xhost +128.97.185.211
This works beautifully, but may not be completely secure.
- It may be that you should try to get magic cookies to work --
though ssh may be all you need.
- xdpyinfo -display $HOST:0.0 to find out if you have display
rights
Debugging
$ cat /proc/meminfo > savefile
$ free
$ ps -eaf | grep X11R6 (get pid)
$ cat /proc/4588/stat (show pid)
$ cat /proc/4588/statm
$ cat /proc/4588/status
$ cat /proc/4588/maps
$ xlsclients
$ xrestop
$ xrestop -b | grep -A 14 appname
$ xrestop -b | grep -A 14 azureus
$ xrestop -b | grep -A 14 java
$ cat /var/lib/xfree86/X.roster
Components
To upgrade x-windows, start with
just upgrade xlibs
That pulls in lots of stuff.
Upgrade these packages:
libdps1 libggi-target-x libggi2 libice-dev libice6
libkrb53 libsm-dev libsm6 libx11-6 libx11-dev libxaw6 libxaw7
libxext-dev libxext6 libxft1 libxi-dev libxi6 libxmu-dev libxmu6
libxmuu-dev libxmuu1 libxp-dev libxpm-dev libxpm4 libxrandr-dev
libxrandr2 libxt-dev libxt6 libxtrap-dev libxtrap6 libxtst-dev libxtst6
libxv-dev libxv1 pm-dev render-dev xbase-clients x-dev xfonts-100dpi
xfonts-100dpi-transcoded xfonts-75dpi xfonts-75dpi-transcoded
xfonts-base xfonts-base-transcoded xfonts-scalable xfree86-common
xlibmesa-gl xlibmesa-gl-dev xlibmesa-glu xlibmesa-glu-dev xlibs
xlibs-data xlibs-dev xlibs-pic xlibs-static-dev xlibs-static-pic libxft2 libxft-dev libxrender1 libxrender-dev
xserver-common xserver-xfree86 xterm xutils
You might also need these:
- xlibmesa-dri xlibosmesa4 (for gubbio's radeon)
- discover mdetect read-edid libcairo1 (suggested packages)
- libglide3 (for a vodoo banshee -- currently not installed)
History
Application list
- These applications work perfectly through X-windows during an
ssh session:
- knode, konqueror, opera, pixie, xmms (no audio), yast2
- pretty much anything without special display requirements
works great
- Video applications that run into an undiagnosed problem
- aviplay: BadShmSeg -- doesn't crash, but is unable to
display the picture
- kino: set the display to gdk
- mplayer: set display to anything other than Xv (which
doesn't work remotely)
Shutting down X-windows
This weird command actually appears to have succeeded in
shutting down KDE and X-windows:
test $DISPLAY && dcop kdesktop default logout
And fast, with no protests! Treasure it...
Xwnc
A mix of Xvnc and XDarwin with improved protocol. It
draws nothing on your screen, every things is drawn into pixmaps.
Similarly as Xvnc, but with a different protocol, Xwnc can send these
pixmaps (and others information) to a "viewer". FvwmAmetista is such a
viewer, it uses OpenGL (via nucleo) for rendering the X desktop into a
window of a "regular" 3D accelerated X server.
New 2 November 2004, not tested.
XTV
The xtv package lets you see a remote desktop on your
local
display. It's not terribly useful -- among other things, the
local screen slows down when it's being piped simultaneously to another
computer.
You first need to allow the server (on your local machine) to
listen to incoming clients. On both machines, edit/etc/X11/xinit/xserverrc and remove "-nolisten tcp" and restart x-windows.
Second, you need to give permission to the clients, so issue on both sides,
xhost +remote-machine
To verify you have permissions right, issue
xlsclients -display remote-machine:0
You should get a list of apps running on that machine. If something
is wrong, error messages are found in /var/log/X*log. Then start xtv
(note -d, not -display):
xtv -d remote-machine:0
and the desktop should appear.
Run two or more instances of x-windows at the same time
first user # startx
second user # startx -- :1 -dpi 100
The first user's session will be in Ctrl-Alt-F7
The second user's session will be in Ctrl-Alt-F8 (note you may need to give the dpi of the x-server)
Now this is very cool. You can be logged in as several
users at once. It seems to run stable -- in fact I left it running and
forgot about it -- and when one instance has a problem, the other
doesn't. Quite neat.
2004-11-01 Update
Trying to get xtv to work. I ssh to spello from sigillo and issue
steen@spello:~$ xhost +128.97.185.211
128.97.185.211 being added to access control list
Back on sigillo,
steen@sigillo:~$ xlsclients -display spello:0.0
xlsclients: unable to open display "spello:0.0"
How do I give x-windows the right to display? The server may be the problem -- on sigillo:
pico /etc/X11/xinit/xserverrc
[remove -nolisten tcp]
restart x-windows
I tried that, then then:
ssh spello
xhost +128.97.185.211
xfig -display 128.97.185.211:0
No dice. Now, of course, if I just type xfig, it comes right up, so clearly I don't understand what I'm doing. And look at this:
steen@spello:~$ xlsclients
spello xfig
sigillo kicker
clitunno /usr/lib/mozilla/mozilla-bin -edit
I get exactly the same on sigillo:
steen@sigillo:~$ xlsclients
spello xfig
sigillo kicker
clitunno /usr/lib/mozilla/mozilla-bin -edit
2004-01-01 Update -- xrandr
On both sigillo and gubbio I installed the new x-windows 4.3.0-0pre1v5, which has the xrandr extension. Syntax:
xrandr -d :0 -q
tells you which functions are currently available for the :0 display, my current default:
SZ:
Pixels
Physical Refresh
*0 1600 x 2054 ( 406mm x 522mm ) *60
1 1600 x 1200 ( 406mm x 522mm ) 60
2 1280 x 854 ( 406mm x 522mm ) 53
Current rotation - normal
Current reflection - none
Rotations possible - normal
Reflections possible - none
Or you can call it screen 0. This shows you some interesting information, such as the fact you're using a 60Hz refresh rate.
None of the rotating or reflecting functions work, but the size
function lets you switch between the three modes defined in the x
config file (better do it with Fn+Ctrl+Alt+p or ;).
2003 Update
RADEON
Manufacturer's story
http://mirror.ati.com/support/faq/linux.html#ati
Instructions (save a local copy?)
http://www.ispep.cx/~x-empt/HOWTO/radeon_dri_howto.txt
XFree86 -- you already have these:
/lib/modules/2.4.19/kernel/drivers/char/drm/radeon.o
/usr/X11R6/lib/modules/dri/radeon_dri.so
/usr/X11R6/lib/modules/drivers/radeon_drv.o
but not this:
/lib/modules/2.4.19/kernel/drivers/video/radeonfb.o
I copied over the new 2.4.20 kernel from Spello to Gubbio and ran
a compile; you'll have to redo it to get the full
DRI support. I copied over the configuration from Sigillo (which is
much leaner), but added in framebuffer and
XFree86 (including DRI) support for the radeon and banshee cards. I
also switched the sound card to EMU10k1, the NIC
is the same (NatSemi), and IDE from ALi to Intel PIIXn and Promise
PDC 20269. This is now a Gubbio-specific
configuration, though it only differs in these minor ways from
Sigillo's. I may well have left out some modules.
TV Out support
http://www.stud.uni-hamburg.de/users/lennart/projects/atitvout/
GATOS -- http://gatos.sourceforge.net/
All-in-Wonder Radeon 8500DV (Radeon200)
Should work fine with 4.2.0 drivers. XvImage (YUV->RGB overlay
and scaling) should work fine. TV-in works in NTSC. It is expected
that PAL and SECAM will be easy to made working once there are people
willing to test and debug TV-in with these formats. Video capture
should work. 3d acceleration is not implemented as of this writing.
Firewire port (at least the one on the card itself) has been observed
to work in Linux. Wireless (RF) remote control should work.
DRI
Debian packages (currently for powerpc and i386) based on CVS
snapshots are available via
deb http://people.debian.org/~daenzer/dri-trunk/./
(for stable and testing) and
deb http://people.debian.org/~daenzer/dri-trunk-sid/./
(for sid). Note that there's no reason to use these; use the 4.3
packages -- see the Gubbio sources.list file.
Install the xserver-xfree86-dri-trunk and
xlibmesa-gl1-dri-trunk/xlibmesa3-dri-trunk packages and build the DRM
from the
drm-trunk-module-src package (most conveniently using
kernel-package).
Feedback about the packaging goes to Michel Dänzer
<daenzer@debian.org>
feedback about the drivers to dri-devel@lists.sf.net
Instructions: http://www.reades.com/radeon.html
Instructions: http://www.tldp.org/HOWTO/mini/XFree86-R200/using_gatos_drivers.html
Xinerama on the Radeon
http://www.linuxdig.com/news_page/1038239754.php
Radeon XFree86 DRI Linux HOWTO -- he recommends the GATOS driver,
which happen to have debs!
http://www.tldp.org/HOWTO/mini/XFree86-R200/index.html
BTTV Howto
http://www.tldp.org/HOWTO/mini/BTTV.html
XFREE86
videogen -- generates Modelines for XFree86 servers to make the
screen refresh rate as high as possible.
XF86Config: test out that you can use the default configuration
file for
an attached monitor!
Latest news on XFree86 for Debian -- see your sources.list
file.
Screenshots -- use KSnapshot under the KDE Graphics menu.
See also xwininfo
(http://www.tomomi256.freeserve.co.uk/linux/l_capture.html)
xengine -- benchmarking x-windows
glxgears -- benchmarking glx
Configuration tools
videogen -- X11 tool, generates modelines -- not terribly useful
xdpyinfo -- show characteristics of current display
xvidtune -- switch between screen sizes (avoid showing desktop to
keep the icons from moving around
xf86config -- text-based tool that works really well
xf86cfg -- X-based tool that is useful for checking an existing
configuration
dpkg-reconfigure xserver-xfree86 -- the Debian way
I ran xf86config on gubbio on 15 Jan 03 and it produced a good
result.
* after X starts, executing fbset -move [right][left] -step NN
from a terminal shifts the display right or
left by NN pixels. I tried this, and fbset was not found.
stop X11 (try this):
kill `/sbin/pidof xfs` or find the pid of xfs using ps and kill it
XF86Config: see
http://www.troubleshooters.com/linux/vidcard.htm#optimizingX
xinerama or DualView
1 Feb 2003
X11 -- xinerama using dual-channel display.
Check out the Debian-KDE mailing list at the end of January
(keyword xinerama) for instructions for how to set up kicker to span
two screens. This could be useful in the office -- you could define a
xinerama setup in x-config. It would let you keep two texts on the
screen at the same time, which is useful for instance for creating
web pages.
It turns out that nVidia's driver handles lots of this stuff --
more than you could imagine! I downloaded the guide (pdf). Wow! Amazing the
level of control you can have over the driver.
So in brief the answer is that yes, it looks like you'll be able
to use xinerama (or something like that that's even better and more
flexible) on Sigillo. You can also turn off the splash screen!
For XFree86 xinerama, you need a dual-head video card (or two
cards), see
http://www.linuxdocs.org/HOWTOs/Xinerama-HOWTO-9.html
Run XFree86 -scanpci to get PCI address (likely no different than
lspci); results in /var/log/XFree86.0.log:
(II) PCI: 01:00:0: chip 10de,0176 card 152d,2201 rev a3 class
03,00,00 hdr 00
(1:0:0) unknown card (0x152d/0x2201) using a NVidia GeForce4 420 Go
M32
The card on Sigillo is 0176, the GeForce4 420 Go M32; cf. nVidia's
documentation. 10de is nVidia.
For X11 help, see the discussion group at http://www.xfree86.org/mailman/listinfo/xfree86
All-in-Wonder Radeon 8500DV
- XFree86 4.3 has great support for Radeon graphics cards, and
specifically DRI drivers for the ATi Radeon 8500 video card: "The
Weather Channel is funding TG to develop an open source 3D DRI
driver for the ATI Radeon 8500 graphics card." These appeared
with 4.3 in February 2003.
- I installed XFree86 4.3 on Gubbio (using the Radeon 8500 128MB)
in early February 2003 and it's working great.
- I installed XFree86 4.3 on derekito (using SiS 300/305) on 9
February 2003 and it's also doing great on direct rendering.
- Mplayer parameters -- use -vo vesa:lvo:/dev/radeon_vid for TV
out? See
http://mplayerhq.hu/pipermail/mplayer-users/2001-December/008377.html
Installation history
November 2002 on spello
The following is a completely botched attempt to set up X-windows
with remote access. None of the steps listed are in fact necessary or
even useful -- all you need do is ssh -X <host>, or modify the
ssh config file (see details). Here is
nevertheless the story of this fruitless exercise, which may reveal
behaviors useful for other purposes (such as cases where your local
machine is not listed in the remote system's hosts.allowed file).
October 2002 on cyberspace
xvinfo
xdpyinfo -queryExtensions
X(7) ,
xwininfo(1) ,
xprop(1) ,
xrdb(1)
lspci lists:
00:0d.0 VGA compatible controller: nVidia Corporation Riva TnT
[NV04] (rev 04)
-- so it looks to me like the nv driver should be fine.
The problem is how to get the x-video extension:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/video-playback.html
xdpyinfo shows that XVIDEO is supported by the X-server
A list of common video interfaces:
X11: normal X11 output using shared memory.
XVideo: an extension to the X11 interface which supports video in
any X11
drawable.
SDL: the Simple Directmedia Layer.
DGA: the Direct Graphics Access.
SVGAlib: low level console graphics layer.
XFree86 4.X has an extension called XVideo (aka Xvideo, aka Xv,
aka xv) which allows video to be directly displayed in drawable
objects through a special acceleration. This extension provides very
good quality playback even on low-end machines (for example my PIII
400 Mhz laptop). Unfortunately, the list of cards in which this
feature is supported ``out of the box'' is currently:
3DFX Voodoo 3
Intel i810 and i815
some S3 chips (such as Savage/IX and Savage/MX)
If your card is not one of these, do not be disappointed yet.
XFree86 4.X adds new xv capabilities with each release [1]. To check
whether the extension is running, use xvinfo
A popular familiar graphics card with generally very good XFree86
performance, nVidia, has yet to release the specifications on their
XVideo support to the XFree86 team. It may be some time before
XFree86 fully
support XVideo for these cards.
So this means that it's the nVidia driver that's giving you
X-video on cyberspace.
This should be the driver, as installed from the tarball:
1195183 Oct 29 20:58
/lib/modules/2.4.19-ac4/kernel/drivers/video/NVdriver
I ran 3Ddiag and realized I had to add this to /etc/rc.config
SCRIPT_3D="switch2nvidia_glx"
I then did a quick make in the
/usr/src/p*/SO*/NVIDIA_GLX-1.0-3123
directory and got this:
Installing new drivers
install usr/lib/libGL.so.1.0.3123 //usr/lib
install usr/lib/libGLcore.so.1.0.3123 //usr/lib
install usr/X11R6/lib/modules/drivers/nvidia_drv.o
//usr/X11R6/lib/modules/drivers
install usr/X11R6/lib/modules/extensions/libglx.so.1.0.3123
//usr/X11R6/lib/modules/extensions
if [ `uname -m` != "ia64" ]; then \
install usr/X11R6/lib/libXvMCNVIDIA.a
//usr/X11R6/lib/libXvMCNVIDIA.a; \
install usr/X11R6/lib/libXvMCNVIDIA.so.1.0.3123
//usr/X11R6/lib/libXvMCNVIDIA.so.1.0.3123;
So it looks like the drivers might just be called nvidia and
glx...
This is what you need in /etc/X11/XF86Config:
Section "Device"
BoardName "Riva TnT 128"
BusID "0:13:0"
Driver "nvidia"
Identifier "Device[0]"
Screen 0
VendorName "NVidia"
EndSection
And these under "Modules"
Load "record"
Load "glx"
Note that you have to remove all references to dri (Load "dri" and
the DRI
section), or you'll get a big green square that won't go away.
Once this is loaded correctly, you get this:
cyberspace:/home/steen # lsmod
Module Size Used by
dv1394 18528 0 (unused)
raw1394 7552 0 (unused)
ohci1394 17712 0 [dv1394]
ieee1394 32496 0 [dv1394 raw1394 ohci1394]
NVdriver 1066256 10 (autoclean)
nfsd 72560 4 (autoclean)
ext3 68480 3 (autoclean)
jbd 49872 3 (autoclean) [ext3]
cyberspace:/home/steen # xvinfo
X-Video Extension version 2.2
screen #0
Adaptor #0: "NV04 Video Overlay"
number of ports: 1
port base: 63
operations supported: PutImage
supported visuals:
depth 16, visualID 0x21
depth 16, visualID 0x23
depth 16, visualID 0x22
depth 16, visualID 0x24
number of attributes: 4
"XV_DOUBLE_BUFFER" (range 0 to 1)
client settable attribute
client gettable attribute (current value is 1)
"XV_COLORKEY" (range 0 to 16777215)
client settable attribute
client gettable attribute (current value is 2110)
"XV_AUTOPAINT_COLORKEY" (range 0 to 1)
client settable attribute
client gettable attribute (current value is 1)
"XV_SET_DEFAULTS" (range 0 to 0)
client settable attribute
maximum XvImage size: 2046 x 2046
Number of image formats: 4
id: 0x32595559 (YUY2)
guid: 59555932-0000-0010-8000-00aa00389b71
bits per pixel: 16
number of planes: 1
type: YUV (packed)
id: 0x32315659 (YV12)
guid: 59563132-0000-0010-8000-00aa00389b71
bits per pixel: 12
number of planes: 3
type: YUV (planar)
id: 0x59565955 (UYVY)
guid: 55595659-0000-0010-8000-00aa00389b71
bits per pixel: 16
number of planes: 1
type: YUV (packed)
id: 0x30323449 (I420)
guid: 49343230-0000-0010-8000-00aa00389b71
bits per pixel: 12
number of planes: 3
type: YUV (planar)
It loads slowly, but regrettably this is what is required to get
the xv extension, which you need for watching video. So that's the
end of that saga.
May 4.2.0 upgrade
On 18 May 02 I upgraded XFree86 from SuSE's 4.1.0 to SuSE's 4.2.0,
as described in the cyberspace
installation. There is a configuration tool you might want to try
-- xf86cfg. The Changes file claims "The mouse driver can now handle
replug events on Linux for PS/2 mice." The README file says,
To install XFree86 4.2.0 download the appropriate files, i.e.
the files located in suse73 (SuSE Linux 7.3) and type the following
commands to update XFree86 to release 4.2.0 in your download
directory:
# rpm --nodeps --force -Uhv *.rpm
# ldconfig
Just ignore the warnings (if there are any).
For configuration of XFree86 4.2.0 use the configuration XFree86
tools 'xf86config', 'xf86cfg' or the SuSE XFree86 4 configuration
tool SaX2. SaX2 is located in suse73/sax2 (SuSE Linux 7.3). Install
SaX2 with
rpm -Uhv sax*.i386.rpm
Make sure that the following packages are installed. They are
required by SaX2!
- perl (series a)
- perl_tk (series perl)
- perl_sto (series perl)
- perl_gtx (series perl)
- xbanner (series xap)
Just type the following command if you want to use SaX2 for
configuratin.
# sax2
If the mouse does not work please run SaX2 with the following
options:
# sax2 -n /dev/<mousedevice> -t <protocol>
The README file is on gubbio under src/packages/SOURCES in the
XFree86 directory. The man pages have also been installed.
April 2002 update
On 28 April I started experimenting with X-windows -- a lot of
stuff works spectacularly, but it remains a bit of a puzzle.
First, I verified that /etc/ssh and sshd permitted X-forwarding;
that's not a problem. In summary, the problem is the xdm
authentication scheme, which I don't understand -- see man
pages.
Secondly, if you SSH from Gubbio to Cyberspace, you can simply
start applications on Cyberspace and they run fine, just like under
VNC! I've tried this with Konqueror, knode, kbear, Pixie -- it looks
like any individual program will run, and they respond reasonably
fast and just run -- faster than VNC by far, close to the local
machine.
Note that this just works -- I don't pass any special parameters,
I don't redirect the display: it just works. It also works
spectacularly well: I can start pixie on gubbio as local and pixie on
Cyberspace as remote, and then drag and drop files between the two
systems through pixie! And the remote pixie looks exactly as good as
the local pixie -- I can't tell the difference, and we're talking
about pictures here.
Third, you can't run kde in this way -- there's some weird
interference with kde running on gubbio, which doesn't make sense.
Fourth, you can't follow the instructions and write
% export DISPLAY=128.97.184.97
or
pixie -display 128.97.184.97:0 &
This attempt is stopped by a control scheme:
steen@cyberspace:~> Xlib: connection to "128.97.184.97:0.0"
refused by server
Xlib: Invalid XDM-AUTHORIZATION-1 key (failed key comparison)
pixie: cannot connect to X server 128.97.184.97:0
This control scheme may be xauth. Here's how you ask for the xauth
of the local user:
steen@cyberspace:~> xauth list :0
Cyberspace/unix:0 MIT-MAGIC-COOKIE-1
ae006e93da491045d6b8ea50d3252788
In the same way you can get the xauth keys for the remotely logged
in user:
steen@cyberspace:~> xauth list 128.97.184.97:0
steen1.sscnet.ucla.edu:0 MIT-MAGIC-COOKIE-1
65c2a1e508fb44288fdbd4cd9e9b48a2
steen1.sscnet.ucla.edu:0 XDM-AUTHORIZATION-1
477942a6f167b1d3009d82710115afa6
I then tried to add one of these to the xauth, but that didn't see
to make a difference:
steen@cyberspace:~> xauth add steen1.sscnet.ucla.edu:0
XDM-AUTHORIZATION-1 477942a65afa6
steen@cyberspace:~> pixie -display 128.97.184.97:0 &
[1] 739
steen@cyberspace:~> Xlib: connection to "128.97.184.97:0.0"
refused by server
Xlib: Invalid XDM-AUTHORIZATION-1 key (failed key comparison)
pixie: cannot connect to X server 128.97.184.97:0
The control scheme is important -- anyone who has access to your
terminal can see everything you do.
- The configuration file is /etc/X11/xdm/xdm-config
- See the README.security file in the same directory
- I commented out the last line of the xdm-config file to allow
xdm and started xcm, but no dice
- I should likely modify the file Xservers in the same
directory
I left it at that -- some permission problem. I could ask Daniel
Tran.
|
