Description of problem: I have this input device section in my xorg.conf file which has always worked: Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "Auto" Option "Device" "/dev/input/mice" Option "ZAxisMapping" "4 5" Option "Emulate3Buttons" "no" Option "DragLockButtons" "2 1" EndSection That sets up button 2 to act as a drag lock of button 1. In the new fedora 9 version of X11 it no longer has any effect. Button 2 still shows up as button 2, and I get no drag lock (which makes a trackball virtually impossible to use). Version-Release number of selected component (if applicable): xorg-x11-server-Xorg-1.4.99.901-29.20080415.fc9.x86_64 How reproducible: always Steps to Reproduce: 1. add the DragLockButtons definition 2. restart X (or reboot - it is juat as ineffective) 3. get no drag lock Actual results: no drag lock Expected results: click button 2 to look like button 1 is held down Additional info: I'll attach the full xorg.conf as well as the log file showing that X recognized the directive and claimed to setup the drag lock. This same input device works great on fedora 8.
Created attachment 305559 [details] The xorg.conf file
Created attachment 305561 [details] The X log file that doesn't work
Created attachment 305562 [details] The log from fedora 8 where it worked fine
Just to be belt and suspenders, I reported this upstream as well: https://bugs.freedesktop.org/show_bug.cgi?id=15961
FYI, upstream just got drag lock support. (moving to xorg-x11-drv-evdev component)
evdev 2.1 has drag lock support https://admin.fedoraproject.org/updates/xorg-x11-drv-evdev-2.1.0-1.fc10 you can get a package from http://koji.fedoraproject.org/koji/buildinfo?buildID=70181
To make draglocks work for my account under Fedora 13 I did the following sudo yum install xinput create a .xprofile file with the following content xinput --set-int-prop 'ImExPS/2 Generic Explorer Mouse' 'Evdev Drag Lock Buttons' 8 8 1 9 3 chmod a+x .xprofile Re login to the xserver. Drag locks work perfectly.
Yea, draglock did finally make it into evdev and xinput, but it was first disabled for quite some time because they made evdev the default before providing all the features that the old input system previously had (an all too common phenomenon :-). But talk about underdocumented features, where the heck did ~/.xprofile come from? I never heard of it. In any case, I need to use this program: http://home.comcast.net/~tomhorsley/software/xdbusd/xdbusd.html which provides a hack for yet another missing feature: It re-runs the xinput command to setup draglock when I plug the mouse back in after unplugging it (which is what happens when I switch to a different system with my KVM box).