Invalid joystick identification via LED after connection loss

Bug #1178844 reported by Sergii Bezpalyi on 2013-05-10
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

To reproduce this issue you need two joystics.
Steps to reproduce:
1. Connect both joysticks to system using bluetooth. Each joystick correctly identified by LED on it's back.
2. Take first joystick and walk away from computer, you should wait until led are off.
3. Return to computer and hit the PS button.
4. Joystick succesfully reconnected as js0 but LED on the joystick back shows him as number two.
It's only display issue, both joysticks are working fine, but I can't find which one is the first.

System: Ubuntu 12.04 64bit
sixad was installed from falk repository: qtsixa_1.5.1+git20130130-0~precise2_amd64.deb

sixad log:
sixad-bin[32168]: started
sixad-bin[32168]: sixad started, press the PS button now
sixad-sixaxis[32405]: started
sixad-sixaxis[32405]: Connected 'PLAYSTATION(R)3 Controller (04:98:F3:3C:20:14)' [Battery 05]
sixad-sixaxis[32459]: started
sixad-sixaxis[32459]: Connected 'PLAYSTATION(R)3 Controller (04:98:F3:3B:AB:DE)' [Battery 05]
sixad-sixaxis[32405]: Force disconnect of "04:98:F3:3C:20:14"
Not connected.
sixad-sixaxis[2799]: started
sixad-sixaxis[2799]: Connected 'PLAYSTATION(R)3 Controller (04:98:F3:3C:20:14)' [Battery 05]

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers