apple magicmouse was working until updates

[ltodd2]

Afternoon

I have been using an apple magicmouse on my system since I built it about 2 weeks ago and its been working fine. My laptop just told me there are updates so I clicked install. A few mins later my system hung so had to power it of. Once it restarted the mouse was not working. Under bluetooth it showed as connected but no buttons or movement. Removed and re added and still the same.
I dug out another mouse and paired it and it worked until I turned it off and back on and now it does the same.
Below is a few lines from /var/log/messages. Any one any ideas?


This is from adding the mouse:
Aug 4 13:58:59 zeus bluetoothd[825]: Discovery session 0x7f518628acb0 with :1.109 activated
Aug 4 13:58:59 zeus bluetoothd[825]: bluetoothd[825]: Discovery session 0x7f518628acb0 with :1.109 activated
Aug 4 13:59:30 zeus bluetoothd[825]: Stopping discovery
Aug 4 13:59:30 zeus bluetoothd[825]: bluetoothd[825]: Stopping discovery
Aug 4 13:59:38 zeus bluetoothd[825]: Stopping discovery
Aug 4 13:59:38 zeus bluetoothd[825]: bluetoothd[825]: Stopping discovery
Aug 4 13:59:43 zeus kernel: [ 1918.808191] input: Apple Magic Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6/2-1.6:1.0/bluetooth/hci0/hci0:12/input27
Aug 4 13:59:43 zeus kernel: [ 1918.808336] magicmouse 0005:05AC:030D.000C: input,hidraw1: BLUETOOTH HID v3.06 Mouse [Apple Magic Mouse] on C0:F8:DA:E5:7D:BF
Aug 4 13:59:43 zeus kernel: [ 1919.029509] magicmouse 0005:05AC:030D.000C: unable to request touch data (-5)
Aug 4 13:59:43 zeus kernel: [ 1919.062710] magicmouse: probe of 0005:05AC:030D.000C failed with error -5
Aug 4 13:59:43 zeus bluetoothd[825]: Stopping discovery
Aug 4 13:59:43 zeus bluetoothd[825]: bluetoothd[825]: Stopping discovery
Aug 4 13:59:43 zeus bluetoothd[825]: Inquiry Failed with status 0x12
Aug 4 13:59:43 zeus bluetoothd[825]: bluetoothd[825]: Inquiry Failed with status 0x12


And this is from disconnecting and re connecting

Aug 4 14:01:19 zeus kernel: [ 2014.955774] input: Apple Magic Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6/2-1.6:1.0/bluetooth/hci0/hci0:11/input28
Aug 4 14:01:19 zeus kernel: [ 2014.956164] magicmouse 0005:05AC:030D.000D: input,hidraw1: BLUETOOTH HID v3.06 Mouse [Apple Magic Mouse] on C0:F8:DA:E5:7D:BF
Aug 4 14:01:19 zeus kernel: [ 2014.961125] magicmouse 0005:05AC:030D.000D: unable to request touch data (-5)
Aug 4 14:01:19 zeus kernel: [ 2014.972440] magicmouse: probe of 0005:05AC:030D.000D failed with error -5


Thanks

Lee

[bob]

moved to Mac

[ltodd2]

Bob

Dont know if it makes a difference but it is a Dell laptop that im using the mouse on

Lee

[bob]

Yes, it's a toss-up on that one! Since it's an Apple mouse, the mac folks are likely to be more help, so let's leave it here for now. PM me if you don't get any solutions by tomorrow and I'll put it into General Support for another try.

[ltodd2]

From looking into this more I think it stopped working when the kernel changed to 2.6.40-4. This seems to have broken a few things. I have changed back to kernel 2.6.38-35 and it still will not work any more. Any ideas anyone?

[hockeyhead019]

help would be great on this. I just set my magic mouse up and it says I'm connected and all but there isn't any reaction from the mouse.

I'm on a Dell Inspiron 1545 with a iogear usb bluetooth adapter (which was recognized no problem by the system)

[ltodd2]

anyone any ideas on this? still not managed to get it working agian

[glezos]

Confirming this on an x220 with an Apple Trackpad.

[chrismurphy]

With F16, when pairing, it fails to pair. It sees the mouse, sees that it is a mouse, yet briefly wants a pairing code, and then that message goes away. The result is the mouse is an added device but it's not paired.

[ltodd2]

I have just tried again and this is what I now get. Im now using kernel 2.6.40.6-0.fc15.x86_64

