Logitech MX Master won't stay Connected to Debian Stretch












0















To preface this, I owned this mouse for over a year now and have used it with no problems on this same hardware with different Linux distros (Fedora, Arch, Manjaro). It was not until I installed Debian 9 that I started having issues.



Firstly, the only way I am able to get the mouse to pair is directly after a reboot, otherwise pairing fails altogether. Then, after pairing or turning the mouse on for the first time, the mouse will connect and the light turns solid for about three seconds then the light on the mouse begins slow blink as if nothing is connected to the mouse. At no point during this process does moving the mouse cause the cursor to move on the screen. Additionally, after connecting the mouse initially, running the info command in the bluetoothctl terminal prints the following output.



Device D3:08:24:D5:FE:3F
Name: MX Master
Alias: MX Master
Appearance: 0x03c2
Icon: input-mouse
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb)
UUID: Battery Service (0000180f-0000-1000-8000-00805f9b34fb)
UUID: Human Interface Device (00001812-0000-1000-8000-00805f9b34fb)
UUID: Vendor specific (00010000-0000-1000-8000-011f2000046d)
Modalias: usb:v046DpB017d0017


The mouse continues to show as Connected: yes even after the mouse disconnects or is powered off entirely. I have tried unpairing and pairing the mouse numerous times under different conditions. I've tried the advice from the following posts:




  • Bluetooth connection fails by connecting to the Logitech MX Master S2 mouse

  • Pairing a Logitech MX Master Mouse with Ubuntu 16.04 Using Bluetooth

  • Logitech MX Master Mouse pairs, but won't work


I am running BlueZ version 5.43-2+deb9u1 on Linux kernel 4.9.0-8-amd64 on a Thinkpad T480. What can I do to solve this?









share







New contributor




