Unable to pair bluetooth mouse (11.10 regression)

Bug #896769 reported by smlx
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bluez (Debian)
Confirmed
Unknown
bluez (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu
$ lsb_release -rd
Description: Ubuntu 11.10
Release: 11.10

2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center
$ apt-cache policy bluez
bluez:
  Installed: 4.96-0ubuntu4
  Candidate: 4.96-0ubuntu4
  Version table:
 *** 4.96-0ubuntu4 0
        500 http://mirror.internode.on.net/pub/ubuntu/ubuntu/ oneiric-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     4.96-0ubuntu3 0
        500 http://mirror.internode.on.net/pub/ubuntu/ubuntu/ oneiric/main amd64 Packages

3) What you expected to happen
When I start pairing mode on my bluetooth mouse, Bluedevil pops up a notification. When I click trust and authorise, the mouse should connect to bluetoothd as it did in 11.04.

4) What happened instead
Instead an error appears in syslog:

27/11/11 11:25:42 hpeb bluetoothd[1287] Refusing input device connect: No such file or directory (2)
27/11/11 11:25:52 hpeb bluetoothd[1287] Agent replied with an error: org.bluez.Error.Canceled, Authorization canceled
27/11/11 11:25:52 hpeb bluetoothd[1287] Access denied: Authorization canceled
27/11/11 11:30:09 hpeb bluetoothd[1287] Refusing input device connect: No such file or directory (2)

Note that I also had this issue in Debian Sid/Wheezy, so it appears to be an issue in bluez upstream:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642104

Also the bug appears to have been encountered by at least one other person using 11.10:
http://ubuntuforums.org/showthread.php?t=1840650

Changed in bluez (Debian):
status: Unknown → Confirmed
Phil. V (philip.v)
tags: added: regression-release
Revision history for this message
smlx (sml) wrote :

Chalk one up for user stupidity. I have fixed this issue by correctly pairing the mouse, rather than using the incorrect pairing procedure as I had done before.

Please close this report as it is not a bug.

Revision history for this message
Phil. V (philip.v) wrote :

Thanks for updating us, I'll mark this as invalid on the Ubuntu side of things.

Changed in bluez (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.