Red Hat Bugzilla – Bug 663345
bluetooth mouse won't reconnect after suspend/resume
Last modified: 2012-08-16 13:28:36 EDT
Description of problem:
After using the Gnome bluetooth applet to connect a bluetooth mouse, I then go through a suspend resume cycle. The mouse is left unconnected and requires that I both push the "connect" button on the mouse and use the applet to reconnect, thus requiring a mouse to connect a mouse.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Successfully pair the mouse
2. Suspend the laptop, then resume.
The mouse will not work without using the applet to reconnect.
Mouse should automatically reconnect and function.
The problem is not limited to this particular mouse as I've tried another bluetooth mouse. It is also not due to the laptop hardware as I can dual boot into Windows XP where the mouse does reconnect after a suspend/resume cycle.
Laptop is Thinkpad T43
This message is a notice that Fedora 14 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 14. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.
(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 14 reached 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 to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.
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.
The process we are following is described here: