FS#21445 - [bluez] 4.76-1 regression: bluetoothd segfaults when launching bluetooth programs

Attached to Project: Arch Linux
Opened by ilya (leniviy) - Sunday, 24 October 2010, 10:17 GMT
Last edited by Andrea Scarpino (BaSh) - Tuesday, 26 October 2010, 19:09 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Andrea Scarpino (BaSh)
Architecture i686
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
It all started after upgrading bluez from 4.69-1 to 4.76-1 .
'hcitool scan' work and the bluetooth service starts normally, but When launching any related program (e.g. Gnome bluetooth-applet), bluetoothd dies with segfault:
Oct 24 11:31:01 IL kernel: bluetoothd[3894]: segfault at 0 ip b7632653 sp bfee9b5c error 4 in libc-2.12.1.so[b75be000+145000]

Downgrading to 4.69-1 helps, I don't even have to reboot, just restarting the service

Additional info:
* package version(s)
kernel26 2.6.35.7-1
bluez 4.76-1
dbus 1.4.0-1

$ lsusb | grep lue
Bus 003 Device 002: ID 0a5c:2121 Broadcom Corp. BCM2210 Bluetooth
This task depends upon

Closed by  Andrea Scarpino (BaSh)
Tuesday, 26 October 2010, 19:09 GMT
Reason for closing:  Fixed
Additional comments about closing:  bluez 4.77-1

thanks to reported this upstream and helped to fix it!
Comment by Andrea Scarpino (BaSh) - Sunday, 24 October 2010, 12:48 GMT
Works here (bluedevil). Is your system fully up-to-date?
Comment by ilya (leniviy) - Sunday, 24 October 2010, 12:54 GMT
Andrea: did pacman -Suy yesterday
posted to linux-bluetooth http://marc.info/?l=linux-bluetooth&m=128792385615617&w=2
Comment by Andrea Scarpino (BaSh) - Sunday, 24 October 2010, 13:06 GMT
which mirror are you using?
Comment by ilya (leniviy) - Sunday, 24 October 2010, 13:14 GMT
Server = http://ftp.cc.uoc.gr/mirrors/linux/archlinux/$repo/os/$arch

Installed clean Arch on Virtualbox and attached my dongle. Same segfault
Comment by ilya (leniviy) - Monday, 25 October 2010, 20:19 GMT
OK, not every BT program kills bluetoothd. For example, Smartcam (which I put to startup) does and AnyRemote doen't.
Still, an ability of a non-root program to kill a daemon is a daemon's bug.
Can someone try to reproduce it? Install smartcam from aur and start it from terminal.
In settings choose Bluetooth. When you press OK, it should print: "Protocol error" to terminal indicating that bluetoothd process just died.
Restart smartcam and this time smartcam itself segfaults.
Comment by Andrea Scarpino (BaSh) - Tuesday, 26 October 2010, 16:21 GMT
you need to fix smartcam using this patch
   no-bluetooth-segfault.patch (0.9 KiB)
Comment by ilya (leniviy) - Tuesday, 26 October 2010, 19:08 GMT
these 2 bugs unrelated
upstream bug confirmed
fixed in 4.77

Loading...