Ubuntu 18 - Touchpad Buttons not working












4















I have installed Ubuntu 18 on my new Notebook



Everything works fine, except the right and left click Button of the touchpad. When I tap with one finger (left click) oder with two fingers (right click) on the touch field. It works, but not the mechanical buttons below...



$ xinput 
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ Logitech USB-PS/2 Optical Mouse id=8 [slave pointer (2)]
⎜ ↳ HTIX5288:00 0911:5288 Touchpad id=10 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Video Bus id=6 [slave keyboard (3)]
↳ Power Button id=7 [slave keyboard (3)]
↳ USB 2.0 PC Camera: PC Camera id=9 [slave keyboard (3)]
↳ Intel HID events id=11 [slave keyboard (3)]
↳ Intel HID 5 button array id=12 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=13 [slave keyboard (3)]


I have tried to modify the synclient with



LTCornerButton
LBCornerButton
RTCornerButton
RBCornerButton



But I think this parameter are not the right ones...



Does anyone have an idea? Because every solution i find somewhere is for the problem, that the whole touchpad doesn't work...



Best regards,
Martin










share|improve this question

























  • Does this answer work askubuntu.com/a/1067292/790920 ?

    – abu_bua
    Aug 25 '18 at 15:18











  • Hi, Martin what's the output of xinput list-props 10? you may want to look at Capabilities property or maybe other you may find relevant. You can use this page as reference

    – aasril
    Sep 8 '18 at 1:41


















4















I have installed Ubuntu 18 on my new Notebook



Everything works fine, except the right and left click Button of the touchpad. When I tap with one finger (left click) oder with two fingers (right click) on the touch field. It works, but not the mechanical buttons below...



$ xinput 
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ Logitech USB-PS/2 Optical Mouse id=8 [slave pointer (2)]
⎜ ↳ HTIX5288:00 0911:5288 Touchpad id=10 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Video Bus id=6 [slave keyboard (3)]
↳ Power Button id=7 [slave keyboard (3)]
↳ USB 2.0 PC Camera: PC Camera id=9 [slave keyboard (3)]
↳ Intel HID events id=11 [slave keyboard (3)]
↳ Intel HID 5 button array id=12 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=13 [slave keyboard (3)]


I have tried to modify the synclient with



LTCornerButton
LBCornerButton
RTCornerButton
RBCornerButton



But I think this parameter are not the right ones...



Does anyone have an idea? Because every solution i find somewhere is for the problem, that the whole touchpad doesn't work...



Best regards,
Martin










share|improve this question

























  • Does this answer work askubuntu.com/a/1067292/790920 ?

    – abu_bua
    Aug 25 '18 at 15:18











  • Hi, Martin what's the output of xinput list-props 10? you may want to look at Capabilities property or maybe other you may find relevant. You can use this page as reference

    – aasril
    Sep 8 '18 at 1:41
















4












4








4


1






I have installed Ubuntu 18 on my new Notebook



Everything works fine, except the right and left click Button of the touchpad. When I tap with one finger (left click) oder with two fingers (right click) on the touch field. It works, but not the mechanical buttons below...



$ xinput 
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ Logitech USB-PS/2 Optical Mouse id=8 [slave pointer (2)]
⎜ ↳ HTIX5288:00 0911:5288 Touchpad id=10 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Video Bus id=6 [slave keyboard (3)]
↳ Power Button id=7 [slave keyboard (3)]
↳ USB 2.0 PC Camera: PC Camera id=9 [slave keyboard (3)]
↳ Intel HID events id=11 [slave keyboard (3)]
↳ Intel HID 5 button array id=12 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=13 [slave keyboard (3)]


I have tried to modify the synclient with



LTCornerButton
LBCornerButton
RTCornerButton
RBCornerButton



But I think this parameter are not the right ones...



Does anyone have an idea? Because every solution i find somewhere is for the problem, that the whole touchpad doesn't work...



Best regards,
Martin










share|improve this question
















I have installed Ubuntu 18 on my new Notebook



