Linux Mint Forums

Posted: **Thu Oct 17, 2019 2:55 am**

Dear All,

I am running a Linux Mint 18.3 Sylvia with Cinnamon. I have blueman running for bluetooth.
I bought Bose HP 700 headphones and managed to add and connect to it, but it doesn't show up in the list of sound devices i.e. I cannot use them.

I have had bluetooth issues before, read a few posts about it (resulted in installing blueman) and cannot figure it out.

Can anybody please help?

Thank you and kind regards,
Peter

Posted: **Thu Oct 17, 2019 7:22 am**

Hi kaszasp.

What output do you get when you run pactl list short | grep blue in the terminal?

Posted: **Sat Oct 19, 2019 9:40 am**

Hi MrEen

I get the following output:

Code: Select all

7	module-bluetooth-policy		
8	module-bluetooth-discover		
9	module-bluez5-discover

Kind regards,
Peter

Posted: **Sat Oct 19, 2019 11:51 am**

The output is good. Maybe you accidentally connected them in the wrong mode? Try deleting them in the Bluetooth settings and connecting again, making sure to use an audio setting. Or click on the Bluetooth icon and select Devices then right click on the device name and then click on Headset (assuming Headset is available) and look in your Sound Settings to see if the device has appeared.

Posted: **Sat Oct 19, 2019 1:59 pm**

Hi MrEen,

Thank you for your reply.
I have tried all of your suggestions even before posting my original post. (I looked around in other BT-related topics a little bit.) Still nothing... The headset in itself is capable of connecting to other (even multiple) devices at the same time and is working properly.

Any other ideas?

Thank you for your help,
Peter

Posted: **Sat Oct 19, 2019 2:00 pm**

Well, let's make certain pulseaudio is not seeing it at all. While the headset is connected run pacmd list-cards in the terminal and paste the output here.

Posted: **Sat Oct 19, 2019 5:07 pm**

I can't even connect anymore. I always get the "device added successfully but failed to connect" error message.

For what it's worth, here is the output of the command:

Code: Select all

