Re: Corruption in bluetoothd if started when adapter was rfkilled

Hi,

On Fri, Oct 16, 2009, Valmantas Palikša wrote:

Steps to reproduce:
1. rfkill block bluetooth
2. start bluetoothd
3. kill bluetoothd

I don't seem to have rfkill support (at least using that command) on my
laptop so I can't verify this fix, but could you try the attached patch
and see if it resolves the issue? The problem seems to be that in this use
case we never load/probe the adapter drivers but still call their remove
callbacks when the adapter initialization fails. This causes some drivers
to call btd_adapter_unref on adapter objects for which they do not own a
reference.

Johan