Everything works fine, except the right and left click Button of the touchpad. When I tap with one finger (left click) oder with two fingers (right click) on the touch field. It works, but not the mechanical buttons below...



$ xinput 
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ Logitech USB-PS/2 Optical Mouse id=8 [slave pointer (2)]
⎜ ↳ HTIX5288:00 0911:5288 Touchpad id=10 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Video Bus id=6 [slave keyboard (3)]
↳ Power Button id=7 [slave keyboard (3)]
↳ USB 2.0 PC Camera: PC Camera id=9 [slave keyboard (3)]
↳ Intel HID events id=11 [slave keyboard (3)]
↳ Intel HID 5 button array id=12 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=13 [slave keyboard (3)]


I have tried to modify the synclient with



LTCornerButton
LBCornerButton
RTCornerButton
RBCornerButton



But I think this parameter are not the right ones...



Does anyone have an idea? Because every solution i find somewhere is for the problem, that the whole touchpad doesn't work...



Best regards,
Martin







mouse touchpad synaptics multi-touch






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jul 3 '18 at 20:02









dobey

32.9k33886




32.9k33886










asked Jul 3 '18 at 6:20









MaubyMauby

211




211













  • Does this answer work askubuntu.com/a/1067292/790920 ?

    – abu_bua
    Aug 25 '18 at 15:18











  • Hi, Martin what's the output of xinput list-props 10? you may want to look at Capabilities property or maybe other you may find relevant. You can use this page as reference

    – aasril
    Sep 8 '18 at 1:41





















  • Does this answer work askubuntu.com/a/1067292/790920 ?

    – abu_bua
    Aug 25 '18 at 15:18











  • Hi, Martin what's the output of xinput list-props 10? you may want to look at Capabilities property or maybe other you may find relevant. You can use this page as reference

    – aasril
    Sep 8 '18 at 1:41



















Does this answer work askubuntu.com/a/1067292/790920 ?

– abu_bua
Aug 25 '18 at 15:18





Does this answer work askubuntu.com/a/1067292/790920 ?

– abu_bua
Aug 25 '18 at 15:18













Hi, Martin what's the output of xinput list-props 10? you may want to look at Capabilities property or maybe other you may find relevant. You can use this page as reference

– aasril
Sep 8 '18 at 1:41







Hi, Martin what's the output of xinput list-props 10? you may want to look at Capabilities property or maybe other you may find relevant. You can use this page as reference

– aasril
Sep 8 '18 at 1:41












3 Answers
3






active

oldest

votes


















2





+50









synclient has no effect because Synaptics is not the TouchPad driver on Ubuntu 18.04. Default installs use libinput instead.



Now, what kind of hardware do you have and what do we need to do to enable the buttons? Previous asked for info from X input. That may help.



Why isn't libinput just doing the right thing? More likely issue is your hardware is unfamiliar to libinput and the system is guessing incorrectly on measurements. Your buttons may be under the hand rest. Possible your attempt to config with Synaptics setting makes this worse.



What brand laptop, what model TouchPad?



Oh, does a USB mouse work?






share|improve this answer
























  • Thank you very much for your comment. I opened the bounty, because I have the exact same problem as the OP, even with the same ID (HTIX5288:00 0911:5288 Touchpad) being displayed by xinput. The output of my xinput and of xinput list-props 15 can be found here: pastebin.com/pLnWqKcD . My hardware: Its a Medion Akoya E3222 (see here; unfortunately the webpage is in German: medion.com/aldi/laptops/md62450-sued-de). A USB mouse is working perfectly. I don't know how I can find out the TouchPad model, sorry.

    – PhoemueX
    Sep 10 '18 at 10:50











  • Your pastebin file shows clearly that your system is trying to use Synaptics, not libinut. So my guess does not help you, except if Synaptics is the wrong driver. I think you have a decision here, whether to try to correct the parameters with what you have or change over to libinput. libinput is the way of the future, Synaptics driver will eventually fade away. If you want to keep trying on Synaptics, first step is to run "synclient -l" to get a listing of the parameter it thinks it has now. Almost for sure, it does not know the correct boundaries of the touchpad device itself.

    – pauljohn32
    Sep 12 '18 at 17:42











  • Note the OP said goal was to get buttons, but if his xprop output is like yours, I expect that means the settings are not available. In yours, the one to concentrate on is Soft Button Areas, I think. If you change over to libinput, the big difference will be that all of those detail settings disappear. They are dedicated to creating correct for most user config files with the libinputs distribution. Peter Hutterer is the contact point and he was very helpful with fixing many settings. (gitlab.freedesktop.org/libinput/libinput). Unfortunately, links in that page are broken today.

    – pauljohn32
    Sep 12 '18 at 17:49



















