[Ubuntu-x-swat] [Bug 366041] Re: Down and Left arrow don't repeat

2010-06-04 Thread Bryce Harrington
We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this

[Ubuntu-x-swat] [Bug 366041] Re: Down and Left arrow don't repeat

2010-06-04 Thread Oli Wade
So there's no chance of a fix for Jaunty? -- Down and Left arrow don't repeat https://bugs.launchpad.net/bugs/366041 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-evdev in ubuntu.

[Ubuntu-x-swat] [Bug 366041] Re: Down and Left arrow don't repeat

2010-05-10 Thread Bryce Harrington
[This is an automatic notification.] Hi Paulo, This bug was reported against an earlier version of Ubuntu, can you test if it still occurs on Lucid? Please note we also provide technical support for older versions of Ubuntu, but not in the bug tracker. Instead, to raise the issue through

[Ubuntu-x-swat] [Bug 366041] Re: Down and Left arrow don't repeat

2009-12-17 Thread martin hodges
I have the same issue on my Acer Travelmate 3010. Output from 'xinput list' Virtual core pointer id=0[XPointer] Num_buttons is 32 Num_axes is 2 Mode is Relative Motion_buffer is 256 Axis 0 : Min_value is -1 Max_value is

[Ubuntu-x-swat] [Bug 366041] Re: Down and Left arrow don't repeat

2009-09-02 Thread Bryce Harrington
** Tags added: jaunty -- Down and Left arrow don't repeat https://bugs.launchpad.net/bugs/366041 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-evdev in ubuntu. ___ Mailing list:

[Ubuntu-x-swat] [Bug 366041] Re: Down and Left arrow don't repeat

2009-06-09 Thread ilia
I'm using dual seat setup (2 xservers/2 monitors/2 keyboards/etc.) and has exactly this problem (on both seats) after upgrading to Jaunty. End key (code 115) is affected too. xset r workaround works for me too. Related `xset q` output before running xset r (note the second line ending with