nanogui: Cannot bind to named socket


Previous by date: 22 May 2001 09:27:34 -0000 Re: unicode chinese display?, yi yang
Next by date: 22 May 2001 09:27:34 -0000 Re: GTK+ port to nano-X, Paolo Molaro
Previous in thread: 22 May 2001 09:27:34 -0000 Re: Cannot bind to named socket, Jordan Crouse
Next in thread: 22 May 2001 09:27:34 -0000 Cannot bind to named socket, victor

Subject: Re: Cannot bind to named socket
From: mcmew ####@####.####
Date: 22 May 2001 09:27:34 -0000
Message-Id: <3B0A3123.D78F6F2A@bigfoot.com>

I am sorry I got the same problem, and I have configured with no mouse
and no keyboard
when compiling nano-X (actually I don't know if I am wrong to do that).

I got:
KDGKMODE: Invalid argument
Cannot initialise keyboard

Anyone could help is much appreciated.

Thanks very much.

McMew

-----------------------------------------
You are also getting an

  'Cannot initialize keyboard'

  error, which means that Microwindows was unable to open your
keyboard.  The
  most common reason for this is that you don't have the correct TTY
devices
  available.  Make sure that you have /dev/tty on your system, and that
it
  points to the correct device. 

  Jordan

Previous by date: 22 May 2001 09:27:34 -0000 Re: unicode chinese display?, yi yang
Next by date: 22 May 2001 09:27:34 -0000 Re: GTK+ port to nano-X, Paolo Molaro
Previous in thread: 22 May 2001 09:27:34 -0000 Re: Cannot bind to named socket, Jordan Crouse
Next in thread: 22 May 2001 09:27:34 -0000 Cannot bind to named socket, victor


Powered by ezmlm-browse 0.20.