From: Per Thomas Jahr <perja@extern.uio.no>
To: linux-bluetooth <linux-bluetooth@vger.kernel.org>
Cc: pavan_savoy@indiatimes.com
Subject: Re: ObexFTP killing the Local SDP server
Date: Fri, 12 Dec 2008 10:11:29 +0100 [thread overview]
Message-ID: <1229073089.3899.21.camel@apollo2> (raw)
In-Reply-To: <1229046459.22285.24.camel@violet.holtmann.net>
On Fri, 2008-12-12 at 02:47 +0100, Marcel Holtmann wrote:
> Hi Pavan,
>
> > I have a blueZ [version 3.35, wrongly claimed as 3.36] hcid daemon running on a machine, and I have put on it an ObexFTP daemon application [openobex + obexftp] which is statically linked with [bluez-libs-3.36].
> >
> > The problem I face is, when I start obexftpd it says cannot register with SDP server,
> > register to SDP Server failed, and comes out & then waits for a connecttion.
> >
> > When I looked into it, it was failing in the function "sdp_connect_local" in bluez-libs/src/sdp.c & it also caused the SDP server to kill, So I cannot even do an sdptool browse local after this.
> > [I checked sdptool browse local before running obexftpd & it is fine...]
> >
> > Is it a problem with permissions given to unix domain sockets on platform ? Or something to do with the version mis-match ? Or something totally different ?
>
> I don't know. Your system seems to be screwed up. Why don't you start
> using something more recent like 4.22.
If you are on Fedora, there was an security update of dbus a couple of
days ago that screwed up bluetooth (and a couple of other things) for
most users. Maybe that is the problem.
http://forums.fedoraforum.org/showthread.php?t=207069
--
Cheers
Per Thomas
prev parent reply other threads:[~2008-12-12 9:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-08 22:47 ObexFTP killing the Local SDP server pavan_savoy
2008-12-12 1:47 ` Marcel Holtmann
2008-12-12 9:11 ` Per Thomas Jahr [this message]
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=1229073089.3899.21.camel@apollo2 \
--to=perja@extern.uio.no \
--cc=linux-bluetooth@vger.kernel.org \
--cc=pavan_savoy@indiatimes.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