Changing click-drag delay setting?





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







1















To drag something with the mouse, it seems I have to hold the mouse button down for a fraction of a second before dragging (dragging immediately after clicking does not work).



I don't like this, but can't find any setting in the 'mouse & touchpad' settings to change it. Is there any way to reduce this delay?










share|improve this question































    1















    To drag something with the mouse, it seems I have to hold the mouse button down for a fraction of a second before dragging (dragging immediately after clicking does not work).



    I don't like this, but can't find any setting in the 'mouse & touchpad' settings to change it. Is there any way to reduce this delay?










    share|improve this question



























      1












      1








      1


      1






      To drag something with the mouse, it seems I have to hold the mouse button down for a fraction of a second before dragging (dragging immediately after clicking does not work).



      I don't like this, but can't find any setting in the 'mouse & touchpad' settings to change it. Is there any way to reduce this delay?










      share|improve this question
















      To drag something with the mouse, it seems I have to hold the mouse button down for a fraction of a second before dragging (dragging immediately after clicking does not work).



      I don't like this, but can't find any setting in the 'mouse & touchpad' settings to change it. Is there any way to reduce this delay?







      mouse settings input






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 14 '15 at 12:31







      UpTheCreek

















      asked Nov 14 '15 at 12:21









      UpTheCreekUpTheCreek

      1066




      1066






















          3 Answers
          3






          active

          oldest

          votes


















          1














          I have the same problem, though it seems to come and go, depending on system updates from Canonical.



          Interestingly, it was happening earlier to me until I plugged in an external USB mouse to test with. Now things are working perfectly, even when I remove the external USB mouse. By the way, my system is a Dell Vostro 2420 laptop with a trackpad.






          share|improve this answer































            1














            And now it's back again, at least with the trackpad. External USB mouse works fine when I plug it in. It seemed to go bad after I did a two-finger click-drag to scroll with the trackpad.






            share|improve this answer































              1














              The solution that's worked for me is toggling the input device on and off.



              First you find the input device that's misbehaving:



              foo@machine:$ xinput list
              ⎡ Virtual core pointer id=2 [master pointer (3)]
              ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
              ⎜ ↳ TPPS/2 IBM TrackPoint id=12 [slave pointer (2)]
              ⎜ ↳ SynPS/2 Synaptics TouchPad id=11 [slave pointer (2)]
              ⎣ Virtual core keyboard id=3 [master keyboard (2)]
              ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
              ↳ Power Button id=6 [slave keyboard (3)]
              ↳ Video Bus id=7 [slave keyboard (3)]
              ↳ Sleep Button id=8 [slave keyboard (3)]
              ↳ Integrated Camera id=9 [slave keyboard (3)]
              ↳ AT Translated Set 2 keyboard id=10 [slave keyboard (3)]
              ↳ ThinkPad Extra Buttons id=13 [slave keyboard (3)]


              Then you toggle that ID on and off, for me it's always been the Synaptics TouchPad (ID=11):



              foo@machine:$ xinput set-prop 11 "Device Enabled" 0
              foo@machine:$ xinput set-prop 11 "Device Enabled" 1


              And now its all working again, I think this is definitely a bug. I've randomly observed it across 3 different laptops, but haven't had the change to debug it.






              share|improve this answer


























              • This worked for me - thanks! (On openSUSE, in fact.) Yes, agree it definitely looks like a bug.

                – Adam Spiers
                yesterday














              Your Answer








              StackExchange.ready(function() {
              var channelOptions = {
              tags: "".split(" "),
              id: "89"
              };
              initTagRenderer("".split(" "), "".split(" "), channelOptions);

              StackExchange.using("externalEditor", function() {
              // Have to fire editor after snippets, if snippets enabled
              if (StackExchange.settings.snippets.snippetsEnabled) {
              StackExchange.using("snippets", function() {
              createEditor();
              });
              }
              else {
              createEditor();
              }
              });

              function createEditor() {
              StackExchange.prepareEditor({
              heartbeatType: 'answer',
              autoActivateHeartbeat: false,
              convertImagesToLinks: true,
              noModals: true,
              showLowRepImageUploadWarning: true,
              reputationToPostImages: 10,
              bindNavPrevention: true,
              postfix: "",
              imageUploader: {
              brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
              contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
              allowUrls: true
              },
              onDemand: true,
              discardSelector: ".discard-answer"
              ,immediatelyShowMarkdownHelp:true
              });


              }
              });














              draft saved

              draft discarded


















              StackExchange.ready(
              function () {
              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f697906%2fchanging-click-drag-delay-setting%23new-answer', 'question_page');
              }
              );

              Post as a guest















              Required, but never shown

























              3 Answers
              3






              active

              oldest

              votes








              3 Answers
              3






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes









              1














              I have the same problem, though it seems to come and go, depending on system updates from Canonical.



              Interestingly, it was happening earlier to me until I plugged in an external USB mouse to test with. Now things are working perfectly, even when I remove the external USB mouse. By the way, my system is a Dell Vostro 2420 laptop with a trackpad.






              share|improve this answer




























                1














                I have the same problem, though it seems to come and go, depending on system updates from Canonical.



                Interestingly, it was happening earlier to me until I plugged in an external USB mouse to test with. Now things are working perfectly, even when I remove the external USB mouse. By the way, my system is a Dell Vostro 2420 laptop with a trackpad.






                share|improve this answer


























                  1












                  1








                  1







                  I have the same problem, though it seems to come and go, depending on system updates from Canonical.



                  Interestingly, it was happening earlier to me until I plugged in an external USB mouse to test with. Now things are working perfectly, even when I remove the external USB mouse. By the way, my system is a Dell Vostro 2420 laptop with a trackpad.






                  share|improve this answer













                  I have the same problem, though it seems to come and go, depending on system updates from Canonical.



                  Interestingly, it was happening earlier to me until I plugged in an external USB mouse to test with. Now things are working perfectly, even when I remove the external USB mouse. By the way, my system is a Dell Vostro 2420 laptop with a trackpad.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Dec 8 '15 at 3:00









                  Roy WoodRoy Wood

                  212




                  212

























                      1














                      And now it's back again, at least with the trackpad. External USB mouse works fine when I plug it in. It seemed to go bad after I did a two-finger click-drag to scroll with the trackpad.






                      share|improve this answer




























                        1














                        And now it's back again, at least with the trackpad. External USB mouse works fine when I plug it in. It seemed to go bad after I did a two-finger click-drag to scroll with the trackpad.






                        share|improve this answer


























                          1












                          1








                          1







                          And now it's back again, at least with the trackpad. External USB mouse works fine when I plug it in. It seemed to go bad after I did a two-finger click-drag to scroll with the trackpad.






                          share|improve this answer













                          And now it's back again, at least with the trackpad. External USB mouse works fine when I plug it in. It seemed to go bad after I did a two-finger click-drag to scroll with the trackpad.







                          share|improve this answer












                          share|improve this answer



                          share|improve this answer










                          answered Dec 8 '15 at 3:03









                          Roy WoodRoy Wood

                          212




                          212























                              1














                              The solution that's worked for me is toggling the input device on and off.



                              First you find the input device that's misbehaving:



                              foo@machine:$ xinput list
                              ⎡ Virtual core pointer id=2 [master pointer (3)]
                              ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
                              ⎜ ↳ TPPS/2 IBM TrackPoint id=12 [slave pointer (2)]
                              ⎜ ↳ SynPS/2 Synaptics TouchPad id=11 [slave pointer (2)]
                              ⎣ Virtual core keyboard id=3 [master keyboard (2)]
                              ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
                              ↳ Power Button id=6 [slave keyboard (3)]
                              ↳ Video Bus id=7 [slave keyboard (3)]
                              ↳ Sleep Button id=8 [slave keyboard (3)]
                              ↳ Integrated Camera id=9 [slave keyboard (3)]
                              ↳ AT Translated Set 2 keyboard id=10 [slave keyboard (3)]
                              ↳ ThinkPad Extra Buttons id=13 [slave keyboard (3)]


                              Then you toggle that ID on and off, for me it's always been the Synaptics TouchPad (ID=11):



                              foo@machine:$ xinput set-prop 11 "Device Enabled" 0
                              foo@machine:$ xinput set-prop 11 "Device Enabled" 1


                              And now its all working again, I think this is definitely a bug. I've randomly observed it across 3 different laptops, but haven't had the change to debug it.






                              share|improve this answer


























                              • This worked for me - thanks! (On openSUSE, in fact.) Yes, agree it definitely looks like a bug.

                                – Adam Spiers
                                yesterday


















                              1














                              The solution that's worked for me is toggling the input device on and off.



                              First you find the input device that's misbehaving:



                              foo@machine:$ xinput list
                              ⎡ Virtual core pointer id=2 [master pointer (3)]
                              ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
                              ⎜ ↳ TPPS/2 IBM TrackPoint id=12 [slave pointer (2)]
                              ⎜ ↳ SynPS/2 Synaptics TouchPad id=11 [slave pointer (2)]
                              ⎣ Virtual core keyboard id=3 [master keyboard (2)]
                              ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
                              ↳ Power Button id=6 [slave keyboard (3)]
                              ↳ Video Bus id=7 [slave keyboard (3)]
                              ↳ Sleep Button id=8 [slave keyboard (3)]
                              ↳ Integrated Camera id=9 [slave keyboard (3)]
                              ↳ AT Translated Set 2 keyboard id=10 [slave keyboard (3)]
                              ↳ ThinkPad Extra Buttons id=13 [slave keyboard (3)]


                              Then you toggle that ID on and off, for me it's always been the Synaptics TouchPad (ID=11):



                              foo@machine:$ xinput set-prop 11 "Device Enabled" 0
                              foo@machine:$ xinput set-prop 11 "Device Enabled" 1


                              And now its all working again, I think this is definitely a bug. I've randomly observed it across 3 different laptops, but haven't had the change to debug it.






                              share|improve this answer


























                              • This worked for me - thanks! (On openSUSE, in fact.) Yes, agree it definitely looks like a bug.

                                – Adam Spiers
                                yesterday
















                              1












                              1








                              1







                              The solution that's worked for me is toggling the input device on and off.



                              First you find the input device that's misbehaving:



                              foo@machine:$ xinput list
                              ⎡ Virtual core pointer id=2 [master pointer (3)]
                              ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
                              ⎜ ↳ TPPS/2 IBM TrackPoint id=12 [slave pointer (2)]
                              ⎜ ↳ SynPS/2 Synaptics TouchPad id=11 [slave pointer (2)]
                              ⎣ Virtual core keyboard id=3 [master keyboard (2)]
                              ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
                              ↳ Power Button id=6 [slave keyboard (3)]
                              ↳ Video Bus id=7 [slave keyboard (3)]
                              ↳ Sleep Button id=8 [slave keyboard (3)]
                              ↳ Integrated Camera id=9 [slave keyboard (3)]
                              ↳ AT Translated Set 2 keyboard id=10 [slave keyboard (3)]
                              ↳ ThinkPad Extra Buttons id=13 [slave keyboard (3)]


                              Then you toggle that ID on and off, for me it's always been the Synaptics TouchPad (ID=11):



                              foo@machine:$ xinput set-prop 11 "Device Enabled" 0
                              foo@machine:$ xinput set-prop 11 "Device Enabled" 1


                              And now its all working again, I think this is definitely a bug. I've randomly observed it across 3 different laptops, but haven't had the change to debug it.






                              share|improve this answer















                              The solution that's worked for me is toggling the input device on and off.



                              First you find the input device that's misbehaving:



                              foo@machine:$ xinput list
                              ⎡ Virtual core pointer id=2 [master pointer (3)]
                              ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
                              ⎜ ↳ TPPS/2 IBM TrackPoint id=12 [slave pointer (2)]
                              ⎜ ↳ SynPS/2 Synaptics TouchPad id=11 [slave pointer (2)]
                              ⎣ Virtual core keyboard id=3 [master keyboard (2)]
                              ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
                              ↳ Power Button id=6 [slave keyboard (3)]
                              ↳ Video Bus id=7 [slave keyboard (3)]
                              ↳ Sleep Button id=8 [slave keyboard (3)]
                              ↳ Integrated Camera id=9 [slave keyboard (3)]
                              ↳ AT Translated Set 2 keyboard id=10 [slave keyboard (3)]
                              ↳ ThinkPad Extra Buttons id=13 [slave keyboard (3)]


                              Then you toggle that ID on and off, for me it's always been the Synaptics TouchPad (ID=11):



                              foo@machine:$ xinput set-prop 11 "Device Enabled" 0
                              foo@machine:$ xinput set-prop 11 "Device Enabled" 1


                              And now its all working again, I think this is definitely a bug. I've randomly observed it across 3 different laptops, but haven't had the change to debug it.







                              share|improve this answer














                              share|improve this answer



                              share|improve this answer








                              edited 18 mins ago









                              Adam Spiers

                              1033




                              1033










                              answered May 16 '17 at 12:30









                              madmazemadmaze

                              3151212




                              3151212













                              • This worked for me - thanks! (On openSUSE, in fact.) Yes, agree it definitely looks like a bug.

                                – Adam Spiers
                                yesterday





















                              • This worked for me - thanks! (On openSUSE, in fact.) Yes, agree it definitely looks like a bug.

                                – Adam Spiers
                                yesterday



















                              This worked for me - thanks! (On openSUSE, in fact.) Yes, agree it definitely looks like a bug.

                              – Adam Spiers
                              yesterday







                              This worked for me - thanks! (On openSUSE, in fact.) Yes, agree it definitely looks like a bug.

                              – Adam Spiers
                              yesterday




















                              draft saved

                              draft discarded




















































                              Thanks for contributing an answer to Ask Ubuntu!


                              • Please be sure to answer the question. Provide details and share your research!

                              But avoid



                              • Asking for help, clarification, or responding to other answers.

                              • Making statements based on opinion; back them up with references or personal experience.


                              To learn more, see our tips on writing great answers.




                              draft saved


                              draft discarded














                              StackExchange.ready(
                              function () {
                              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f697906%2fchanging-click-drag-delay-setting%23new-answer', 'question_page');
                              }
                              );

                              Post as a guest















                              Required, but never shown





















































                              Required, but never shown














                              Required, but never shown












                              Required, but never shown







                              Required, but never shown

































                              Required, but never shown














                              Required, but never shown












                              Required, but never shown







                              Required, but never shown







                              Popular posts from this blog

                              GameSpot

                              connect to host localhost port 22: Connection refused

                              Getting a Wifi WPA2 wifi connection