Skip to main content ↑ ↓
Topic: Segfault bluetoothd bluez 5.49-1 (Read 1462 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Segfault bluetoothd bluez 5.49-1

Hi, everybody!

I own a very cheap Bluetooth dongle:
Code: [Select]
0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

Then I installed the following:
Code: [Select]
gremlins/bluez-runit 20180226-1 (runit-world) [installed]
world/bluez 5.49-1 [installed]
world/bluez-hid2hci 5.49-1 [installed]
world/bluez-libs 5.49-1 [installed]
world/bluez-openrc 20180221-1 (openrc-world) [installed]
world/bluez-plugins 5.49-1 [installed]
world/bluez-utils-compat 5.47-1 [installed]
community/bluez-tools 0.2.0-1 [installed]

Ran:
Code: [Select]
# rc-service bluetooth start
bluetooth         | * Starting bluetooth ...      [ ok ]
$ bluetoothctl
[NEW] Controller xx:xx:xx:xx:xx:xx Somename [default]
Agent registered
[bluetooth]# show xx:xx:xx:xx:xx:xx
Controller xx:xx:xx:xx:xx:xx
	Name: Somename
	Alias: Somename
	Class: 0x00000104
	Powered: yes
	Discoverable: no
	Pairable: yes
	UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
	UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
	UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
	Modalias: usb:v1D6Bp0246d0531
	Discovering: yes

Meanwhile in /var/log/messages:
Code: [Select]
Mar 19 14:04:21 PowerTuX kernel: usb 5-3: new full-speed USB device number 4 using ohci-pci 
Mar 19 14:04:21 PowerTuX kernel: usb 5-3: new full-speed USB device number 5 using ohci-pci 
Mar 19 14:04:21 PowerTuX kernel: usb 5-3: New USB device found, idVendor=0a12, idProduct=0001 
Mar 19 14:04:21 PowerTuX kernel: usb 5-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0 
Mar 19 14:04:24 PowerTuX bluetoothd[15598]: Bluetooth daemon 5.49 
Mar 19 14:04:24 PowerTuX bluetoothd[15598]: Starting SDP server 
Mar 19 14:04:24 PowerTuX bluetoothd[15598]: Bluetooth management interface 1.14 initialized 
Mar 19 14:04:24 PowerTuX NetworkManager[2466]: <info>  [1521489864.9380] bluez5: NAP: added interface xx:xx:xx:xx:xx:xx 
Mar 19 14:04:25 PowerTuX dbus-daemon[1132]: [system] Activating service name='org.blueman.Mechanism' requested by ':1.135' (uid=1000 pid=4832 comm="python /usr/bin/blueman-applet ") (using servicehelper) 
Mar 19 14:04:26 PowerTuX blueman-mechanism[15609]: Starting blueman-mechanism  
Mar 19 14:04:26 PowerTuX dbus-daemon[1132]: [system] Successfully activated service 'org.blueman.Mechanism' 
Mar 19 14:04:26 PowerTuX blueman-mechanism[15609]: loading Rfcomm  
Mar 19 14:04:26 PowerTuX blueman-mechanism[15609]: loading Ppp  
Mar 19 14:04:26 PowerTuX blueman-mechanism[15609]: loading RfKill  
Mar 19 14:04:26 PowerTuX blueman-mechanism[15609]: loading Network 

Until this point everything has happiness; however, when I tried to make the dongle discoverable...
Code: [Select]
bluetooth]# discoverable on
Changing discoverable on succeeded
Agent unregistered
[DEL] Controller xx:xx:xx:xx:xx:xx Somename [default]
Waiting to connect to bluetoothd...
And in /var/log/messages:
Code: [Select]
Mar 19 14:05:40 PowerTuX kernel: bluetoothd[15598] segfault at 8 ip 00005648765bafd0 sp 00007fff8dc16248 error 4 in bluetoothd[564876557000+f8000]

Kernel is:
Code: [Select]
# uname -a
Linux PowerTuX 4.15.10-1-ck-bulldozer #1 SMP PREEMPT Thu Mar 15 19:48:49 EDT 2018 x86_64 GNU/Linux

desktop alternative, blueman, also segfaults when trying to make the device discoverable.

Any help would be appreciated.

Regards.