Hot answers tagged

3

Because the folder where that file is is not in PATH variable, and by default any command you just type into the prompt will be searched from the list of dirs in the PATH. You can type in git and run it just like that because it's located in some directory that is listed in PATH and yours is not. Use ·/command , give full path like /home/admin/somedir/...


2

This problem exists because Atheros re-used the chip VID and PID. See this bug report As a workaround you can patch the btusb.c module and change it form ath3k to Rome. I've built a DKMS package to fix this issue and uploaded it to my PPA. https://launchpad.net/~hanipouspilot/+archive/ubuntu/bluetooth/+files/btusb-lp1542743-dkms_0.1_all.deb Install this ...


1

Try this: sudo apt-get --reinstall install bluez Updated Answer: Disable and reenable your bluetooth device with the hard switch on your computer (switch or button) Go to 'System Settings' >> 'Bluetooth' and activate 'Show Bluetooth Status in the menu bar'... Set 'Bluetooth ON' in the menu bar and reboot your system...


1

Ensure the following: Jaybird X2 is paired it is marked as trusted (either via bluetoothctl and trust XX:XX:XX:XX (where XX:XX:XX:XX is the MAC address of your Jaybird) or via blueman-manager) it is turned on Press the power button of your Jaybird X2 once. This probably triggers an auto-connect to known devices. So you may need to ensure that other ...


1

If someone else stumbles upon this, I had/have a similar problem. For whatever reason, on my system /usr/lib/bluetooth/bluetoothd is not executable, and thus it obviously fails to start. So, sudo chmod a+x /usr/lib/bluetooth/bluetoothd fixes the problem, at least until the next reboot. Reinstalling bluex fixes it as well - though I have not rebooted ...


1

In my case the issue that you can find here for 15.10 and the provided solution helped me: hciconfig hci0 sspmode 1 hciconfig hci0 down hciconfig hci0 up


1

Do and install Bluetooth control manager blueman sudo apt-get install blueman Problem not in drivers but in controlling bluetooth.


1

I'm on Ubuntu GNOME 16.04 and I've found a solution that works perfectly here: https://wiki.debian.org/BluetoothUser/a2dp On ubuntu user is gdm and not Debian-gdm, here are the exact instructions: In order to prevent GDM from capturing the A2DP sink on session start, edit /var/lib/gdm3/.config/pulse/client.conf (or create it, if it doesn't exist):...



Only top voted, non community-wiki answers of a minimum length are eligible