Xfbdev grabs control of the keyboard
ersin.akinci at gmail.com
Wed Apr 21 02:01:59 PDT 2010
The saga continues...
I wrote a small script to start Xfbdev and sleep before starting xterm and
xev, and the results are interesting. xev shows that Xfbdev is clearly
getting my keyboard input and all the keysyms, keymaps, etc. are correct.
However, when I try to type into xterm nothing shows up _unless_ I turn on
num lock and type using the keypad. Of course, this means that only the
keypad works. Any reason why this may be? My gut instinct tells me that
this is not an Xfbdev-specific problem, but rather something having to do
with different keymaps or other configurations within xkb.
P.S.: I mistakenly sent another related e-mail to the list about xkbcomp,
please ignore that. (I managed to solve that problem; in case anyone was
curious, I didn't have an XkeysymsDB file installed).
On Mon, Apr 19, 2010 at 4:21 PM, Ersin Akinci <ersin.akinci at gmail.com>wrote:
> Hi everyone,
> I'm trying to use Xfbdev and I've run into a problem with the keyboard.
> When I start X with
> Xfbdev -ac -mouse mouse -keybd keyboard
> X successfully grabs my keyboard but then doesn't seem to let it go. That
> is, I can't switch to my virtual terminals with alt+f1, etc. I'm not using
> any xorg.conf file or any xkb stuff at all. It's just Xfbdev and the
> minimum required font files.
> I would also greatly appreciate if someone could explain kdrive's input
> mechanisms. I've read that Xorg now uses the evdev driver, but all the
> kdrive stuff I've found seems to indicate that it still uses the old
> keyboard driver. How does it "know" what keyboard I'm using without xkb?
> Is this somehow related to "xinput"?
> What Digital Revolution? -- www.whatdigitalrevolution.com
> Thinking critically about digital worlds.
What Digital Revolution? -- www.whatdigitalrevolution.com
Thinking critically about digital worlds.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the xorg