From: Vinicius Gomes <vinicius.gomes@openbossa.org>
To: Serhiy Kachaniuk <serzholino@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [bugreport]
Date: Tue, 11 May 2010 10:52:30 -0300 [thread overview]
Message-ID: <AANLkTiliG_XySAecN9JZ9cBt1rEc7IqtFB7ISaHP4yDb@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinOD1ODHqYSWTLv5ho2ZYU-bfiJ1xYkWNlbgaZQ@mail.gmail.com>
Hi Serhiy,
On Tue, May 11, 2010 at 10:06 AM, Serhiy Kachaniuk <serzholino@gmail.com> wrote:
> 2010/5/6 Serhiy Kachaniuk <serzholino@gmail.com>:
>> Hi!
>>
>> My USB bluetooth adapter stopped working with new versions of bluez.
>> Latest version which works is 4.32.
>> I initially reported bug for ubuntu package in launchpad here
>> https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/453885 , but then
>> i tried also opensuse livecd and problem remained there too, so looks
>> like it's not ubuntu specific.
>> jhe at #bluez-devel suggested to me to collect hcidump output on
>> bluetoothd startup, and then write to this mailinglist. I attached
>> suggested hcidumps for bluez versions 4.64 and 4.32, and looks like
>> 4.64 stops initialization process after it cannot read parameter
>> 'Default Link Policy Settings' from device.
>>
>> Can you please take a look at this bug?
>> Thanks in advance.
>>
>
> Can someone turn this e-mail thread into bluez bugreport? If i
> understand correctly, only developers can create bluez bugreports in
> trac? Also, if you need any more debugging info, i would be glad to
> provide you with any.
This (the mailing list) is the correct place for bug reports.
Someone here in the office has an ancient Bluetooth 1.2 dongle, which
shows a similar problem. Now that you discovered that it is probably a
regression and I can reproduce it, I will try to debug it.
And it looks like that the hcidump logs that you attached in your
first email got lost somehow.
Anyway, I think that the only information missing is your kernel version.
Cheers,
--
Vinicius
next prev parent reply other threads:[~2010-05-11 13:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-06 5:22 [bugreport] Serhiy Kachaniuk
2010-05-06 7:34 ` [bugreport] Fabian Greffrath
2010-05-06 9:56 ` [bugreport] Serhiy Kachaniuk
2010-05-11 14:47 ` [bugreport] Iain Hibbert
2010-05-11 16:40 ` [bugreport] Serhiy Kachaniuk
2010-05-11 17:23 ` [bugreport] Iain Hibbert
2010-05-06 10:01 ` [bugreport] Serhiy Kachaniuk
2010-05-06 10:05 ` [bugreport] Fabian Greffrath
2010-05-06 10:11 ` [bugreport] Bastien Nocera
2010-05-06 10:20 ` [bugreport] Fabian Greffrath
2010-05-06 10:18 ` [bugreport] Serhiy Kachaniuk
[not found] ` <4BE298C4.7090904@greffrath.com>
2010-05-06 10:32 ` [bugreport] Serhiy Kachaniuk
2010-05-06 10:34 ` [bugreport] Fabian Greffrath
2010-05-06 10:39 ` [bugreport] Serhiy Kachaniuk
2010-05-07 8:51 ` [bugreport] Serhiy Kachaniuk
2010-05-11 13:06 ` [bugreport] Serhiy Kachaniuk
2010-05-11 13:52 ` Vinicius Gomes [this message]
2010-05-11 16:38 ` [bugreport] Serhiy Kachaniuk
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=AANLkTiliG_XySAecN9JZ9cBt1rEc7IqtFB7ISaHP4yDb@mail.gmail.com \
--to=vinicius.gomes@openbossa.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=serzholino@gmail.com \
/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).