Bug 10632 - bluetooth mice that go to sleep wont auto connect, when woken
Summary: bluetooth mice that go to sleep wont auto connect, when woken
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 3
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL: https://forums.mageia.org/en/viewtopi...
Whiteboard:
Keywords: PATCH, Triaged
Depends on:
Blocks:
 
Reported: 2013-06-27 11:54 CEST by peter winterflood
Modified: 2014-01-16 11:35 CET (History)
1 user (show)

See Also:
Source RPM: bluez-4.99
CVE:
Status comment:


Attachments

Description peter winterflood 2013-06-27 11:54:05 CEST
Description of problem:


bluez-4.99-3.mga2 and possibly newer releases, not had a chance to eval newer.


How reproducible:


Steps to Reproduce:
1.connect bluetooth mouse
2.leave for half an hour or so, so it sleeps
3.move it, it wont reconnect.
4. use the bluetooth reconnect menu
5. still wont reconnect.
6. make the mouse visible if its gone into hidden mode 
7. still wont connect.
8. remove mouse from list of devices, make unhidden , scan for new devices, connect, and its OK. go back to 2.

this has been well described in the following ubuntu forum and bugzilla in 2005, symptoms are almost identical.

https://bugs.launchpad.net/ubuntu/+source/kdebluetooth/+bug/175743

Reproducible: 

Steps to Reproduce:
Comment 1 Samuel Verschelde 2013-08-28 16:13:28 CEST
The ubuntu bug has a patch.

Keywords: (none) => PATCH, Triaged
CC: (none) => stormi
Assignee: bugsquad => dmorganec
Source RPM: believed to be bluez-4.99 => bluez-4.99

D Morgan 2013-09-18 00:08:28 CEST

Assignee: dmorganec => bugsquad

Comment 2 Manuel Hiebel 2013-10-22 12:11:48 CEST
This message is a reminder that Mageia 2 is nearing its end of life.
Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'.

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 Mageia version prior to Mageia 2's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 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 Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

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 Mageia release includes newer upstream software that fixes bugs or makes them obsolete.

-- 
The Mageia Bugsquad
Comment 3 Manuel Hiebel 2013-11-23 16:14:58 CET
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 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 Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

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

--
The Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD

Comment 4 peter winterflood 2014-01-15 12:25:45 CET
upgraded to mageia 3 as of yesterday, with all updates.

still has this problem.

Version: 2 => 3

peter winterflood 2014-01-15 12:25:59 CET

Status: RESOLVED => REOPENED
Resolution: OLD => (none)

Comment 5 peter winterflood 2014-01-16 11:34:32 CET
OK, ill backtrack on that 

out of the box the problem still appears to be there, an additional step 
is required at install time to address this.

for kde blues users 

edit the file 

/usr/share/apps/bluedevilwizard/pin-code-database.xml

and add

in my case 

,device oui="&C:1E:52" type="mouse" name="Microsoft Wedge Touch Mouse" pin="0000" />

to the ,devices. section

now go and discover your mouse and get it to join.

now it will work the second you turn on the mouse without any further rejoining/or reconnecting.

regards peter
Comment 6 peter winterflood 2014-01-16 11:35:59 CET
resolving, oh typo above that should have been

<device oui="7C:1E:52" type="mouse" name="Microsoft Wedge Touch Mouse" pin="0000" />

Status: REOPENED => RESOLVED
Resolution: (none) => FIXED


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