Oct 18 08:02:52 zeus bluetoothd[901]: No agent available for request type 0
Oct 18 08:02:52 zeus bluetoothd[901]: PIN code negative reply: Operation not permitted
Oct 18 08:02:52 zeus bluetoothd[901]: bluetoothd[901]: No agent available for request type 0
Oct 18 08:02:52 zeus bluetoothd[901]: bluetoothd[901]: PIN code negative reply: Operation not permitted
Oct 18 08:02:56 zeus bluetoothd[901]: No agent available for request type 0
Oct 18 08:02:56 zeus bluetoothd[901]: PIN code negative reply: Operation not permitted
Oct 18 08:02:56 zeus bluetoothd[901]: bluetoothd[901]: No agent available for request type 0
Oct 18 08:02:56 zeus bluetoothd[901]: bluetoothd[901]: PIN code negative reply: Operation not permitted
Oct 18 08:03:09 zeus bluetoothd[901]: Discovery session 0x7fee85c0e810 with :1.495 activated
Oct 18 08:03:09 zeus bluetoothd[901]: bluetoothd[901]: Discovery session 0x7fee85c0e810 with :1.495 activated
Oct 18 08:03:28 zeus bluetoothd[901]: Stopping discovery
Oct 18 08:03:28 zeus bluetoothd[901]: bluetoothd[901]: Stopping discovery
Oct 18 08:03:31 zeus bluetoothd[901]: No agent available for request type 0
Oct 18 08:03:31 zeus bluetoothd[901]: PIN code negative reply: Operation not permitted
Oct 18 08:03:31 zeus bluetoothd[901]: bluetoothd[901]: No agent available for request type 0
Oct 18 08:03:31 zeus bluetoothd[901]: bluetoothd[901]: PIN code negative reply: Operation not permitted
Oct 18 08:03:31 zeus bluetoothd[901]: Connection refused (111)
Oct 18 08:03:31 zeus bluetoothd[901]: bluetoothd[901]: Connection refused (111)
Oct 18 08:03:31 zeus bluetoothd[901]: Permission denied (13)
Oct 18 08:03:31 zeus bluetoothd[901]: bluetoothd[901]: Permission denied (13)
Oct 18 08:03:35 zeus bluetoothd[901]: No agent available for request type 0
Oct 18 08:03:35 zeus bluetoothd[901]: PIN code negative reply: Operation not permitted
Oct 18 08:03:35 zeus bluetoothd[901]: bluetoothd[901]: No agent available for request type 0
Oct 18 08:03:35 zeus bluetoothd[901]: bluetoothd[901]: PIN code negative reply: Operation not permitted
Oct 18 08:03:35 zeus bluetoothd[901]: Connection refused (111)
Oct 18 08:03:35 zeus bluetoothd[901]: bluetoothd[901]: Connection refused (111)
Oct 18 08:03:44 zeus bluetoothd[901]: No agent available for request type 0
Oct 18 08:03:44 zeus bluetoothd[901]: PIN code negative reply: Operation not permitted
Oct 18 08:03:44 zeus bluetoothd[901]: bluetoothd[901]: No agent available for request type 0
Oct 18 08:03:44 zeus bluetoothd[901]: bluetoothd[901]: PIN code negative reply: Operation not permitted
Oct 18 08:03:49 zeus bluetoothd[901]: No agent available for request type 0
Oct 18 08:03:49 zeus bluetoothd[901]: PIN code negative reply: Operation not permitted
Oct 18 08:03:49 zeus bluetoothd[901]: bluetoothd[901]: No agent available for request type 0
Oct 18 08:03:49 zeus bluetoothd[901]: bluetoothd[901]: PIN code negative reply: Operation not permitted

[bob]

Well now! You're up to F16, which means that I can move the thread once again and hopefully get some fresh eyes looking at the problem. Moved to F16 Development.

[YeOK]

With F16, when pairing, it fails to pair. It sees the mouse, sees that it is a mouse, yet briefly wants a pairing code, and then that message goes away. The result is the mouse is an added device but it's not paired.

My Magic mouse works just fine, you need to enter '0000' when it asks for the pairing code.

I started a bug a while ago, it got fixed for me but i still get emails about the bug number and it has broken a few times since. I think it should be working fine again on Fedora 15.

https://bugzilla.redhat.com/show_bug.cgi?id=714381

[ltodd2]

YeOK

I dont get prompted for any code. Have tried setting it to use 0000 but just get what I posted today. Im not sure if it prompted when I first used it and it worked.

[chrismurphy]

