From: Stuart Pook <kernel6org@pook.es>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: BlueZ development <linux-bluetooth@vger.kernel.org>
Subject: Re: bluez-4.9 + 2.6.27-rc8 + SCO headset -> bluetoothd: connect: Operation not permitted
Date: Sat, 04 Oct 2008 13:25:27 +0200 [thread overview]
Message-ID: <48E752A7.70600@pook.es> (raw)
In-Reply-To: <2d5a2c100810032047s47bec394w828852079d64e591@mail.gmail.com>
On 04/10/08 05:47, Luiz Augusto von Dentz wrote:
> There is a regression on bluetoothd daemon, we introduce a SCO socket
> listen recently which is causing the problem, although it seem that
> the driver is also cooperating with the problem.
ok. Thanks for the information. Would installing bluez-4.10 help?
Or would changing my USB blueooth dongle help? I have an old Bluetooth
1.2 Linksys USBBT100 dongle but have ordered a BELKIN F8T017ng
(Bluetooth v2.1 + EDR + Class I) which should arrive in a few days.
Perhaps it will work better though it appears that kernel 2.6.27-rc8
does not include the required quirks (2.6.26-mh6 crashes for me).
I'm keen to get a Bluetooth headset working for VoIP so I could also
change my headset if necessary. My Jabra JX10 Series II is however quite
recent so I'd hope to be able to get it to work.
thanks
Stuart
next prev parent reply other threads:[~2008-10-04 11:25 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-30 21:03 bluez-4.9 + 2.6.27-rc8 + SCO headset -> bluetoothd: connect: Operation not permitted Stuart Pook
2008-09-30 23:26 ` David Sainty
2008-10-01 17:30 ` Stuart Pook
2008-10-04 3:47 ` Luiz Augusto von Dentz
2008-10-04 11:25 ` Stuart Pook [this message]
2008-10-04 11:51 ` Marcel Holtmann
2008-10-04 23:24 ` bluez-4.11 + 2.6.27-rc8 + SCO headset -> bluetoothd: connect(): Connection timed out (110) Stuart Pook
2008-10-05 17:50 ` Johan Hedberg
2008-10-05 19:17 ` Stuart Pook
2008-10-05 20:07 ` bluez-4.11 + 2.6.27-rc8 + SCO headset -> Invalid read of size 4 Stuart Pook
2008-10-06 8:47 ` Johan Hedberg
2008-10-06 10:52 ` Johan Hedberg
2008-10-06 18:38 ` Stuart Pook
2008-10-06 19:56 ` Stuart Pook
2008-10-06 20:31 ` Johan Hedberg
2008-10-06 20:56 ` bluez/git + 2.6.27-rc8 + SCO headset -> SIGSEGV Stuart Pook
2008-10-06 21:03 ` Marcel Holtmann
2008-10-06 21:10 ` Stuart Pook
2008-10-06 21:21 ` Marcel Holtmann
2008-10-06 22:40 ` bluez/git + 2.6.27-rc8 + bluetoothd " Stuart Pook
2008-10-07 5:34 ` Johan Hedberg
2008-12-06 12:15 ` bluez-4.22 + twinkle -> Unable to lock headset Stuart Pook
2008-12-08 18:42 ` Luiz Augusto von Dentz
2008-12-09 12:23 ` sreevani medhahal
2008-10-06 20:39 ` bluez/git + 2.6.27-rc8 + Belkin F8T017 -> Can't read class of adapter Stuart Pook
2008-10-06 20:45 ` Marcel Holtmann
2008-10-06 21:55 ` Stuart Pook
2008-10-06 22:38 ` Marcel Holtmann
2008-10-06 23:17 ` bluez/git + 2.6.27-rc8 + Belkin F8T017 -> works with reset=1 Stuart Pook
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=48E752A7.70600@pook.es \
--to=kernel6org@pook.es \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@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