New answers tagged

0

Have you tried this: sudo dpkg --configure -a and it might work fine this way.


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 ...


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 ...


-2

You could try to reinstall bluetooth: sudo apt-get purge bluetooth sudo apt-get install bluetooth That worked for me.


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):...


1

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


0

Probably not the most appreciated way, but it might be the most pragmatic. I.e. this worked for me: Download one of the windows VM's for testing MSIE. Run it in Virtualbox with the Extension pack enabled for USB 2.0 support. Before you start the VM, add yourself to the vboxusers group and login again. After you logged in, add all USB devices to the VM. In ...


0

You can install the file that is failing on line [ 3.352116] bluetooth hci0: Direct firmware load for brcm/BCM-0a5c-6410.hcd failed with error -2 [ 3.352118] Bluetooth: hci0: BCM: Patch brcm/BCM-0a5c-6410.hcd not found Download from https://www.dropbox.com/s/8goc4omhnzxij93/BCM-0a5c-6410.hcd?dl=0 the missing firmware and create a file like /lib/...


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/...


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 ...


0

alsa is really not suited to hotplugging , pulseaudio is far better suited to this mode of operation. My TV supports sending to bluetooth audio so i use that , with my old tv i used a dedicated bluetooth sender that i got with some Plantronic backbeat 903+ headphones. Bluetooth generally has a noticable latency so you will need to delay the video ...


0

As far as I know, the cdc-acm is for serial<->usb adapters (includes usb modems or any other device that uses USB as a bridge for a TTL or RS232 serial port). For a bluetooth dongle on ubuntu 16.04 you are probably looking for "bluetoothctl".


0

There is a bug report about it; https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1298552 As you can see from the report status, bug has been expired, importance is low and not assigned to anyone. I highly believe that the bug will not be resolved if no one reports a crash about it. Workaround: You may try disabling bluetooth service by writing a ...


0

The fix is to open terminal and then enter bluetoothctl This opens the bluetooth control in terminal, then enter the command to power the bluetooth device with power on And finally turn scanning on scan on If more commands are needed type help


0

On viewing uname -a; lsusb; dmesg | egrep -i 'blue|firm' and lshw on the terminal, there is no mention of Bluetooth capabilities, so it would appear that the Compaq Presario C504EA is one of the models that wasn't Bluetooth enabled.


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...


0

I have the same issue, here is the result of lspci -nnk | grep -iA2 net; lsusb; lsmod | grep blue; rfkill list all; dmesg | egrep -i 'blue|firm' ; 01:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 09) Subsystem: Samsung Electronics Co Ltd RTL8111/8168/8411 PCI ...


0

Open a terminal. Cut and paste the following commands (all together) and hit enter: pactl unload-module module-bluetooth-discover pactl load-module module-bluetooth-discover sudo systemctl restart bluetooth You should be prompted for your password. Enter that. Exit Terminal. Should be up and running again. I think this is some bug in bluetooth. ...


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


0

As mentioned by Pilot6 in the comment above, this device uses the QCA_ROME driver. However, this precise bluetooth device is not currently supported in the kernel sources. I'm on a Acer Aspire VN7-791 (quite similar model), with the same bluetooth device. Output of lsusb: Bus 003 Device 007: ID 0489:e092 Foxconn / Hon Hai On my laptop, this device is ...


0

Like Jeremy31 said. Search in your Downloads Folder. Try navigating to /home/"user"/Downloads or /home/"user"/Public/ Where "user" is your Ubuntu Username, without the quotes (").


0

I added it to startup gksudo gedit /etc/rc.local rfkill unblock bluetooth And now it's working. Hope it keeps that way


3

Thats a perfect output, to explain it a bit I'll take it step by step: SpiRegistry daemon is running with well-known name - org.ally.atspi.Registry This one seems to be a system daemon, not really sure what he does. Starting User manager for UID 1000 This is the UID of your users group. UID 108 This is the syslogs group UID. CRON [3076]: pam_unix (cron:...


1

I solved this problem by installing blueman In blueman right click on the headphone and select 'audio profile' -> 'High Fidelity Playback' There may be better profiles but this works for me. I ran blueman from the terminal with sudo apt-get install blueman and then ran blueman and locked it to launcher.


0

Use systemctl to start the Bluetooth service systemctl start bluetooth


2

It is a known bug. Try rmmod btusb ; modprobe btusb. I have had to do it up to four times. I have seen this with my Lenovo P50 with Intel 8260 wifi/bluetooth. Sometimes the bluetooth firmware doesn't load correctly at boot. Other times it just doesn't work.



Top 50 recent answers are included