Am 25.05.2010 14:38, schrieb Bastien Nocera:
The output of "locale" as root would probably help.
Here you are: $ su -c locale LANG=de_DE.UTF-8 LC_CTYPE="de_DE.UTF-8" LC_NUMERIC="de_DE.UTF-8" LC_TIME="de_DE.UTF-8" LC_COLLATE="de_DE.UTF-8" LC_MONETARY="de_DE.UTF-8" LC_MESSAGES="de_DE.UTF-8" LC_PAPER="de_DE.UTF-8" LC_NAME="de_DE.UTF-8" LC_ADDRESS="de_DE.UTF-8" LC_TELEPHONE="de_DE.UTF-8" LC_MEASUREMENT="de_DE.UTF-8" LC_IDENTIFICATION="de_DE.UTF-8" LC_ALL=
My guess is that we make assumptions as to a user entry being valid UTF-8 somewhere, when it could be non-UTF-8. As for your problem, I don't think we want to allow non-UTF-8 device names anyhow. They're not valid spec.
Sure, that's why my patch converts the device name to valid UTF-8 as soon as it is possible to detect that it is actually non-UTF-8. However, it may be right that this approach only fixes the symptoms and does not cure the illness. But my knowledge of the Bluez code is not deep enough to track down the real issue on my own.
Thanks for your reply anyway, 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
