Oleksandr Shybystyi, that doesn't work for gnome3? That's a shame. I think
I'm just going to give OpenSuse a try, I've had it with all those terribly
easy to solve bugs in Ubuntu that are open for more than a year.
On Wed, May 4, 2011 at 8:02 AM, Oleksandr Shybystyi
Is there any status update on this bug? I've made a button now to reset the
tapbuttons to their correct value, but it's still really annoiing that i
have to click that first before it's working right...
Groeten, David
On Tue, Nov 30, 2010 at 6:04 PM, Bartosz Wucke bwu...@gmail.com wrote:
I
attached: sysclient.log.
TapButton2 = 3
TapButton3 = 2
Is it just me, or doesn't that make sense at all?
** Attachment added: sysclient log
I found the solution for this bug here:
http://ubuntuforums.org/showthread.php?t=1460790
I don't know why but it seems like somehow someone decided it would be a
good idea just to map the tap-actions in the wrong order... I'm just
glad I can fix this problem, I hope it will be reversed for other
Public bug reported:
Binary package hint: xserver-xorg-input-synaptics
I'm using: Ubuntu 10.10 beta, xserver-xorg-input-synaptics 1.2.2-2ubuntu5
Hardware Asus K50IN laptop, with multitouch-touchpad
What I expected to happen:
I expected two-finger tap to produce a middleclick event, and
I forgot to mention: I've got this problem since upgrading to Maverick
Alpha. On Lucid, the mapping was perfectly fine.
--
two finger tap produces right-click, three-fingers produces middle-click
https://bugs.launchpad.net/bugs/646207
You received this bug notification because you are a member
6 matches
Mail list logo
