Bug 1674305 - Sixaxis controller refuses to connect
Summary: Sixaxis controller refuses to connect
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: bluez
Version: 29
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Don Zickus
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-02-10 22:55 UTC by Victor Oliveira
Modified: 2019-06-18 18:13 UTC (History)
5 users (show)

Fixed In Version: bluez-5.50-8.fc30
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-18 18:13:35 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Victor Oliveira 2019-02-10 22:55:47 UTC
Description of problem:
When i try to connect Sixaxis controller on Fedora over Bluetooth, it keeps connecting and dropping.

Version-Release number of selected component (if applicable):
bluez-5.50-3.fc29.rpm

How reproducible:
Always

Steps to Reproduce:
1. Open gnome-control-center on bluetooth configuration
2. Connect the controller over USB
3. Confirm the controller connection
4. Remove the USB cable from the controller
5. The bluetooth icon keeps looping into active device and no device connected

Actual results:
Not working controller over bluetooth

Expected results:
Controller connected via Bluetooth

Additional info:
The log of bluetooth unit says:
fev 10 19:29:05 N460 systemd[1]: Started Bluetooth service.
fev 10 19:29:05 N460 bluetoothd[720]: Starting SDP server
fev 10 19:29:07 N460 bluetoothd[720]: Bluetooth management interface 1.14 initialized
fev 10 19:31:15 N460 bluetoothd[720]: Endpoint registered: sender=:1.215 path=/MediaEndpoint/A2DPSource
fev 10 19:31:15 N460 bluetoothd[720]: Endpoint registered: sender=:1.215 path=/MediaEndpoint/A2DPSink
fev 10 20:13:37 N460 bluetoothd[720]: sixaxis: compatible device connected: Sony PLAYSTATION(R)3 Controller (054C:0268 /sys/devices/pci0000:00/0000:0>
fev 10 20:13:37 N460 bluetoothd[720]: sixaxis: setting up new device
fev 10 20:13:52 N460 bluetoothd[720]: getpeername: Transport endpoint is not connected (107)
fev 10 20:13:53 N460 bluetoothd[720]: getpeername: Transport endpoint is not connected (107)
fev 10 20:13:54 N460 bluetoothd[720]: getpeername: Transport endpoint is not connected (107)
fev 10 20:13:54 N460 bluetoothd[720]: getpeername: Transport endpoint is not connected (107)
fev 10 20:13:56 N460 bluetoothd[720]: getpeername: Transport endpoint is not connected (107)
fev 10 20:13:57 N460 bluetoothd[720]: getpeername: Transport endpoint is not connected (107)
fev 10 20:13:58 N460 bluetoothd[720]: getpeername: Transport endpoint is not connected (107)
fev 10 20:13:59 N460 bluetoothd[720]: sixaxis: compatible device connected: Sony PLAYSTATION(R)3 Controller (054C:0268 /sys/devices/pci0000:00/0000:0>
fev 10 20:13:59 N460 bluetoothd[720]: sixaxis: setting up new device
fev 10 20:14:00 N460 bluetoothd[720]: getpeername: Transport endpoint is not connected (107)
fev 10 20:14:17 N460 bluetoothd[720]: getpeername: Transport endpoint is not connected (107)
fev 10 20:14:18 N460 bluetoothd[720]: getpeername: Transport endpoint is not connected (107)

Comment 1 Bastien Nocera 2019-06-07 08:17:43 UTC
Please make sure you use kernel 5.1.5, and use this bluez update and let us know whether it fixes your problem:
https://bodhi.fedoraproject.org/updates/FEDORA-2019-5101717387

Comment 2 Victor Oliveira 2019-06-10 23:18:40 UTC
I've updated my system to Fedora 30 and the error is gone.
Thanks!

Comment 3 Fedora Update System 2019-06-11 09:58:12 UTC
FEDORA-2019-5101717387 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-5101717387

Comment 4 Fedora Update System 2019-06-18 18:13:35 UTC
bluez-5.50-8.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.


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