[Bug 1483629] Middle mouse button failed on Thinkpad T520/T530
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1483629
--- Comment #6 from Peter Hutterer <peter.hutterer(a)redhat.com> ---
fwiw, is's usually easy to figure out what libinput is doing by running 'sudo
libinput debug-events' and then looking at the output.
if I'm reading this correctly, a middle button press + move triggers a zoom,
not an orbit. That's caused by the middle button scroll emulation that is
enabled by default on the trackpoint devices, it converts middle down +
movement to a wheel event equivalent.
under X you can permanently disable this with an xorg.conf snippet that sets
Option "ScrollMethod" "none" for that device. Or with xinput set-prop "device
name" "libinput Scroll Method Enabled" 0 0 0, but that's not persistent. I
don't think GNOME has a toggle for that yet.
--
You are receiving this mail because:
You are on the CC list for the bug.
6 years, 5 months
[Bug 1483629] Middle mouse button failed on Thinkpad T520/T530
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1483629
Luya Tshimbalanga <luya(a)fedoraproject.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Middle mouse emulation |Middle mouse button failed
|failed on Thinkpad t520 |on Thinkpad T520/T530
--- Comment #5 from Luya Tshimbalanga <luya(a)fedoraproject.org> ---
As per request, renaming the title.
--
You are receiving this mail because:
You are on the CC list for the bug.
6 years, 5 months
[Bug 1483629] Middle mouse emulation failed on Thinkpad t520
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1483629
--- Comment #4 from Peter Rathlev <peter(a)rathlev.dk> ---
I'm also on a Thinkpad, though a T530 (specifically model 24295ZG). So it's
probably specific to Thinkpad.
Agree that it's not Blender. And good thing to rename the bug, but I don't
think it's emulation failing. Emulation (when using left+right lower mouse
buttons, those that belong to the touchpad) actually works, whereas the
physical middle mouse button (upper buttons, between the spacebar and the
touchpad) does not. Maybe it could be called "Middle mouse button fails on
Thinpad T520/T530"?
It tested installing "xorg-x11-drv-synaptics-legacy" and that does not seem to
make a difference to this problem, though the touchpad does seem to handle a
bit better.
I have perused the Lenovo forum thread and it doesn't look like the same
problem to me. In this case everything except the physical middle mouse button
works, and the problems seems to be that the "press" event is held back until
the button is released, at which point it arrives together with the "release"
event. And this is seen with "xev"; testing with "evtest" from a text VTY shows
events arriving as expected, "press" on button down and "release" on button up.
--
You are receiving this mail because:
You are on the CC list for the bug.
6 years, 5 months
[Bug 1483629] Middle mouse emulation failed on Thinkpad t520
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1483629
Luya Tshimbalanga <luya(a)fedoraproject.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Orbiting the scene doesn't |Middle mouse emulation
|work |failed on Thinkpad t520
--- Comment #3 from Luya Tshimbalanga <luya(a)fedoraproject.org> ---
Lets change the title for better description of the problem.
--
You are receiving this mail because:
You are on the CC list for the bug.
6 years, 5 months
[Bug 1483629] Orbiting the scene doesn't work
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1483629
Luya Tshimbalanga <luya(a)fedoraproject.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
CC| |dchen(a)redhat.com,
| |luya(a)fedoraproject.org,
| |peter.hutterer(a)redhat.com
Component|blender |libinput
Hardware|Unspecified |All
Assignee|luya_tfz(a)thefinalzone.net |peter.hutterer(a)redhat.com
--- Comment #2 from Luya Tshimbalanga <luya(a)fedoraproject.org> ---
Hello(In reply to Ralf Baechle from comment #0)
> Description of problem:
>
> Fedora 26/blender-2.78c-4 on Thinkpad T520
>
> Steps to reproduce:
> Start blender with the default scene and default settings. In the default
> scene press and hold the middle mouse button of the three mouse buttons
> below the laptop's space bar and move the TrackPoint in any direction.
> Orbiting won't work, that is moving left or right will not have any effect
> while moving up and down will zoom in and out - but orbiting is expected.
Hello Ralf,
I just saw this report at the time of writing (I don't know why this report did
not show up on my e-mail until now).
What you faced seemed a issue related to Thinkpad as I am unable to reproduce
on my laptop, an ASUS X550 running the latest stable Blender.
Further research to Lenovo possibly releaved an issue with libinput:
https://forums.lenovo.com/t5/Linux-Discussion/Thinkpad-X1-Carbon-2017-Gen...
thus assigning the report to that component.
--
You are receiving this mail because:
You are on the CC list for the bug.
6 years, 5 months
[Bug 1483629] Orbiting the scene doesn't work
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1483629
Peter Rathlev <peter(a)rathlev.dk> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |peter(a)rathlev.dk
--- Comment #1 from Peter Rathlev <peter(a)rathlev.dk> ---
I have what I think is the same problem, though using camera panning in Kerbal
Space Program instead.
Testing from a text VTY with "evtest" shows seperate events on press and
release for all buttons, including the middle trackpoint button. But testing
with "xev" in a running Xorg session only fires events on release (though both
press and release are then logged) when using the middle mouse button.
So it seems like the kernel does things right, but somewhere on the way to X
something stops working. I have only today upgraded to Fedora 26, so I don't
know when the problem appeared. I have not seen the problem with Fedora 25.
While searching I stumbled upon bug 1482640, but I have no idea it it's
related.
How does one debug further on this? Specifically whatever is between what
evtest reads from (kernel?) and what xev reads from (Xorg?).
(And this is like _super_ critical, not being able to play Kerbal Space Program
to its full extent is a big problem. ;-])
--
You are receiving this mail because:
You are on the CC list for the bug.
6 years, 5 months