Petr Lautrbach wrote: > but there is running boot (changing runlevel) process, so sometime after starting dbus is started > bluetooth again, this time successfully Triggered by what? A init script that is always enabled? Is it checking if there is an adapter present? If not, it's unconditionally always starting bluetoothd (and thus the ondemand functionality is not strictly needed ;) Best regards, Stefan -- Stefan Seyfried R&D Team Mobile Devices | "Any ideas, John?" SUSE LINUX Products GmbH, Nürnberg | "Well, surrounding them's out." This footer brought to you by insane German lawmakers: SUSE Linux Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- 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
