I am assuming you are using blueman provided GUI bluetooth manager? Try to open it and have a terminal open by it’s side and launch
udevadm monitor
then try to connect to your controller. If that doesn’t give sufficient logs,
journalctl --grep bluetooth -b
should. You can also go with command line method of connecting with your bluetooth device to see if that has any difference,
- Ensure bluetooth is on with
rfkill list
it should show something like this,
1: ideapad_bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
9: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
If bluetooth is not blocked like above then
bluetoothctl
This will change your command prompt. You can type
help
here to list all available commands.
Then try to do as needed to connect with your device it might take a little messing around here but it should give you substantially more logs than udev monitor
.
once done just type
exit
to exit.