> > > Xlib: connection to ":0.0" refused by server
> Not that strange after all - I have to use the -display option ...
Hmm - what do you give to it ? ":0.0" ? That should be equivalent ... Hmm.
Well - maybe you want to try my infamous "xggi" script:
----------------
#!/bin/bash
#
DIS=${1:-:0}
(export DISPLAY=$DIS ; sleep 3; fvwm2 & sleep 3 ;\
xmodmap /usr/local/lib/ggi/xggikeymaps/xggimap.base ; \
xmodmap /usr/local/lib/ggi/xggikeymaps/xggimap.de_de \
) &
exec XGGI $* -noxfreeemu -terminate
----------------
which works like a charm for me.
> Okay - my USB-Mouse (Logitech WingMan as I don't get used to those
> wheels) is working now with an adapter at the PS/2-port. However,
> it SHOULD also work at the USB-port as the USB-driver uses the
> PS/2-protocol.
O.K. - you probably didn't configure the mouse explicitly, then ?
The autodetection scheme only works, if the mouse is on the ps2 device,
as it is detected my its major/minor.
Try configuring it explicitly as explained in libgii/doc/inputs.txt:
You may also specify 'auto' as the mousetype. In that case
we first try to read ~/.ggi/input/linux-mouse and then
$prefix/etc/ggi/input/linux-mouse. In the first file found
we look for the following entries:
mouse <moustype>
mdev <file>
> In fact it does work under normal X. It doesn't work in monitest and XGGI.
O.K. - see above. That or permissions.
> Unfortunately, xdm and kdm still don't work - there are no errors and
> the login-dialogs do appear on the screen, but they don't take ANY input.
> In fact the console - still visible as through an alpha-mask -
> takes all the input.
That sounds like the infamous "Libggi/kgicon-program not connected to its
tty" problem. Try using the above script - with fvwm replaced.
Libggi programs don't like to be run in the background - has to do with the
linux way of controlling consoles. You should get a pretty similar effect
by running a Libggi application from mc.
CU, ANdy
--
= Andreas Beck | Email : <[EMAIL PROTECTED]> =