1 card(s) available.
    index: 0
	name: <alsa_card.pci-0000_00_1f.3>
	driver: <module-alsa-card.c>
	owner module: 6
	properties:
		alsa.card = "0"
		alsa.card_name = "HDA Intel PCH"
		alsa.long_card_name = "HDA Intel PCH at 0xb2328000 irq 132"
		alsa.driver_name = "snd_hda_intel"
		device.bus_path = "pci-0000:00:1f.3"
		sysfs.path = "/devices/pci0000:00/0000:00:1f.3/sound/card0"
		device.bus = "pci"
		device.vendor.id = "8086"
		device.vendor.name = "Intel Corporation"
		device.product.id = "9d71"
		device.form_factor = "internal"
		device.string = "0"
		device.description = "Built-in Audio"
		module-udev-detect.discovered = "1"
		device.icon_name = "audio-card-pci"
	profiles:
		input:analog-stereo: Analog Stereo Input (priority 60, available: unknown)
		output:analog-stereo: Analog Stereo Output (priority 6000, available: unknown)
		output:analog-stereo+input:analog-stereo: Analog Stereo Duplex (priority 6060, available: unknown)
		output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5400, available: unknown)
		output:hdmi-stereo+input:analog-stereo: Digital Stereo (HDMI) Output + Analog Stereo Input (priority 5460, available: unknown)
		output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output (priority 5200, available: unknown)
		output:hdmi-stereo-extra1+input:analog-stereo: Digital Stereo (HDMI 2) Output + Analog Stereo Input (priority 5260, available: unknown)
		output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) Output (priority 100, available: unknown)
		output:hdmi-surround-extra1+input:analog-stereo: Digital Surround 5.1 (HDMI 2) Output + Analog Stereo Input (priority 160, available: unknown)
		output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) Output (priority 100, available: unknown)
		output:hdmi-surround71-extra1+input:analog-stereo: Digital Surround 7.1 (HDMI 2) Output + Analog Stereo Input (priority 160, available: unknown)
		output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output (priority 5200, available: unknown)
		output:hdmi-stereo-extra2+input:analog-stereo: Digital Stereo (HDMI 3) Output + Analog Stereo Input (priority 5260, available: unknown)
		output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) Output (priority 100, available: unknown)
		output:hdmi-surround-extra2+input:analog-stereo: Digital Surround 5.1 (HDMI 3) Output + Analog Stereo Input (priority 160, available: unknown)
		output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) Output (priority 100, available: unknown)
		output:hdmi-surround71-extra2+input:analog-stereo: Digital Surround 7.1 (HDMI 3) Output + Analog Stereo Input (priority 160, available: unknown)
		off: Off (priority 0, available: unknown)
	active profile: <output:hdmi-stereo+input:analog-stereo>
	sinks:
		alsa_output.pci-0000_00_1f.3.hdmi-stereo/#19: Built-in Audio Digital Stereo (HDMI)
	sources:
		alsa_input.pci-0000_00_1f.3.analog-stereo/#1: Built-in Audio Analog Stereo
		alsa_output.pci-0000_00_1f.3.hdmi-stereo.monitor/#20: Monitor of Built-in Audio Digital Stereo (HDMI)
	ports:
		analog-input-internal-mic: Internal Microphone (priority 8900, latency offset 0 usec, available: unknown)
			properties:
				device.icon_name = "audio-input-microphone"
		analog-input-mic: Microphone (priority 8700, latency offset 0 usec, available: no)
			properties:
				device.icon_name = "audio-input-microphone"
		analog-output-speaker: Speakers (priority 10000, latency offset 0 usec, available: unknown)
			properties:
				device.icon_name = "audio-speakers"
		analog-output-headphones: Headphones (priority 9000, latency offset 0 usec, available: no)
			properties:
				device.icon_name = "audio-headphones"
		hdmi-output-0: HDMI / DisplayPort (priority 5900, latency offset 0 usec, available: yes)
			properties:
				device.icon_name = "video-display"
				device.product.name = "DELL S2419H"
		hdmi-output-1: HDMI / DisplayPort 2 (priority 5800, latency offset 0 usec, available: no)
			properties:
				device.icon_name = "video-display"
		hdmi-output-2: HDMI / DisplayPort 3 (priority 5700, latency offset 0 usec, available: no)
			properties:
				device.icon_name = "video-display"

Posted: **Sat Oct 19, 2019 5:16 pm**

Not sure why that's happening. Have you tried a reboot? There should be a second sink if pulseaudio does "see" the connection when you run the pacmd command.

EDIT: The headphones might need to be charged again.

Posted: **Sun Oct 20, 2019 11:54 am**

I have rebooted, then deleted the previously added Bose HP 700 (that I could not connect to).
I added the Bose HP 700 again as a headset, chose option with Pairing.
I managed to set it up and get connected BUT immediately after that I got this error message in a window:

Connection to BlueZ failed

Bluez daemon is not running, blueman-manager cannot continue.
This probably means that there were no Bluetooth adapters detected or Bluetooth daemon was not started.

and it obviously is not listed under the Sound panel of Settings.

Interestingly, the standard Linux Mint Bluetooth devices list shows the Bose as connected (blueman is still frozen), but it does not appear in the Sound output hardware list.

EDIT:
I also see something else now, which is quite interesting:
The previously added but unconnected Bose HP 700 that I deleted after the reboot (see first line of this reply) keeps reappearing. It has the same name but a different address. Whenever I remove the device, it just keeps reappearing after a few seconds.

Posted: **Sun Oct 20, 2019 12:06 pm**

Hmm. Maybe try apt install --reinstall bluez bluez-tools

Also, did you uninstall Blueberry when you installed Blueman? If not, that might be conflicting.

Posted: **Mon Oct 21, 2019 2:22 am**

I have done the --reinstall, no change (Bose could get connected, but did not show up in Sound).

Then I uninstalled Blueberry. Now I have lost all Bluetooth connections, including my mouse and other headsets. Needless to say, I cannot even connect to the Bose.

I reinstalled Blueberry to give me at least other peripherals, but it does not work now. It did not conflict earlier, maybe it does now.

