Hi,
I'm using a Microsoft Sculpt Touch Mouse on a Fedora 19 machine
(kernel-3.11.9-200.fc19.x86_64 and bluez-4.101-9.fc19.x86_64) with a:
Bus 002 Device 019: ID 0a5c:2148 Broadcom Corp. BCM92046DG-CL1ROM Bluetooth 2.1 Adapter
bluetooth adapter. This exact same configuration worked for months just
fine with a Logitech bluetooth mouse. But sadly that mouse was crap
(second one to fail within the warranty period of one of them) so
replaced it with this MS one.
The problem with this MS mouse is that it just goes AWOL and needs to be
delete and re-paired with the machine every few hours. Typically it's
after I have gotten up from the computer and have come back to it. But
I have also had it just happen while using it.
When this happens, the messages log reports messages such as:
Nov 30 12:42:03 pc kernel: [2500032.028982] Bluetooth: Unexpected continuation frame (len 0)
Nov 30 12:42:03 pc kernel: [2500032.115027] Bluetooth: Unexpected continuation frame (len 0)
Any ideas what the problem might be here?
Cheers,
b.
On Wed, 2013-12-04 at 00:12 +0100, Bastien Nocera wrote:
>
> Just how did you pair your mouse?
With mate[gnome]-bluetooth-properties.
Cheers,
b.
On Tue, 2013-12-03 at 16:43 -0500, Brian J. Murrell wrote:
> On Sat, 2013-11-30 at 15:37 -0500, Brian J. Murrell wrote:
> > Hi,
> >
> > I'm using a Microsoft Sculpt Touch Mouse on a Fedora 19 machine
> > (kernel-3.11.9-200.fc19.x86_64 and bluez-4.101-9.fc19.x86_64) with a:
> >
> > Bus 002 Device 019: ID 0a5c:2148 Broadcom Corp. BCM92046DG-CL1ROM Bluetooth 2.1 Adapter
> >
> > bluetooth adapter. This exact same configuration worked for months just
> > fine with a Logitech bluetooth mouse. But sadly that mouse was crap
> > (second one to fail within the warranty period of one of them) so
> > replaced it with this MS one.
> >
> > The problem with this MS mouse is that it just goes AWOL and needs to be
> > delete and re-paired with the machine every few hours. Typically it's
> > after I have gotten up from the computer and have come back to it. But
> > I have also had it just happen while using it.
> >
> > When this happens, the messages log reports messages such as:
> >
> > Nov 30 12:42:03 pc kernel: [2500032.028982] Bluetooth: Unexpected continuation frame (len 0)
> > Nov 30 12:42:03 pc kernel: [2500032.115027] Bluetooth: Unexpected continuation frame (len 0)
> >
> > Any ideas what the problem might be here?
>
> So an interesting development in this is that after a reboot, I am now
> starting to see notification bubbles pop up when the mouse goes AWOL
> that say:
>
> Authorization request from 'Microsoft Sculpt Touch Mouse' with a "Check
> authorization" button it. When I click that I get a dialog popping up
> that says:
>
> Grant access to '<uuid>'
>
> Device 'Microsoft Sculpt Touch Mouse' (<MAC address>) wants access to
> the service '<uuid>'.
>
> With both a Reject and a Grant button as well as an "Always grant
> access" checkbox.
>
> Clicking Grant restores the functionality of the mouse and clearly I
> could click the Always grant access checkbox to have this automatic.
Just how did you pair your mouse?
On Sat, 2013-11-30 at 15:37 -0500, Brian J. Murrell wrote:
> Hi,
>
> I'm using a Microsoft Sculpt Touch Mouse on a Fedora 19 machine
> (kernel-3.11.9-200.fc19.x86_64 and bluez-4.101-9.fc19.x86_64) with a:
>
> Bus 002 Device 019: ID 0a5c:2148 Broadcom Corp. BCM92046DG-CL1ROM Bluetooth 2.1 Adapter
>
> bluetooth adapter. This exact same configuration worked for months just
> fine with a Logitech bluetooth mouse. But sadly that mouse was crap
> (second one to fail within the warranty period of one of them) so
> replaced it with this MS one.
>
> The problem with this MS mouse is that it just goes AWOL and needs to be
> delete and re-paired with the machine every few hours. Typically it's
> after I have gotten up from the computer and have come back to it. But
> I have also had it just happen while using it.
>
> When this happens, the messages log reports messages such as:
>
> Nov 30 12:42:03 pc kernel: [2500032.028982] Bluetooth: Unexpected continuation frame (len 0)
> Nov 30 12:42:03 pc kernel: [2500032.115027] Bluetooth: Unexpected continuation frame (len 0)
>
> Any ideas what the problem might be here?
So an interesting development in this is that after a reboot, I am now
starting to see notification bubbles pop up when the mouse goes AWOL
that say:
Authorization request from 'Microsoft Sculpt Touch Mouse' with a "Check
authorization" button it. When I click that I get a dialog popping up
that says:
Grant access to '<uuid>'
Device 'Microsoft Sculpt Touch Mouse' (<MAC address>) wants access to
the service '<uuid>'.
With both a Reject and a Grant button as well as an "Always grant
access" checkbox.
Clicking Grant restores the functionality of the mouse and clearly I
could click the Always grant access checkbox to have this automatic.
I just wonder what this functionality is. I never had it with my
previous Logitech bluetooth mouse.
Cheers,
b.
On Sun, 2013-12-01 at 23:28 +0100, Bastien Nocera wrote:
>
> Upstream developers don't work on BlueZ 4.x anymore. Any chance for you
> to test using Fedora 20? It uses BlueZ 5.x which has a lot of fixes and
> architectural changes compared to 4.x.
So, assuming I'm supposed to use something like bluetooth-wizard to
start the pairing, that doesn't even see my mouse when I have the mouse
in pairing mode. It does see a headset if I put it into pairing mode
though, so basic bluetooth functionality is at least working. It's just
not seeing my mouse.
Unfortunately though F20 is a bit of a nightmare at the moment for me to
keep it up and running on the workstation where this mouse is having
problems so being able to test will be difficult as it will mean having
to switch back and forth between F19 to get work done and F20 where too
much stuff crashes for it to be usable. It doesn't help that abrt
doesn't seem to be even able to install debuginfos so I can't even
report these crashes. But I digress.
I will try to leave this F20 system up for the next little while in case
there is any debugging you want me to try.
Cheers,
b.
On Sun, 2013-12-01 at 23:38 +0100, Bastien Nocera wrote:
>
> You could try with a LiveCD.
I don't think a LiveCD would be a useful enough work environment for me
to use long enough to see the problem occur. It has happened within
minutes once or twice but typically it can take several hours. This
afternoon has actually been quite good a quite a few hours.
I don't know that there is enough useful stuff for me to do (without a
whole ton of configuring self preferences) in a livecd environment for
me to keep using it for hours. Probably upgrading to F20 is the most
productive way to see.
Cheers,
b.
On Sun, 2013-12-01 at 17:36 -0500, Brian J. Murrell wrote:
> On Sun, 2013-12-01 at 23:28 +0100, Bastien Nocera wrote:
> > Hey Brian,
>
> Hi Bastien,
>
> > Upstream developers don't work on BlueZ 4.x anymore. Any chance for you
> > to test using Fedora 20?
>
> Hrm. Scheduling an upgrade, complete with back-out path here is bit of
> work. I will see what I can do. But for F19 I guess I am just stuck
> with this frustrating behavior? :-(
You could try with a LiveCD.
> > It uses BlueZ 5.x which has a lot of fixes and
> > architectural changes compared to 4.x.
>
> Interesting to know.
>
> Cheers,
> b.
>
On Sun, 2013-12-01 at 23:28 +0100, Bastien Nocera wrote:
> Hey Brian,
Hi Bastien,
> Upstream developers don't work on BlueZ 4.x anymore. Any chance for you
> to test using Fedora 20?
Hrm. Scheduling an upgrade, complete with back-out path here is bit of
work. I will see what I can do. But for F19 I guess I am just stuck
with this frustrating behavior? :-(
> It uses BlueZ 5.x which has a lot of fixes and
> architectural changes compared to 4.x.
Interesting to know.
Cheers,
b.
Hey Brian,
On Sat, 2013-11-30 at 15:37 -0500, Brian J. Murrell wrote:
> Hi,
>
> I'm using a Microsoft Sculpt Touch Mouse on a Fedora 19 machine
> (kernel-3.11.9-200.fc19.x86_64 and bluez-4.101-9.fc19.x86_64) with a:
>
> Bus 002 Device 019: ID 0a5c:2148 Broadcom Corp. BCM92046DG-CL1ROM Bluetooth 2.1 Adapter
>
> bluetooth adapter. This exact same configuration worked for months just
> fine with a Logitech bluetooth mouse. But sadly that mouse was crap
> (second one to fail within the warranty period of one of them) so
> replaced it with this MS one.
>
> The problem with this MS mouse is that it just goes AWOL and needs to be
> delete and re-paired with the machine every few hours. Typically it's
> after I have gotten up from the computer and have come back to it. But
> I have also had it just happen while using it.
>
> When this happens, the messages log reports messages such as:
>
> Nov 30 12:42:03 pc kernel: [2500032.028982] Bluetooth: Unexpected continuation frame (len 0)
> Nov 30 12:42:03 pc kernel: [2500032.115027] Bluetooth: Unexpected continuation frame (len 0)
>
> Any ideas what the problem might be here?
Upstream developers don't work on BlueZ 4.x anymore. Any chance for you
to test using Fedora 20? It uses BlueZ 5.x which has a lot of fixes and
architectural changes compared to 4.x.
Cheers