Dear Bluez developers, Am 21.05.2010 11:01, schrieb Fabian Greffrath:
Long story short: If the bluetooth adapter's device name contains non-UTF-8 characters (which my dongle does by default), it requires a manual device name change and a restart of the daemon (!) to bring the device back to life. I have previously posted a patch to this list which fixes this issue by instantly converting faulty device names to UTF-8 and writing them back to the device during the device configuration phase: <http://marc.info/?l=linux-bluetooth&m=127315737929319&w=2> However, I have been told that my "patch might be just working around the real issue instead of fixing it" and that "It sounds like there's something else wrong in the initialization process which makes the initialzation fail if the adapter contains some invalid default name". So, please, try the steps I presented above yourself and tell me what is wrong so I can attempt to fix the root of the problem. I am really itching to get this issue fixed in the short term.
this is a real issue (it bites me each and every time I plug in my USB Bluetooth dongle) and it is easily reproducible following the simple steps I have posted earlier. Please give me a hint how to track down this bug and fix it.
Thanks, Fabian -- 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