I am on the verge of crying, really.

Posted: **Mon Oct 21, 2019 7:41 am**

Damn! I'm really sorry about that!

I'm not sure what's going on. Try rfkill unblock bluetooth first.

Also, see if this post is of any help: viewtopic.php?f=42&t=125166&p=1694155&h ... l#p1447716

Posted: **Mon Oct 21, 2019 4:31 pm**

After some hassle, I got blueman back (and nothing else) and my BT mouse is working (haven't checked other peripherals, I suppose they are fine, too).

I have tried the tutorial on the link you sent me. As a matter of fact, I went through the whole thing without a glitch. I even got my Bose HP 700 to pair. However, it is still not showing up in the Sound settings as an available device.

EDIT:
I used the

Code: Select all

pacmd list-cards

you suggested and cannot find the Bose HP 700 in the list.

Posted: **Mon Oct 21, 2019 5:16 pm**

See if deleting the files in /home/YourUserName/.config/pulse then running pulseaudio -k in the terminal fixes that. The sound daemon should automatically restart, but if it doesn't within a few seconds, run pulseaudio --start. I'm struggling to figure out why pulseaudio isn't seeing the headphones.

Posted: **Mon Oct 21, 2019 7:56 pm**

I doubt this is going to help, but let's see the output of cat /etc/modprobe.d/blacklist.conf and ls -la /etc/modprobe.d

Also, although I'm not very knowledgeable on Bluetooth issues, I did find this; In your File Manager navigate to /var/lib/bluetooth/, then right click in the window and select Open As Root. In the root window, double click on the folder that has the MAC address, then in there open each folder one by one, skipping cache, and right click on the info file and select Open with "Text Editor". When you find the one for the Bose device, as you'll see in the Name= line does the line starting with Blocked say true?

Posted: **Tue Oct 22, 2019 4:11 am**

Hi MrEen,

Thank you for your continued interest.

I cleared the files in the pulse directory (files got recreated almost instantaneously).

Output 1:

Code: Select all

# This file lists those modules which we don't want to be loaded by
# alias expansion, usually so some other driver will be loaded for the
# device instead.

# evbug is a debug tool that should be loaded explicitly
blacklist evbug

# these drivers are very simple, the HID drivers are usually preferred
blacklist usbmouse
blacklist usbkbd

# replaced by e100
blacklist eepro100

# replaced by tulip
blacklist de4x5

# causes no end of confusion by creating unexpected network interfaces
blacklist eth1394

# snd_intel8x0m can interfere with snd_intel8x0, doesn't seem to support much
# hardware on its own (Ubuntu bug #2011, #6810)
blacklist snd_intel8x0m

# Conflicts with dvb driver (which is better for handling this device)
blacklist snd_aw2

# Causes trackpads to stop working on Lenovo 11e 2nd gen (Ubuntu: #1802135)
# and Lenovo x240 to hang on boot (Ubuntu: #1802689)
blacklist i2c_i801

# replaced by p54pci
blacklist prism54

# replaced by b43 and ssb.
blacklist bcm43xx

# most apps now use garmin usb driver directly (Ubuntu: #114565)
blacklist garmin_gps

# replaced by asus-laptop (Ubuntu: #184721)
blacklist asus_acpi

# low-quality, just noise when being used for sound playback, causes
# hangs at desktop session start (Ubuntu: #246969)
blacklist snd_pcsp

# ugly and loud noise, getting on everyone's nerves; this should be done by a
# nice pulseaudio bing (Ubuntu: #77010)
blacklist pcspkr

# EDAC driver for amd76x clashes with the agp driver preventing the aperture
# from being initialised (Ubuntu: #297750). Blacklist so that the driver
# continues to build and is installable for the few cases where its
# really needed.
blacklist amd76x_edac

Output 2:

Code: Select all

total 68
drwxr-xr-x   2 root root  4096 Aug 13 09:02 .
drwxr-xr-x 151 root root 12288 Oct 21 22:19 ..
-rw-r--r--   1 root root  2507 Jul 31  2015 alsa-base.conf
-rw-r--r--   1 root root   325 Mar 13  2016 blacklist-ath_pci.conf
-rw-r--r--   1 root root  1667 Nov 12  2018 blacklist.conf
-rw-r--r--   1 root root   210 Mar 13  2016 blacklist-firewire.conf
-rw-r--r--   1 root root   697 Mar 13  2016 blacklist-framebuffer.conf
-rw-r--r--   1 root root   156 Jul 31  2015 blacklist-modem.conf
lrwxrwxrwx   1 root root    41 Apr  4  2018 blacklist-oss.conf -> /lib/linux-sound-base/noOSS.modprobe.conf
-rw-r--r--   1 root root   583 Mar 13  2016 blacklist-rare-network.conf
-rw-r--r--   1 root root  1077 Mar 13  2016 blacklist-watchdog.conf
-rw-r--r--   1 root root   127 Mar 11  2015 dkms.conf
-rw-r--r--   1 root root   390 Apr 12  2016 fbdev-blacklist.conf
-rw-r--r--   1 root root   347 Mar 13  2016 iwlwifi.conf
-rw-r--r--   1 root root   104 Mar 13  2016 mlx4.conf
-rw-r--r--   1 root root    30 Mar  3  2016 vmwgfx-fbdev.conf

My Bose HP 700 is not blocked in the Info file.

Maybe it is not solely a pulseaudio issue, because when I try to connect the device, the headset says "mobile device not found" and the BT sign keeps on flashing as it were trying to connect. At the same time, though, the blueman icon on the tray shows that it is connected. This is in line with what I experienced when running the commands from the other link that you suggested (the step-by-step tutorial about connecting/pairing using the terminal). There I saw it briefly connect and even pair, and then it was disconnected.

When I tried to connect the Bose HP 700 one of these times using blueman and clicking on "Headset", I got an error message saying something like "software does not allow connection". It did not specify which side (Bose/Linux/Blueman) the software is on.

I believe the thing is not properly connected and the issue lays somewhere in the BT layers.

Posted: **Tue Oct 22, 2019 8:48 pm**

Darn. We need someone with more BT experience I'm afraid.

Hopefully someone will spot this soon and add some better ideas.

Posted: **Thu Nov 07, 2019 6:24 am**

I have the exact same issue with a Master&Dynamic MW60. No matter what, it does not work at all. I tried everything under the Sun bluetooth related on Linux. Does not work. So far I do love Mint on my XPS 13 but bluetooth support is general is extremely poor. Mouse becomes laggy every once in a while, headsets in many cases do not work and so on. The worst part is all these cryptic errors that state there is something wrong but no one knows exactly what and therefore no fix exists. Terrible indeed.

CR

Posted: **Tue Dec 17, 2019 7:34 pm**

"Trusting" the device was the solution that worked for me.

Run blueman-manager in a terminal or "Bluetooth Manager" in activity search.
Right-click the device in the list and click "Trust"
Right-click the device in the list and select a sub-option under "Connect To:"

Linux Mint Forums

Bose HP700 connected but not working over Bluetooth

Bose HP700 connected but not working over Bluetooth

Re: Bose HP700 connected but not working over Bluetooth

Re: Bose HP700 connected but not working over Bluetooth

Re: Bose HP700 connected but not working over Bluetooth

Re: Bose HP700 connected but not working over Bluetooth

Re: Bose HP700 connected but not working over Bluetooth

Re: Bose HP700 connected but not working over Bluetooth

Re: Bose HP700 connected but not working over Bluetooth

Re: Bose HP700 connected but not working over Bluetooth

Re: Bose HP700 connected but not working over Bluetooth

Re: Bose HP700 connected but not working over Bluetooth

Re: Bose HP700 connected but not working over Bluetooth

Re: Bose HP700 connected but not working over Bluetooth

Re: Bose HP700 connected but not working over Bluetooth

Re: Bose HP700 connected but not working over Bluetooth

Re: Bose HP700 connected but not working over Bluetooth

Re: Bose HP700 connected but not working over Bluetooth

Re: Bose HP700 connected but not working over Bluetooth

Re: Bose HP700 connected but not working over Bluetooth