Bug 1033038 - Bluetooth mouse is recognized, but won't connect
Bluetooth mouse is recognized, but won't connect
Product: Fedora
Classification: Fedora
Component: bluez (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Don Zickus
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2013-11-21 08:10 EST by Horst H. von Brand
Modified: 2015-06-29 09:05 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-06-29 09:05:48 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Output from hcidump while turning on the mouse (2.99 KB, application/octet-stream)
2013-11-21 08:17 EST, Horst H. von Brand
no flags Details

  None (edit)
Description Horst H. von Brand 2013-11-21 08:10:49 EST
Description of problem:
My Targus Soft-Touch Bluetooth mouse can be set up fine in gnome, but the "Connect" button is grayed out. The mouse just won't connect, even if I try to force it (turn it off and on; LEDs blink).

It used to work before (bluez-5.10 or so).

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Start Gnome; no mouse recognized (even when turning off and restarting the mouse)
2. Go to Settings->Bluetooth; mouse shows up, but connecting can't be selected.

Actual results:
No mouse connection possible

Expected results:
Be able to use the mouse...

Additional info:
Comment 1 Horst H. von Brand 2013-11-21 08:17:56 EST
Created attachment 827179 [details]
Output from hcidump while turning on the mouse

It says the connection was terminated due to missing authorization/security block (?!)
Comment 2 Horst H. von Brand 2013-11-21 08:49:25 EST
Argh... went to the bluetooth manager (as systemctl status bluetooth told me the device was "unknown"), deleted the mouse and added it again.

Now it works.

Stay tuned...
Comment 3 Fedora End Of Life 2015-05-29 05:49:20 EDT
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 4 Fedora End Of Life 2015-06-29 09:05:48 EDT
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

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.