[SOLVED] bluetooth headset works only on root

husarz · 12-26-2016, 05:32 PM

Hey,

I'm trying to make bluetooth headset to run. So far I was able to successfully pair and connect then run (play sound) but only as root. Then the conclusion is that the problem is somewhere in permissions. The solution was to add regular user to all default Slackware groups. So I did it, unfortunately w/o success.
I work on Slackware64 14.2 with BlueZ 5 then only pulseaudio possible for bt audio devices. I run pulseaudio with '--start' flag for every user. Then as my regular user as well. After paired and connected headset in bluetoothctl as root I can see headset in pacmd 'list-sinks' but only as root. Regular user can't see it.

My regular user has groups as follows:

Code:

bash-4.3$ groups
users wheel lp floppy audio video cdrom pulse plugdev power netdev scanner mntfs

BW-userx · 12-27-2016, 10:46 AM

hi I am back, sorry to hear you not getting this to work yet. I don't use Bluetooth headsets, but I did find this on the same subject getting Bluetooth headset to work in Slackware in here

http://www.linuxquestions.org/questi...re-4175490452/

and here:

Quote:

Finally I found the cause of my Bluetooth problems. As I supposed a solution was simple. It was enough to run blueman-manager as root. Before I started it as a regular user. During configuration of the system one of my scripts should register my user in the plugdev group. For some reason, it failed. In result my user hadn’t enough rights to run blueman-manager.

http://www.linuxquestions.org/questi...roblem-816013/

maybe remove yourself from plugdev, logout, login add yourself back to it logout, login and see if that helps OR just put me on ignore and wait ....

Code:

sudo usermod -G users wheel lp floppy audio video cdrom pulse  power netdev scanner mntfs $USER

then adding plugdev back to you

Code:

sudo usermod -aG  plugdev users wheel lp floppy audio video cdrom pulse  power netdev scanner mntfs $USER

Richard Cranium · 12-27-2016, 02:39 PM

Quote:

Originally Posted by husarz

Hey,

I'm trying to make bluetooth headset to run. So far I was able to successfully pair and connect then run (play sound) but only as root. Then the conclusion is that the problem is somewhere in permissions. The solution was to add regular user to all default Slackware groups. So I did it, unfortunately w/o success.
I work on Slackware64 14.2 with BlueZ 5 then only pulseaudio possible for bt audio devices. I run pulseaudio with '--start' flag for every user. Then as my regular user as well. After paired and connected headset in bluetoothctl as root I can see headset in pacmd 'list-sinks' but only as root. Regular user can't see it.

My regular user has groups as follows:

Code:

bash-4.3$ groups
users wheel lp floppy audio video cdrom pulse plugdev power netdev scanner mntfs

While replying to another thread a few minutes ago, I paired my H800 headset as a normal user (and have never done so as root).

I did not use bluetoothctl to pair but used the XFCE app to do so.

Code:

