From: Fabian Greffrath <fabian@greffrath.com>
To: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: WRT non-UTF-8 device names
Date: Tue, 25 May 2010 13:35:22 +0200 [thread overview]
Message-ID: <4BFBB5FA.6000200@greffrath.com> (raw)
In-Reply-To: <1274432516.4068.29.camel@vfrodo>
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
next prev parent reply other threads:[~2010-05-25 11:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-21 9:01 WRT non-UTF-8 device names Fabian Greffrath
2010-05-25 11:35 ` Fabian Greffrath [this message]
2010-05-25 12:38 ` Bastien Nocera
2010-05-25 12:56 ` Fabian Greffrath
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BFBB5FA.6000200@greffrath.com \
--to=fabian@greffrath.com \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).