3.1.0-0.rc6.git0.3.fc16.x86_64 and 3.1.0-0.rc9.git0.0.fc16.x86_64 I get in messages:

Oct 18 16:10:24 localhost bluetoothd[915]: Discovery session 0x7f4b11322970 with :1.89 activated
Oct 18 16:10:24 localhost bluetoothd[915]: bluetoothd[915]: Discovery session 0x7f4b11322970 with :1.89 activated
Oct 18 16:10:50 localhost bluetoothd[915]: Stopping discovery
Oct 18 16:10:50 localhost bluetoothd[915]: bluetoothd[915]: Stopping discovery
Oct 18 16:11:31 localhost bluetoothd[915]: Connection refused (111)
Oct 18 16:11:31 localhost bluetoothd[915]: bluetoothd[915]: Connection refused (111)

I'm not really getting much info. I wondered if maybe it was still expecting to be paired with another computer running Mac OS so I reconnect to the mouse, went into Bluetooth prefs, found the mouse and deleted it. Then I tried to repair on linux and got:

Oct 18 16:22:37 localhost bluetoothd[915]: Discovery session 0x7f4b11336690 with :1.93 activated
Oct 18 16:22:37 localhost bluetoothd[915]: bluetoothd[915]: Discovery session 0x7f4b11336690 with :1.93 activated
Oct 18 16:24:17 localhost bluetoothd[915]: Software caused connection abort (103)
Oct 18 16:24:17 localhost bluetoothd[915]: bluetoothd[915]: Software caused connection abort (103)

At the same time I get a crash notification, crash in gnome-control-center-3.1.91-1.fc16 and the automatic bug reporting tool says the backtrace is unusable.

[YeOK]

Hmm...

Not sure I can really help, I had issues when I first bought the mouse with pairing. I had tried the auto pair option back on Fedora 14 or 15 (I don't remember). Since then it has worked perfectly, I have paired it since without issue. All I can suggest is to delete the entry under fedora, turn the mouse off, wait 30 seconds, then turn the mouse back on. The green led should flash. Try pair it again. You do have to add '0000', it should popup and ask, make sure notifications are switched on for your user.

Another problem could possibly be the bluetooth adapter, have you tried pairing anything else to make sure it works ?

[chrismurphy]

Notifications are on, but I do not get a popup asking me to add anything. I do get a pop-up at the very bottom of the screen which simply informs "Bluetooth Pairing Request for 'chris's mouse'" for about 5 seconds then goes away on its own.

Ahhhh...OK I think we have a HIG failure here. The pop up is actually much bigger, but is not revealed by default. You have to move down to it, before it vanishes, to get it to reveal. Once it fully reveals there is a way to type in 0000 and the pairing works.

Further fail is that in the Bluetooth Setup New Device, there is a "PIN Options" which defaults to auto but can be changed to 0000. Even that fails to pair properly. One has to snag the notification and manually enter in 0000.

But now it works, although it's way way way too fast and sensitive despite the Pointer Speed settings both all the way to the left (Slow and Low). Very difficult to use. Hmmmm.....

---------- Post added at 04:07 PM ---------- Previous post was at 03:57 PM ----------

Connection defaults to Off on reboot....not good!

[YeOK]

Yeah about the speed, it just takes some getting used too. My mouse has to be woken up on every boot, it shuts down to save power. You lift it up and click the button, that works best for me.

I don't remember having an issue with Bluetooth not starting on every boot. You should check this link,

http://www.sohailriaz.com/how-to-fix-bluetooth-in-fedora-15/

I do forget the things I've fixed in fedora over time. Preupgrade tool has spoiled me....

[AdamW]

that sounds like some kind of quirk with the Apple mouse, to me. I set up a bog standard Bluetooth mouse on my laptop yesterday and it just worked perfectly: pairs without any PIN nonsense, and it works on every boot and on resume from suspend and so on with no manual intervention needed (just have to move it around a bit and wait for it to wake up).

[YeOK]

that sounds like some kind of quirk with the Apple mouse, to me. I set up a bog standard Bluetooth mouse on my laptop yesterday and it just worked perfectly: pairs without any PIN nonsense, and it works on every boot and on resume from suspend and so on with no manual intervention needed (just have to move it around a bit and wait for it to wake up).

Yeah, pairing does let it down. One you know you have to type '0000' its not much of an issue. I picked the apple mouse for the touch interface, my parrots pulled the middle mouse button apart on my last mouse. They can't do any damage to this one, fingers crossed.