nanogui: "Keyboard Initialize Error" when using on X11?
Subject:
RE: [nanogui] "Keyboard Initialize Error" when using on X11?
From:
Simon Wood ####@####.####
Date:
25 Mar 2002 08:52:10 -0000
Message-Id: <44632C76B97BD211AF6B00805FADCAB208790BBA@exchange.saltaire.pace.co.uk>
Yes I've seen this before (and I mentioned it on the list) when I was
running over VNC as a tester system at work.
Attached is the previous email, not really a fix, but a quick bodge to
get it working....
Simon Wood
-----Original Message-----
From: ####@####.#### ####@####.####
Sent: Monday, March 25, 2002 4:56 AM
To: ####@####.####
Subject: [nanogui] "Keyboard Initialize Error" when using on X11?
Hi, How's it going?
I have been using microwindows 0.89pre8 and lower version on RedHat 7.1.
We were using X11 for debugging and after that we do cross-compile and
link it with the framebuffer version.
The problem is... After upgrading to RedHat Linux 7.2, I get these
message from microwindows.
(Not on framebuffer, but on X11)
'Error reading Indicator Status'
'Cannot initialise keyboard'
So, I tried where that happens, and I found that it was happening on
'src/device/kdb_x11.c' on init_modstate() function.
XkbGEtIndicatorStatus() made the 'Error reading Indicator Status' and
the other will be the result of the failure of init_modstate().
Is there some significant changes between 7.1 and 7.2?
Hmm..
May be that could be some problem with Xwindow's authentication.
Sincerly,
Ashuaria Lee
---------------------------------------------------------------------
To unsubscribe, e-mail: ####@####.####
For additional commands, e-mail: ####@####.####
Hi all,
The subject says it all....
In the function init_modstate (very end of src/drivers/kbd_x11.c) it
returns -1 if XkbGetIncatorState doesn't return 'Success'. This results
in the message 'Error reading indicator state'.
It appears that this fails all the time when you use X over VNC.
Making the return value 0 results in a working system, however this is
not really a suitable fix....
Simon Wood
PS I'm only using VNC as it's stateless and that means that I don't
loose my session when my (work) Windows machine crashes... :-)