$ pacmd list-sinks
3 sink(s) available.
  * index: 0
	name: <alsa_output.pci-0000_00_07.0.analog-stereo>
	driver: <module-alsa-card.c>
	flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY DYNAMIC_LATENCY
	state: SUSPENDED
	suspend cause: IDLE 
	priority: 9959
	volume: front-left: 65536 / 100% / 0.00 dB,   front-right: 65536 / 100% / 0.00 dB
	        balance 0.00
	base volume: 65536 / 100% / 0.00 dB
	volume steps: 65537
	muted: yes
	current latency: 0.00 ms
	max request: 0 KiB
	max rewind: 0 KiB
	monitor source: 0
	sample spec: s16le 2ch 48000Hz
	channel map: front-left,front-right
	             Stereo
	used by: 0
	linked by: 0
	configured latency: 0.00 ms; range is 0.50 .. 1837.33 ms
	card: 0 <alsa_card.pci-0000_00_07.0>
	module: 6
	properties:
		alsa.resolution_bits = "16"
		device.api = "alsa"
		device.class = "sound"
		alsa.class = "generic"
		alsa.subclass = "generic-mix"
		alsa.name = "VT1708S Analog"
		alsa.id = "VT1708S Analog"
		alsa.subdevice = "0"
		alsa.subdevice_name = "subdevice #0"
		alsa.device = "0"
		alsa.card = "1"
		alsa.card_name = "HDA NVidia"
		alsa.long_card_name = "HDA NVidia at 0xf9e78000 irq 22"
		alsa.driver_name = "snd_hda_intel"
		device.bus_path = "pci-0000:00:07.0"
		sysfs.path = "/devices/pci0000:00/0000:00:07.0/sound/card1"
		device.bus = "pci"
		device.vendor.id = "10de"
		device.vendor.name = "NVIDIA Corporation"
		device.product.id = "0774"
		device.product.name = "MCP72XE/MCP72P/MCP78U/MCP78S High Definition Audio"
		device.form_factor = "internal"
		device.string = "front:1"
		device.buffering.buffer_size = "352768"
		device.buffering.fragment_size = "176384"
		device.access_mode = "mmap+timer"
		device.profile.name = "analog-stereo"
		device.profile.description = "Analog Stereo"
		device.description = "Built-in Audio Analog Stereo"
		alsa.mixer_name = "VIA VT1708S"
		alsa.components = "HDA:11060397,104383c5,00100000"
		module-udev-detect.discovered = "1"
		device.icon_name = "audio-card-pci"
	ports:
		analog-output-lineout: Line Out (priority 9900, latency offset 0 usec, available: yes)
			properties:
				
		analog-output-headphones: Headphones (priority 9000, latency offset 0 usec, available: no)
			properties:
				device.icon_name = "audio-headphones"
	active port: <analog-output-lineout>
    index: 1
	name: <combined>
	driver: <module-combine-sink.c>
	flags: DECIBEL_VOLUME LATENCY DYNAMIC_LATENCY
	state: SUSPENDED
	suspend cause: IDLE 
	priority: 1000
	volume: front-left: 65536 / 100% / 0.00 dB,   front-right: 65536 / 100% / 0.00 dB
	        balance 0.00
	base volume: 65536 / 100% / 0.00 dB
	volume steps: 65537
	muted: yes
	current latency: 0.00 ms
	max request: 34 KiB
	max rewind: 0 KiB
	monitor source: 1
	sample spec: s16le 2ch 44100Hz
	channel map: front-left,front-right
	             Stereo
	used by: 0
	linked by: 0
	configured latency: 0.00 ms; range is 0.50 .. 200.00 ms
	module: 15
	properties:
		device.class = "filter"
		device.description = "Simultaneous output to Built-in Audio Analog Stereo, H800 Logitech Headset"
		device.icon_name = "audio-card"
    index: 3
	name: <bluez_sink.00_0D_44_D1_7D_CE>
	driver: <module-bluez5-device.c>
	flags: HARDWARE DECIBEL_VOLUME LATENCY 
	state: IDLE
	suspend cause: 
	priority: 9030
	volume: front-left: 65536 / 100% / 0.00 dB,   front-right: 65536 / 100% / 0.00 dB
	        balance 0.00
	base volume: 65536 / 100% / 0.00 dB
	volume steps: 65537
	muted: no
	current latency: 27.45 ms
	max request: 3 KiB
	max rewind: 0 KiB
	monitor source: 3
	sample spec: s16le 2ch 44100Hz
	channel map: front-left,front-right
	             Stereo
	used by: 0
	linked by: 0
	fixed latency: 45.32 ms
	card: 2 <bluez_card.00_0D_44_D1_7D_CE>
	module: 34
	properties:
		bluetooth.protocol = "a2dp_sink"
		device.description = "H800 Logitech Headset"
		device.string = "00:0D:44:D1:7D:CE"
		device.api = "bluez"
		device.class = "sound"
		device.bus = "bluetooth"
		device.form_factor = "headset"
		bluez.path = "/org/bluez/hci0/dev_00_0D_44_D1_7D_CE"
		bluez.class = "0x240404"
		bluez.alias = "H800 Logitech Headset"
		device.icon_name = "audio-headset-bluetooth"
		device.intended_roles = "phone"
	ports:
		headset-output: Headset (priority 0, latency offset 0 usec, available: yes)
			properties:
				
	active port: <headset-output>

bassmadrigal · 12-27-2016, 03:25 PM

As asked in the other thread, why are you manually running pulseaudio? There should be no reason to run that as it should all be handled automatically. Do you have any pre-14.2 .asoundrc or /etc/asound.conf files? If so, they should be removed (or renamed) so pulse can work as expected. Have you tried a new user to see if the problem is related to your user's configs?

husarz · 12-27-2016, 03:32 PM

Quote:

Originally Posted by bassmadrigal

As asked in the other thread, why are you manually running pulseaudio? There should be no reason to run that as it should all be handled automatically. Do you have any pre-14.2 .asoundrc or /etc/asound.conf files? If so, they should be removed (or renamed) so pulse can work as expected. Have you tried a new user to see if the problem is related to your user's configs?

Yes, I have some old configuration when the system have been upgraded several times to newer Slackware versions. I will work now to check and eventually fix everything around this context.

husarz · 12-27-2016, 05:40 PM

I did more cleanup-after-upgrade (including use of .new files) in /etc and /etc/rc.d. Now I can connect to bluetooth headphones as regular user who is assigned to all mentioned groups excluding 'wheel' group. Marking thread as SOLVED.