> 1) "kde &" results in the above error - that's my startup-script :-(
Hmm - that's a bit strange ... Does the XGGI server start correctly ?
> 2) "XGGI &" "xterm -display :0" doesn't work without the display option
This is correct. XGGI is only an X server - you will see the same beahviour
with a regular X server.
xterm determines its display by evaluating the DISPLAY envvar. XGGI has no
chance to set that in its parent shell ...
It usually works by xinit starting up the X server (recording the display
it started it for), setting DISPLAY to the recorded value and then going
through its xinitrc in a _subshell_ that has DISPLAY set.
> > Well - maybe you want to try my infamous "xggi" script:
> Okay it works for me, too.
Should be easily customizeable to work with other desktops.
> > Try configuring it explicitly as explained in libgii/doc/inputs.txt:
> Well I did read that stuff. But WHERE do I specify those options ??
> "./inputdump --input 'linux-mouse=ps2, /dev/mouse" doesn't have an effect.
Almost there ... LibG** specify options separated by colons ...
However "auto" is the default - just put the right mouse device and type
into the mentioned files.
> > That sounds like the infamous "Libggi/kgicon-program not connected to its
> > tty" problem. Try using the above script - with fvwm replaced.
> So xdm/kdm doesn't work with XGGI because they always start the X-Server
> in the background?
Yeah. However XGGI should work if you don't suppress the newvt stuff and
start it as root, but well ...
> By the way: Does anybody know why I can't start netscape from an
> X-Console?
What happens ?
CU, ANdy
--
= Andreas Beck | Email : <[EMAIL PROTECTED]> =