Will Carroll is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

























    0















    To preface this, I owned this mouse for over a year now and have used it with no problems on this same hardware with different Linux distros (Fedora, Arch, Manjaro). It was not until I installed Debian 9 that I started having issues.



    Firstly, the only way I am able to get the mouse to pair is directly after a reboot, otherwise pairing fails altogether. Then, after pairing or turning the mouse on for the first time, the mouse will connect and the light turns solid for about three seconds then the light on the mouse begins slow blink as if nothing is connected to the mouse. At no point during this process does moving the mouse cause the cursor to move on the screen. Additionally, after connecting the mouse initially, running the info command in the bluetoothctl terminal prints the following output.



    Device D3:08:24:D5:FE:3F
    Name: MX Master
    Alias: MX Master
    Appearance: 0x03c2
    Icon: input-mouse
    Paired: yes
    Trusted: yes
    Blocked: no
    Connected: yes
    LegacyPairing: no
    UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
    UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
    UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb)
    UUID: Battery Service (0000180f-0000-1000-8000-00805f9b34fb)
    UUID: Human Interface Device (00001812-0000-1000-8000-00805f9b34fb)
    UUID: Vendor specific (00010000-0000-1000-8000-011f2000046d)
    Modalias: usb:v046DpB017d0017


    The mouse continues to show as Connected: yes even after the mouse disconnects or is powered off entirely. I have tried unpairing and pairing the mouse numerous times under different conditions. I've tried the advice from the following posts:




    • Bluetooth connection fails by connecting to the Logitech MX Master S2 mouse

    • Pairing a Logitech MX Master Mouse with Ubuntu 16.04 Using Bluetooth

    • Logitech MX Master Mouse pairs, but won't work


    I am running BlueZ version 5.43-2+deb9u1 on Linux kernel 4.9.0-8-amd64 on a Thinkpad T480. What can I do to solve this?









    share







    New contributor




    Will Carroll is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.























      0












      0








      0








      To preface this, I owned this mouse for over a year now and have used it with no problems on this same hardware with different Linux distros (Fedora, Arch, Manjaro). It was not until I installed Debian 9 that I started having issues.



      Firstly, the only way I am able to get the mouse to pair is directly after a reboot, otherwise pairing fails altogether. Then, after pairing or turning the mouse on for the first time, the mouse will connect and the light turns solid for about three seconds then the light on the mouse begins slow blink as if nothing is connected to the mouse. At no point during this process does moving the mouse cause the cursor to move on the screen. Additionally, after connecting the mouse initially, running the info command in the bluetoothctl terminal prints the following output.



      Device D3:08:24:D5:FE:3F
      Name: MX Master
      Alias: MX Master
      Appearance: 0x03c2
      Icon: input-mouse
      Paired: yes
      Trusted: yes
      Blocked: no
      Connected: yes
      LegacyPairing: no
      UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
      UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
      UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb)
      UUID: Battery Service (0000180f-0000-1000-8000-00805f9b34fb)
      UUID: Human Interface Device (00001812-0000-1000-8000-00805f9b34fb)
      UUID: Vendor specific (00010000-0000-1000-8000-011f2000046d)
      Modalias: usb:v046DpB017d0017


      The mouse continues to show as Connected: yes even after the mouse disconnects or is powered off entirely. I have tried unpairing and pairing the mouse numerous times under different conditions. I've tried the advice from the following posts:




      • Bluetooth connection fails by connecting to the Logitech MX Master S2 mouse

      • Pairing a Logitech MX Master Mouse with Ubuntu 16.04 Using Bluetooth

      • Logitech MX Master Mouse pairs, but won't work


      I am running BlueZ version 5.43-2+deb9u1 on Linux kernel 4.9.0-8-amd64 on a Thinkpad T480. What can I do to solve this?









      share







      New contributor




      Will Carroll is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.












      To preface this, I owned this mouse for over a year now and have used it with no problems on this same hardware with different Linux distros (Fedora, Arch, Manjaro). It was not until I installed Debian 9 that I started having issues.



      Firstly, the only way I am able to get the mouse to pair is directly after a reboot, otherwise pairing fails altogether. Then, after pairing or turning the mouse on for the first time, the mouse will connect and the light turns solid for about three seconds then the light on the mouse begins slow blink as if nothing is connected to the mouse. At no point during this process does moving the mouse cause the cursor to move on the screen. Additionally, after connecting the mouse initially, running the info command in the bluetoothctl terminal prints the following output.



      Device D3:08:24:D5:FE:3F
      Name: MX Master
      Alias: MX Master
      Appearance: 0x03c2
      Icon: input-mouse
      Paired: yes
      Trusted: yes
      Blocked: no
      Connected: yes
      LegacyPairing: no
      UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
      UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
      UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb)
      UUID: Battery Service (0000180f-0000-1000-8000-00805f9b34fb)
      UUID: Human Interface Device (00001812-0000-1000-8000-00805f9b34fb)
      UUID: Vendor specific (00010000-0000-1000-8000-011f2000046d)
      Modalias: usb:v046DpB017d0017


      The mouse continues to show as Connected: yes even after the mouse disconnects or is powered off entirely. I have tried unpairing and pairing the mouse numerous times under different conditions. I've tried the advice from the following posts:




      • Bluetooth connection fails by connecting to the Logitech MX Master S2 mouse

      • Pairing a Logitech MX Master Mouse with Ubuntu 16.04 Using Bluetooth

      • Logitech MX Master Mouse pairs, but won't work


      I am running BlueZ version 5.43-2+deb9u1 on Linux kernel 4.9.0-8-amd64 on a Thinkpad T480. What can I do to solve this?







      linux debian ubuntu bluetooth bluez





      share







      New contributor




      Will Carroll is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.










      share







      New contributor




      Will Carroll is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.








      share



      share






      New contributor




      Will Carroll is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      asked 4 mins ago









      Will CarrollWill Carroll

      1




      1




      New contributor




      Will Carroll is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.





      New contributor





      Will Carroll is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






      Will Carroll is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






















          0






          active

          oldest

          votes











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "106"
          };
          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: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          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
          });


          }
          });






          Will Carroll is a new contributor. Be nice, and check out our Code of Conduct.










          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f494055%2flogitech-mx-master-wont-stay-connected-to-debian-stretch%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          Will Carroll is a new contributor. Be nice, and check out our Code of Conduct.










          draft saved

          draft discarded


















          Will Carroll is a new contributor. Be nice, and check out our Code of Conduct.













          Will Carroll is a new contributor. Be nice, and check out our Code of Conduct.












          Will Carroll is a new contributor. Be nice, and check out our Code of Conduct.
















          Thanks for contributing an answer to Unix & Linux Stack Exchange!


          • 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%2funix.stackexchange.com%2fquestions%2f494055%2flogitech-mx-master-wont-stay-connected-to-debian-stretch%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

          宮崎県

          濃尾地震

          シテ島