From: JP Freeley <jpf321@gmail.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Error: sdptool browse --> Connection reset by peer
Date: Tue, 25 Jul 2006 00:26:26 -0400 [thread overview]
Message-ID: <44C59D72.5070402@gmail.com> (raw)
In-Reply-To: <44BFF555.2090606@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 3234 bytes --]
Just FYI ....
It seems as though most of my woes are over.
As it turns out, I was running the debian-etch version of bluez ..
which seems to be a bit stale, and still buggy.
I recompiled based on the 3.1.tar.gz packages from
bluez.sourceforge.net and everything seems working much better.
My problem right now is that the /etc/init.d/bluetooth script doesn't
work. I went through and fixed paths to /usr/local/sbin (from simply
/usr/sbin) .. It produces no log output and doesn't start any daemons,
just a quiet exit. Any thoughts would be appreciated. When I run the
most important commands by hand, they work fine (so it must be failing
before trying to execute these commands):
start-stop-daemon --start --exec /usr/local/sbin/hcid
start-stop-daemon --start --exec /usr/local/sbin/sdpd
(I think I have kernel rfcomm [krfcommd])
Thanks
jpf
JP Freeley wrote:
> Mr. Holtmann--
>
> Thanks for the reply, but I'm having trouble replicating the
> situation. I'm having trouble in general I think. My bluetooth setup
> seems quite finicky and unstable. There are so many factors which
> affect this, it's hard to point the finger at any single point of
> failure. (Could be handheld devices, could be Linux, could be bluez,
> could be BT Dongle, could be kernel, etc.)
>
> I can send you any notes on my configuration that may lend clues, just
> tell me where to start. I just ran an "apt-get upgrade" last night and
> haven't had much time to see if it helped at all yet.
>
> Thanks,
>
> jpf
>
> Marcel Holtmann wrote:
>> Hi,
>>
>>
>>> I am getting an error ("Connection reset by peer") when I run an
>>> "sdptool browse" and it discovers my Sprint Pocket PC handset.
>>>
>>> I'm sure this is probably a common situation. I have attached my
>>> "hcidump -V -R". Any help in deciphering this problem would be great. My
>>> goal is to send a .vcf file to the device.
>>>
>>
>> please include "hcidump -X -V".
>>
>> Regards
>>
>> Marcel
>>
>>
>>
>> -------------------------------------------------------------------------
>> Take Surveys. Earn Cash. Influence the Future of IT
>> Join SourceForge.net's Techsay panel and you'll get the chance to share your
>> opinions on IT & business topics through brief surveys -- and earn cash
>> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>> _______________________________________________
>> Bluez-devel mailing list
>> Bluez-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>>
>>
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys -- and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> ------------------------------------------------------------------------
>
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>
[-- Attachment #1.2: Type: text/html, Size: 4473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 348 bytes --]
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-07-25 4:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-19 16:28 [Bluez-devel] Error: sdptool browse --> Connection reset by peer JP Freeley
2006-07-20 0:48 ` Marcel Holtmann
2006-07-20 21:27 ` JP Freeley
2006-07-25 4:26 ` JP Freeley [this message]
2006-07-22 14:08 ` [Bluez-devel] It's rfcomm connect problem Fabrizio Guglielmino
2006-07-24 8:38 ` Andreas Gaufer
2006-07-24 13:33 ` Fabrizio Guglielmino
2006-07-24 13:56 ` Andreas Gaufer
2006-07-24 16:35 ` Marcel Holtmann
2006-07-24 18:34 ` Andreas Gaufer
2006-07-24 20:30 ` Fabrizio Guglielmino
2006-07-24 21:12 ` Marcel Holtmann
2006-07-27 9:04 ` Fabrizio Guglielmino
2006-07-27 9:25 ` [Bluez-devel] It's rfcomm connect problem [ERRATA] Fabrizio Guglielmino
2006-07-28 11:14 ` [Bluez-devel] It's rfcomm connect problem Marcel Holtmann
2006-07-31 10:02 ` [Bluez-devel] About l2cap patch to handle multiple connections Fabrizio Guglielmino
2006-07-31 14:14 ` Marcel Holtmann
2006-08-02 11:24 ` Fabrizio Guglielmino
2006-08-02 13:43 ` Marcel Holtmann
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=44C59D72.5070402@gmail.com \
--to=jpf321@gmail.com \
--cc=bluez-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.