[Bug 971783] Re: 3 touch taps and clicks are broken
I am SO sorry, only now I read again the bug description and realized that I have to issue the command "synclient TapButton3=2 ClickFinger3=2" for it to work. I did it and now it is working. Thank you very much! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/971783 Title: 3 touch taps and clicks are broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/971783/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 971783] Re: 3 touch taps and clicks are broken
Clean Ubuntu 12.04 installation here, on asus Eee pc 1000HA and three fingers click is not working. Please, is there any workaround? This bug is *very* annoying. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/971783 Title: 3 touch taps and clicks are broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/971783/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 272606] Re: ABNT2 Numpad Keyboard keys misbehaving
I might have have found the problem.
The generic Brazil ABNT2 keyboard layout is attached.
The main difference in keypad is that the key besides the enter is a comma and
there is a key above enter (dot).
In /usr/share/X11/xkb/geometry/pc there is the ABNT2 layout map. The
numpad dot key is and comma is .
In /usr/share/X11/xkb/keycodes/evdev there is the following code:
// For brazilian ABNT2 keyboard.
xkb_keycodes "abnt2" {
include "evdev(evdev)"
};
In evdev, the keycode for is 91, which correctly outputs a comma.
But there is no definition for the key, which should have the
keycode 129 (dot).
So, I modified the ABNT2 code in the evdev file to:
// For brazilian ABNT2 keyboard.
xkb_keycodes "abnt2" {
include "evdev(evdev)"
= 129;
};
And now everything is working how is supposed to.
I am a completely newbie in this stuff, so I am not sure about this.
Here is my output from 'xprop -root | grep XKB' and xev:
_XKB_RULES_NAMES(STRING) = "evdev", "abnt2", "br", "", ""
xev for numpad comma:
KeyPress event, serial 33, synthetic NO, window 0x301,
root 0x1a6, subw 0x0, time 2036170, (298,-52), root:(309,643),
state 0x10, keycode 91 (keysym 0xffac, KP_Separator), same_screen YES,
XLookupString gives 1 bytes: (2c) ","
XmbLookupString gives 1 bytes: (2c) ","
XFilterEvent returns: False
KeyRelease event, serial 33, synthetic NO, window 0x301,
root 0x1a6, subw 0x0, time 2036286, (296,-69), root:(307,626),
state 0x10, keycode 91 (keysym 0xffac, KP_Separator), same_screen YES,
XLookupString gives 1 bytes: (2c) ","
XFilterEvent returns: False
xev for numpad dot
KeyPress event, serial 33, synthetic NO, window 0x301,
root 0x1a6, subw 0x0, time 2073656, (58,-4), root:(69,691),
state 0x10, keycode 129 (keysym 0xffae, KP_Decimal), same_screen YES,
XLookupString gives 1 bytes: (2e) "."
XmbLookupString gives 1 bytes: (2e) "."
XFilterEvent returns: False
KeyRelease event, serial 33, synthetic NO, window 0x301,
root 0x1a6, subw 0x0, time 2073738, (58,-4), root:(69,691),
state 0x10, keycode 129 (keysym 0xffae, KP_Decimal), same_screen YES,
XLookupString gives 1 bytes: (2e) "."
XFilterEvent returns: False
** Attachment added: "output1.pdf"
http://launchpadlibrarian.net/19709373/output1.pdf
--
ABNT2 Numpad Keyboard keys misbehaving
https://bugs.launchpad.net/bugs/272606
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 272606] Re: ABNT2 Numpad Keyboard keys misbehaving
I had the same problems here with the package in proposed. And had to 'downgrade' to the package in the main repository. I have found a solution to the problem. In System -> Preferences -> Keyboard Go to Layouts, then Other Options. In "Numeric keypad layout selection" choose "Legacy keypad". That is it. Now please, can someone remove the package from proposed and put the "Legacy keypad" option as default? -- ABNT2 Numpad Keyboard keys misbehaving https://bugs.launchpad.net/bugs/272606 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 272606] Re: ABNT2 Numpad Keyboard keys misbehaving
Can someone please fix this bug? It is very annoying. I am on Ubuntu 8.10 64bit. xev for dot in numeric key (above enter): KeyPress event, serial 31, synthetic NO, window 0x3c1, root 0x1a6, subw 0x0, time 49731679, (-760,347), root:(496,406), state 0x10, keycode 129 (keysym 0xffac, KP_Separator), same_screen YES, XLookupString gives 1 bytes: (2c) "," XmbLookupString gives 1 bytes: (2c) "," XFilterEvent returns: False And for comma in numeric key (beside enter): KeyPress event, serial 34, synthetic NO, window 0x3c1, root 0x1a6, subw 0x0, time 49774072, (-106,8), root:(1150,67), state 0x10, keycode 91 (keysym 0xffac, KP_Separator), same_screen YES, XKeysymToKeycode returns keycode: 129 XLookupString gives 1 bytes: (2c) "," XmbLookupString gives 1 bytes: (2c) "," XFilterEvent returns: False -- ABNT2 Numpad Keyboard keys misbehaving https://bugs.launchpad.net/bugs/272606 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
