linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 202203] New: Bluetooth mouse doesn't move until sending a pair request
Date: Wed, 09 Jan 2019 21:03:20 +0000	[thread overview]
Message-ID: <bug-202203-62941@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=202203

            Bug ID: 202203
           Summary: Bluetooth mouse doesn't move until sending a pair
                    request
           Product: Drivers
           Version: 2.5
    Kernel Version: 4.20
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Bluetooth
          Assignee: linux-bluetooth@vger.kernel.org
          Reporter: felixonmars@gmail.com
        Regression: No

Created attachment 280363
  --> https://bugzilla.kernel.org/attachment.cgi?id=280363&action=edit
btmon output when the mouse "connects" but not moving

My Bluetooth LE mouse (Rapoo MT750) doesn't move when it's turned off and on
again. The problem is that it's shown as connected but the pointer won't move.
The mouse itself (reading from LED) doesn't think it's connected.

The mouse works if I disable/re-enable bluetooth (using laptop's key binding),
or simply send a "pair" command in bluetoothctl. The pair operation here will
always timeout, but the mouse correctly moves right after sending the command.
The pair command will succeed after a second try (after the first timeout), but
it doesn't fix the problem (shown as unpaired after reconnecting).

-- 
You are receiving this mail because:
You are the assignee for the bug.

             reply	other threads:[~2019-01-09 21:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-09 21:03 bugzilla-daemon [this message]
2019-01-09 21:04 ` [Bug 202203] Bluetooth mouse doesn't move until sending a pair request bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-202203-62941@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).