| View previous topic :: View next topic |
| Author |
Message |
mathfeel
l33t
Joined: 03 Aug 2004
Posts: 700
|
 Posted: Sat May 17, 2008 1:25 am Post subject: X key repeat problem |
 |
|
I am having a weird problem with key repeat: LEFT-ARROW and only LEFT-ARROW does not repeat when I hold it down.
- I have eliminated that it's not a hardware issue because it works in Windows boot as well as console mode
- It it also not a GNOME issue (which I am using) because starting x with startx also result in the same problem
- when I hold down other keys under xev, it would capture a sequences of events; for the LEFT-ARROW key, it'll just display two events, then stop.
- the keyboard driver I am using is 'evdev' (since last X-update).
I am running out to idea about how to isolate this bug.
_________________
-----------------------------------------------------------
"In heaven all the interesting people are missing"
-- Friedrich Nietzsche |
|
| Back to top |
|
 |
OmSai
l33t
Joined: 30 Sep 2007
Posts: 605
Location: Manchester, CT, USA
|
| Posted: Sat May 17, 2008 3:22 am Post subject: |
|
|
Hi mathfeel,
Does this command fix your issue -
| Code: | #xev says `100' is the keycode for my left-arrow key... it may be different for you ;)
xset r 100 |
If so, then you might want to provide your information to this open Xorg bug
Assuming that xset command above works for you, at the moment your workaround would be a adding it into your ~/.xinitrc file, since there is also an Xorg bug which does not allow you to save a permanent kb configuration with xkbcomp
_________________
Gentoo is the stick-shift of Linux.
You work it manually, it has somewhat better performance, but it's really for the fun of it. |
|
| Back to top |
|
|
mathfeel
l33t
Joined: 03 Aug 2004
Posts: 700
|
| Posted: Sat May 17, 2008 4:29 am Post subject: |
|
|
| OmSai wrote: | Hi mathfeel,
Does this command fix your issue -
| Code: | #xev says `100' is the keycode for my left-arrow key... it may be different for you ;)
xset r 100 |
If so, then you might want to provide your information to this open Xorg bug
Assuming that xset command above works for you, at the moment your workaround would be a adding it into your ~/.xinitrc file, since there is also an Xorg bug which does not allow you to save a permanent kb configuration with xkbcomp |
It did work. Thank you very much. I am surprised that I didn't find this bug upon googling.
_________________
-----------------------------------------------------------
"In heaven all the interesting people are missing"
-- Friedrich Nietzsche |
|
| Back to top |
|
|
OmSai
l33t
Joined: 30 Sep 2007
Posts: 605
Location: Manchester, CT, USA
|
| Posted: Sat May 17, 2008 4:35 am Post subject: |
|
|
| mathfeel wrote: | | It did work. Thank you very much. I am surprised that I didn't find this bug upon googling. |
Looks like Xorg is hiding from google's prying robots 
I pulled it up from a direct search in Xorg's Bugzilla, after some other result (a forum thread) hinted that your issue could be an X problem
_________________
Gentoo is the stick-shift of Linux.
You work it manually, it has somewhat better performance, but it's really for the fun of it. |
|
| Back to top |
|
|
VoidMage
Watchman
Joined: 14 Oct 2006
Posts: 6196
|
| Posted: Sat May 17, 2008 10:45 am Post subject: |
|
|
Actually, your solution is wrong.
It's a hal/evdev issue. I know that, cause I had the same problem.
Try `hal-find-by-capability --capability input.keys`
and post output of hal-device <device name> for every printed device.
The problem comes from the fact, that
/usr/share/hal/fdi/policy/10osvendor/10-keymap.fdi (shipped with hal)
checks for input.keymap, where it should be either input.keys or input.keyboard. |
|
| Back to top |
|
|
mathfeel
l33t
Joined: 03 Aug 2004
Posts: 700
|
| Posted: Tue May 20, 2008 12:44 am Post subject: |
|
|
| VoidMage wrote: | Actually, your solution is wrong.
It's a hal/evdev issue. I know that, cause I had the same problem.
Try `hal-find-by-capability --capability input.keys`
and post output of hal-device <device name> for every printed device. |
okie...
| Code: | $ hal-find-by-capability --capability input.keys
/org/freedesktop/Hal/devices/computer_logicaldev_input_3
/org/freedesktop/Hal/devices/computer_logicaldev_input
/org/freedesktop/Hal/devices/platform_i8042_i8042_KBD_port_logicaldev_input
|
| Quote: |
The problem comes from the fact, that
/usr/share/hal/fdi/policy/10osvendor/10-keymap.fdi (shipped with hal)
checks for input.keymap, where it should be either input.keys or input.keyboard. |
_________________
-----------------------------------------------------------
"In heaven all the interesting people are missing"
-- Friedrich Nietzsche |
|
| Back to top |
|
|
Insanity5902
Veteran
Joined: 23 Jan 2004
Posts: 1228
Location: Fort Worth, Texas
|
| Posted: Thu May 29, 2008 8:25 pm Post subject: |
|
|
Found these things in the emerge of sys-apps/hal-0.5.11-r1
| Quote: | * X Input Hotplugging (if you build xorg-server with the HAL useflag)
* reads user specific configuration from /etc/hal/fdi/policy/.
* We have converted your existing xorg.conf rules and the FDI is stored
* at /etc/hal/fdi/policy/10-x11-input.fdi
* You should remove the Input sections from your xorg.conf once you have
* migrated the rules to a HAL fdi file.
|
This also modified my /etc/hal/fdi/policy/10-x11-input.fdi -- which is now empty
after merging this update, I still have keyboard settings in my x11-xorg, 10-x11-input.fdi is empty, and after restarting hald my arrow keys work.
_________________
Join the adopt an unanswered post initiative today |
|
| Back to top |
|
|
Insanity5902
Veteran
Joined: 23 Jan 2004
Posts: 1228
Location: Fort Worth, Texas
|
| Posted: Fri May 30, 2008 12:57 pm Post subject: |
|
|
Booted up today, the two arrow keys don't "auto-repeat" .
I commented out all references to the keyboard/mouse input sections, included their declarations in the server layout.
I looked and found the input fdi file in /usr/share/hal/fdi/policy/10osvendor/10-x11-input.fdi . It contained entries for using evdev for both the keyboard and the mouse. I rebooted and no my synaptic mousepad didn't work 100%, I copied the mouse portion out of this file and into /etc/hal/fdi/policy/10-x11-input.fdi, change the device name and driver for synaptics, and now my synaptics work.
my keyboard is set up as follows | Code: | <match key="info.capabilities" contains="input.keys">
<!-- If we're using Linux, we use evdev by default (falling back to
keyboard otherwise). -->
<merge key="input.x11_driver" type="string">keyboard</merge>
<match key="/org/freedesktop/Hal/devices/computer:system.kernel.name"
string="Linux">
<merge key="input.x11_driver" type="string">evdev</merge>
</match>
</match>
|
With gnome-keyboard-properties shows the same information, evdev managed, us layout, no assecibility and auto-repeat is turned on
And for the record
| Code: | % hal-find-by-capability --capability input.keys
/org/freedesktop/Hal/devices/platform_i8042_i8042_KBD_port_logicaldev_input
|
_________________
Join the adopt an unanswered post initiative today |
|
| Back to top |
|
|
VoidMage
Watchman
Joined: 14 Oct 2006
Posts: 6196
|
| Posted: Fri May 30, 2008 5:12 pm Post subject: |
|
|
You definitely misunderstood me.
Output of `hal-find-by-capability --capability input.keys` is of no interest.
What is interesting is output of `hal-device <device name>` on every device listed
by previous command.
But as long as it works , it doesn't matter. |
|
| Back to top |
|
|
ziggysquatch
Apprentice
Joined: 16 Nov 2004
Posts: 172
Location: /USA/Minnesota
|
| Posted: Fri May 30, 2008 5:54 pm Post subject: |
|
|
I think you have to add this to your xorg.conf to stop hal from messing with input stuff:
| Code: |
Option "AutoAddDevices" "FALSE"
|
I had to do that because I didn't want hal telling X how to use my bluetooth mouse. It would only have vertical movement before I added that line to the conf. |
|
| Back to top |
|
|
mathfeel
l33t
Joined: 03 Aug 2004
Posts: 700
|
| Posted: Wed Jun 11, 2008 8:54 pm Post subject: |
|
|
| ziggysquatch wrote: | I think you have to add this to your xorg.conf to stop hal from messing with input stuff:
| Code: |
Option "AutoAddDevices" "FALSE"
|
I had to do that because I didn't want hal telling X how to use my bluetooth mouse. It would only have vertical movement before I added that line to the conf. |
I think I do like this line because HAL works for me. Maybe I just had the right kind of hardware.
Anyway, I fixed the problem by adding the required xset line to /etc/X11/xinit/xinitrc
It works in GNOME (basically xdm started session), but not when I just run startx.
I thought this were strange because I put in the same place where twm is called in the system xinitrc file, and clearly twm and 3 xterm windows started correctly:
| Code: | ...
# Failsafe
else
# start some nice programs
twm &
xclock -geometry 50x50-1+1 &
xterm -geometry 80x50+494+51 &
xterm -geometry 80x20+494-0 &
exec xterm -geometry 80x66+0+0 -name login
fi
# temperarily fix the left-arrow repeat problem
xset r 113
|
_________________
-----------------------------------------------------------
"In heaven all the interesting people are missing"
-- Friedrich Nietzsche |
|
| Back to top |
|
|
VoidMage
Watchman
Joined: 14 Oct 2006
Posts: 6196
|
|
| Back to top |
|
|
Insanity5902
Veteran
Joined: 23 Jan 2004
Posts: 1228
Location: Fort Worth, Texas
|
| Posted: Thu Jun 12, 2008 5:00 am Post subject: |
|
|
For those who don't make it over to the other thread. I've found a solution, though I still don't know what my problem is.
After reading through, it sound like it was a gnome/gconf problem overwriting HAL. I ran gconf-cleaner, sadly I was impatient and didn't let it run so it cleared them out before I could read anything, but it cleaned out over 650 keys and when I restarted X, my keyboard now works fine.[/post]
_________________
Join the adopt an unanswered post initiative today |
|
| Back to top |
|
|
|
Desktop Environments
