yep, client->dev = NULL seems to be a bug, although by looking the log it seems there is another problem, the sco connection doesn't succeed but it still attempt to send the file descriptor. The logic on a2dp is a little different, since it doesn't start the stream on BT_SETCONFIGURATION_REQ and unlock the sep in any possible error. Btw, I couldn't reproduce the problem here by using aplay, arecord or even both together. -- Luiz Augusto von Dentz Engenheiro de Computação -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html