From: Serhiy Kachaniuk <serzholino@gmail.com>
To: Fabian Greffrath <fabian@greffrath.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [bugreport]
Date: Thu, 6 May 2010 13:18:48 +0300 [thread overview]
Message-ID: <j2o793f89501005060318nfb8e2e84y54a2b1e9ee346ca3@mail.gmail.com> (raw)
In-Reply-To: <4BE2947F.9030103@greffrath.com>
2010/5/6 Fabian Greffrath:
> Maybe a stupid question, but do you have an application like GNOME's
> bluetooth applet running (that keeps the shared lib in memory) while
> switching bluez versions?
>
Yeah, kbluetooth was running, but switching bluez version implies
bluetoothd restart.
Anyway, here is what i get after terminating kbluetooth and manually
stopping and starting bluetoothd:
First run without sudo:
$ hciconfig -a
hci0: Type: USB
BD Address: 00:1A:7D:0A:C8:8A ACL MTU: 377:10 SCO MTU: 16:0
UP RUNNING
RX bytes:664 acl:0 sco:0 events:18 errors:0
TX bytes:73 acl:0 sco:0 commands:19 errors:0
Features: 0xff 0xff 0x0d 0x38 0x08 0x08 0x00 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy:
Link mode: SLAVE ACCEPT
Can't read local name on hci0: Connection timed out (110)
Second run without sudo:
$ hciconfig -a
hci0: Type: USB
BD Address: 00:1A:7D:0A:C8:8A ACL MTU: 377:10 SCO MTU: 16:0
UP RUNNING
RX bytes:664 acl:0 sco:0 events:18 errors:0
TX bytes:77 acl:0 sco:0 commands:20 errors:0
Features: 0xff 0xff 0x0d 0x38 0x08 0x08 0x00 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy:
Link mode: SLAVE ACCEPT
Can't read local name on hci0: Connection timed out (110)
Third run without sudo, and 'Name:' appears:
$ hciconfig -a
hci0: Type: USB
BD Address: 00:1A:7D:0A:C8:8A ACL MTU: 377:10 SCO MTU: 16:0
UP RUNNING
RX bytes:664 acl:0 sco:0 events:18 errors:0
TX bytes:83 acl:0 sco:0 commands:21 errors:0
Features: 0xff 0xff 0x0d 0x38 0x08 0x08 0x00 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy:
Link mode: SLAVE ACCEPT
Name: 'Broadcom BCM2035'
Can't read class of device on hci0: Connection timed out (110)
Same result with sudo: first one or two runs didn't get name, but later did
next prev parent reply other threads:[~2010-05-06 10:18 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 ` Serhiy Kachaniuk [this message]
[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 ` [bugreport] Vinicius Gomes
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=j2o793f89501005060318nfb8e2e84y54a2b1e9ee346ca3@mail.gmail.com \
--to=serzholino@gmail.com \
--cc=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).