0














I have the same touch pad on a Geo netbook, and I can confirm that installing Ubuntu 18.10 (Cosmic Cuttlefish) solves this issue. From what I can tell it is a result of fixes in the 4.18 kernel, so any distribution with that kernel should work too.






share|improve this answer































    0














    You need to install gnome-tweaks to solve this.
    Launch Gnome Tweaks, and go to Keyboard & Mouse tab. Change the Mouse Click Emulation setting to AREA.
    That should enable the buttons for you.






    share|improve this answer























      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%2f1051699%2fubuntu-18-touchpad-buttons-not-working%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









      2





      +50









      synclient has no effect because Synaptics is not the TouchPad driver on Ubuntu 18.04. Default installs use libinput instead.



      Now, what kind of hardware do you have and what do we need to do to enable the buttons? Previous asked for info from X input. That may help.



      Why isn't libinput just doing the right thing? More likely issue is your hardware is unfamiliar to libinput and the system is guessing incorrectly on measurements. Your buttons may be under the hand rest. Possible your attempt to config with Synaptics setting makes this worse.



      What brand laptop, what model TouchPad?



      Oh, does a USB mouse work?






      share|improve this answer
























      • Thank you very much for your comment. I opened the bounty, because I have the exact same problem as the OP, even with the same ID (HTIX5288:00 0911:5288 Touchpad) being displayed by xinput. The output of my xinput and of xinput list-props 15 can be found here: pastebin.com/pLnWqKcD . My hardware: Its a Medion Akoya E3222 (see here; unfortunately the webpage is in German: medion.com/aldi/laptops/md62450-sued-de). A USB mouse is working perfectly. I don't know how I can find out the TouchPad model, sorry.

        – PhoemueX
        Sep 10 '18 at 10:50











      • Your pastebin file shows clearly that your system is trying to use Synaptics, not libinut. So my guess does not help you, except if Synaptics is the wrong driver. I think you have a decision here, whether to try to correct the parameters with what you have or change over to libinput. libinput is the way of the future, Synaptics driver will eventually fade away. If you want to keep trying on Synaptics, first step is to run "synclient -l" to get a listing of the parameter it thinks it has now. Almost for sure, it does not know the correct boundaries of the touchpad device itself.

        – pauljohn32
        Sep 12 '18 at 17:42











      • Note the OP said goal was to get buttons, but if his xprop output is like yours, I expect that means the settings are not available. In yours, the one to concentrate on is Soft Button Areas, I think. If you change over to libinput, the big difference will be that all of those detail settings disappear. They are dedicated to creating correct for most user config files with the libinputs distribution. Peter Hutterer is the contact point and he was very helpful with fixing many settings. (gitlab.freedesktop.org/libinput/libinput). Unfortunately, links in that page are broken today.

        – pauljohn32
        Sep 12 '18 at 17:49
















      2





      +50









      synclient has no effect because Synaptics is not the TouchPad driver on Ubuntu 18.04. Default installs use libinput instead.



      Now, what kind of hardware do you have and what do we need to do to enable the buttons? Previous asked for info from X input. That may help.



      Why isn't libinput just doing the right thing? More likely issue is your hardware is unfamiliar to libinput and the system is guessing incorrectly on measurements. Your buttons may be under the hand rest. Possible your attempt to config with Synaptics setting makes this worse.



      What brand laptop, what model TouchPad?



      Oh, does a USB mouse work?






      share|improve this answer
























      • Thank you very much for your comment. I opened the bounty, because I have the exact same problem as the OP, even with the same ID (HTIX5288:00 0911:5288 Touchpad) being displayed by xinput. The output of my xinput and of xinput list-props 15 can be found here: pastebin.com/pLnWqKcD . My hardware: Its a Medion Akoya E3222 (see here; unfortunately the webpage is in German: medion.com/aldi/laptops/md62450-sued-de). A USB mouse is working perfectly. I don't know how I can find out the TouchPad model, sorry.

        – PhoemueX
        Sep 10 '18 at 10:50











      • Your pastebin file shows clearly that your system is trying to use Synaptics, not libinut. So my guess does not help you, except if Synaptics is the wrong driver. I think you have a decision here, whether to try to correct the parameters with what you have or change over to libinput. libinput is the way of the future, Synaptics driver will eventually fade away. If you want to keep trying on Synaptics, first step is to run "synclient -l" to get a listing of the parameter it thinks it has now. Almost for sure, it does not know the correct boundaries of the touchpad device itself.

        – pauljohn32
        Sep 12 '18 at 17:42











      • Note the OP said goal was to get buttons, but if his xprop output is like yours, I expect that means the settings are not available. In yours, the one to concentrate on is Soft Button Areas, I think. If you change over to libinput, the big difference will be that all of those detail settings disappear. They are dedicated to creating correct for most user config files with the libinputs distribution. Peter Hutterer is the contact point and he was very helpful with fixing many settings. (gitlab.freedesktop.org/libinput/libinput). Unfortunately, links in that page are broken today.

        – pauljohn32
        Sep 12 '18 at 17:49














      2





      +50







      2





      +50



      2




      +50





      synclient has no effect because Synaptics is not the TouchPad driver on Ubuntu 18.04. Default installs use libinput instead.



      Now, what kind of hardware do you have and what do we need to do to enable the buttons? Previous asked for info from X input. That may help.



      Why isn't libinput just doing the right thing? More likely issue is your hardware is unfamiliar to libinput and the system is guessing incorrectly on measurements. Your buttons may be under the hand rest. Possible your attempt to config with Synaptics setting makes this worse.



      What brand laptop, what model TouchPad?



      Oh, does a USB mouse work?






      share|improve this answer













      synclient has no effect because Synaptics is not the TouchPad driver on Ubuntu 18.04. Default installs use libinput instead.



      Now, what kind of hardware do you have and what do we need to do to enable the buttons? Previous asked for info from X input. That may help.



      Why isn't libinput just doing the right thing? More likely issue is your hardware is unfamiliar to libinput and the system is guessing incorrectly on measurements. Your buttons may be under the hand rest. Possible your attempt to config with Synaptics setting makes this worse.



      What brand laptop, what model TouchPad?



      Oh, does a USB mouse work?







      share|improve this answer












      share|improve this answer



      share|improve this answer










      answered Sep 8 '18 at 16:32









      pauljohn32pauljohn32

      2,414925




      2,414925













      • Thank you very much for your comment. I opened the bounty, because I have the exact same problem as the OP, even with the same ID (HTIX5288:00 0911:5288 Touchpad) being displayed by xinput. The output of my xinput and of xinput list-props 15 can be found here: pastebin.com/pLnWqKcD . My hardware: Its a Medion Akoya E3222 (see here; unfortunately the webpage is in German: medion.com/aldi/laptops/md62450-sued-de). A USB mouse is working perfectly. I don't know how I can find out the TouchPad model, sorry.

        – PhoemueX
        Sep 10 '18 at 10:50











      • Your pastebin file shows clearly that your system is trying to use Synaptics, not libinut. So my guess does not help you, except if Synaptics is the wrong driver. I think you have a decision here, whether to try to correct the parameters with what you have or change over to libinput. libinput is the way of the future, Synaptics driver will eventually fade away. If you want to keep trying on Synaptics, first step is to run "synclient -l" to get a listing of the parameter it thinks it has now. Almost for sure, it does not know the correct boundaries of the touchpad device itself.

        – pauljohn32
        Sep 12 '18 at 17:42











      • Note the OP said goal was to get buttons, but if his xprop output is like yours, I expect that means the settings are not available. In yours, the one to concentrate on is Soft Button Areas, I think. If you change over to libinput, the big difference will be that all of those detail settings disappear. They are dedicated to creating correct for most user config files with the libinputs distribution. Peter Hutterer is the contact point and he was very helpful with fixing many settings. (gitlab.freedesktop.org/libinput/libinput). Unfortunately, links in that page are broken today.

        – pauljohn32
        Sep 12 '18 at 17:49



















      • Thank you very much for your comment. I opened the bounty, because I have the exact same problem as the OP, even with the same ID (HTIX5288:00 0911:5288 Touchpad) being displayed by xinput. The output of my xinput and of xinput list-props 15 can be found here: pastebin.com/pLnWqKcD . My hardware: Its a Medion Akoya E3222 (see here; unfortunately the webpage is in German: medion.com/aldi/laptops/md62450-sued-de). A USB mouse is working perfectly. I don't know how I can find out the TouchPad model, sorry.

        – PhoemueX
        Sep 10 '18 at 10:50











      • Your pastebin file shows clearly that your system is trying to use Synaptics, not libinut. So my guess does not help you, except if Synaptics is the wrong driver. I think you have a decision here, whether to try to correct the parameters with what you have or change over to libinput. libinput is the way of the future, Synaptics driver will eventually fade away. If you want to keep trying on Synaptics, first step is to run "synclient -l" to get a listing of the parameter it thinks it has now. Almost for sure, it does not know the correct boundaries of the touchpad device itself.

        – pauljohn32
        Sep 12 '18 at 17:42











      • Note the OP said goal was to get buttons, but if his xprop output is like yours, I expect that means the settings are not available. In yours, the one to concentrate on is Soft Button Areas, I think. If you change over to libinput, the big difference will be that all of those detail settings disappear. They are dedicated to creating correct for most user config files with the libinputs distribution. Peter Hutterer is the contact point and he was very helpful with fixing many settings. (gitlab.freedesktop.org/libinput/libinput). Unfortunately, links in that page are broken today.

        – pauljohn32
        Sep 12 '18 at 17:49

















      Thank you very much for your comment. I opened the bounty, because I have the exact same problem as the OP, even with the same ID (HTIX5288:00 0911:5288 Touchpad) being displayed by xinput. The output of my xinput and of xinput list-props 15 can be found here: pastebin.com/pLnWqKcD . My hardware: Its a Medion Akoya E3222 (see here; unfortunately the webpage is in German: medion.com/aldi/laptops/md62450-sued-de). A USB mouse is working perfectly. I don't know how I can find out the TouchPad model, sorry.

      – PhoemueX
      Sep 10 '18 at 10:50





      Thank you very much for your comment. I opened the bounty, because I have the exact same problem as the OP, even with the same ID (HTIX5288:00 0911:5288 Touchpad) being displayed by xinput. The output of my xinput and of xinput list-props 15 can be found here: pastebin.com/pLnWqKcD . My hardware: Its a Medion Akoya E3222 (see here; unfortunately the webpage is in German: medion.com/aldi/laptops/md62450-sued-de). A USB mouse is working perfectly. I don't know how I can find out the TouchPad model, sorry.

      – PhoemueX
      Sep 10 '18 at 10:50













      Your pastebin file shows clearly that your system is trying to use Synaptics, not libinut. So my guess does not help you, except if Synaptics is the wrong driver. I think you have a decision here, whether to try to correct the parameters with what you have or change over to libinput. libinput is the way of the future, Synaptics driver will eventually fade away. If you want to keep trying on Synaptics, first step is to run "synclient -l" to get a listing of the parameter it thinks it has now. Almost for sure, it does not know the correct boundaries of the touchpad device itself.

      – pauljohn32
      Sep 12 '18 at 17:42





      Your pastebin file shows clearly that your system is trying to use Synaptics, not libinut. So my guess does not help you, except if Synaptics is the wrong driver. I think you have a decision here, whether to try to correct the parameters with what you have or change over to libinput. libinput is the way of the future, Synaptics driver will eventually fade away. If you want to keep trying on Synaptics, first step is to run "synclient -l" to get a listing of the parameter it thinks it has now. Almost for sure, it does not know the correct boundaries of the touchpad device itself.

      – pauljohn32
      Sep 12 '18 at 17:42













      Note the OP said goal was to get buttons, but if his xprop output is like yours, I expect that means the settings are not available. In yours, the one to concentrate on is Soft Button Areas, I think. If you change over to libinput, the big difference will be that all of those detail settings disappear. They are dedicated to creating correct for most user config files with the libinputs distribution. Peter Hutterer is the contact point and he was very helpful with fixing many settings. (gitlab.freedesktop.org/libinput/libinput). Unfortunately, links in that page are broken today.

      – pauljohn32
      Sep 12 '18 at 17:49





      Note the OP said goal was to get buttons, but if his xprop output is like yours, I expect that means the settings are not available. In yours, the one to concentrate on is Soft Button Areas, I think. If you change over to libinput, the big difference will be that all of those detail settings disappear. They are dedicated to creating correct for most user config files with the libinputs distribution. Peter Hutterer is the contact point and he was very helpful with fixing many settings. (gitlab.freedesktop.org/libinput/libinput). Unfortunately, links in that page are broken today.

      – pauljohn32
      Sep 12 '18 at 17:49













      0














      I have the same touch pad on a Geo netbook, and I can confirm that installing Ubuntu 18.10 (Cosmic Cuttlefish) solves this issue. From what I can tell it is a result of fixes in the 4.18 kernel, so any distribution with that kernel should work too.






      share|improve this answer




























        0














        I have the same touch pad on a Geo netbook, and I can confirm that installing Ubuntu 18.10 (Cosmic Cuttlefish) solves this issue. From what I can tell it is a result of fixes in the 4.18 kernel, so any distribution with that kernel should work too.






        share|improve this answer


























          0












          0








          0







          I have the same touch pad on a Geo netbook, and I can confirm that installing Ubuntu 18.10 (Cosmic Cuttlefish) solves this issue. From what I can tell it is a result of fixes in the 4.18 kernel, so any distribution with that kernel should work too.






          share|improve this answer













          I have the same touch pad on a Geo netbook, and I can confirm that installing Ubuntu 18.10 (Cosmic Cuttlefish) solves this issue. From what I can tell it is a result of fixes in the 4.18 kernel, so any distribution with that kernel should work too.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Feb 22 at 9:46









          Ian TurtonIan Turton

          1013




          1013























              0














              You need to install gnome-tweaks to solve this.
              Launch Gnome Tweaks, and go to Keyboard & Mouse tab. Change the Mouse Click Emulation setting to AREA.
              That should enable the buttons for you.






              share|improve this answer




























                0














                You need to install gnome-tweaks to solve this.
                Launch Gnome Tweaks, and go to Keyboard & Mouse tab. Change the Mouse Click Emulation setting to AREA.
                That should enable the buttons for you.






                share|improve this answer


























                  0












                  0








                  0







                  You need to install gnome-tweaks to solve this.
                  Launch Gnome Tweaks, and go to Keyboard & Mouse tab. Change the Mouse Click Emulation setting to AREA.
                  That should enable the buttons for you.






                  share|improve this answer













                  You need to install gnome-tweaks to solve this.
                  Launch Gnome Tweaks, and go to Keyboard & Mouse tab. Change the Mouse Click Emulation setting to AREA.
                  That should enable the buttons for you.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Feb 22 at 12:34









                  Kamil KhanKamil Khan

                  1




                  1






























                      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%2f1051699%2fubuntu-18-touchpad-buttons-not-working%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

                      flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

                      Mangá

                      Eduardo VII do Reino Unido