Bug 1040657 - unable to find my mouse during scan
Summary: unable to find my mouse during scan
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-bluetooth
Version: 20
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-11 20:21 UTC by Brian J. Murrell
Modified: 2015-06-29 13:28 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-29 13:28:50 UTC
Type: Bug


Attachments (Terms of Use)

Description Brian J. Murrell 2013-12-11 20:21:55 UTC
Description of problem:
Trying to scan for and pair my bluetooth mouse fails to discover it during scan

Version-Release number of selected component (if applicable):
gnome-bluetooth-3.10.0-1.fc20.x86_64

How reproducible:
100%

Steps to Reproduce:
1. start bluetooth-wizard
2. put mouse in pairing mode
3. scan using bluetooth-wizard
4. wait
5. and wait more
6. and wait some more
7. give up

Actual results:
Never finds my mouse

Expected results:
Should find my mouse and allow me to pair it

Additional info:
Using bluetoothctl I was able to scan for, and pair my mouse:

$ bluetoothctl 
[NEW] Controller 00:02:72:1E:E0:12 pc.interlinx.bc.ca-0 [default]
[NEW] Device 00:0D:E6:68:B4:6F Samsung WEP850
[NEW] Device 70:F3:95:3E:92:34 brian-laptop
[NEW] Device 7C:1E:52:6E:59:D2 Microsoft Sculpt Touch Mouse
[bluetooth]# agent on
Agent registered
[bluetooth]# power on
Changing power on succeeded
[bluetooth]# scan on
Discovery started
[CHG] Controller 00:02:72:1E:E0:12 Discovering: yes
[CHG] Device 7C:1E:52:6E:59:D2 RSSI: -59
[bluetooth]# scan off
[CHG] Device 7C:1E:52:6E:59:D2 RSSI is nil
Discovery stopped
[CHG] Controller 00:02:72:1E:E0:12 Discovering: no
[bluetooth]# pair 7C:1E:52:6E:59:D2
Attempting to pair with 7C:1E:52:6E:59:D2
[CHG] Device 7C:1E:52:6E:59:D2 Connected: yes
[CHG] Device 7C:1E:52:6E:59:D2 Paired: yes
Pairing successful
[CHG] Device 7C:1E:52:6E:59:D2 Connected: no
[bluetooth]# connect 7C:1E:52:6E:59:D2
Attempting to connect to 7C:1E:52:6E:59:D2
[CHG] Device 7C:1E:52:6E:59:D2 Connected: yes
Connection successful
[CHG] Device 7C:1E:52:6E:59:D2 Modalias: usb:v045Ep077Cd011E
[CHG] Device 7C:1E:52:6E:59:D2 Modalias: usb:v045Ep077Cd011E
[bluetooth]# trust 7C:1E:52:6E:59:D2
Changing 7C:1E:52:6E:59:D2 trust succeeded
[bluetooth]# quit
[DEL] Controller 00:02:72:1E:E0:12 pc.interlinx.bc.ca-0 [default]

Comment 1 Fedora End Of Life 2015-05-29 09:58:10 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Fedora End Of Life 2015-06-29 13:28:50 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.