From: Steffen Becker <steffen.becker@tu-ilmenau.de>
To: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: gnome-obex-send problem
Date: Thu, 30 Aug 2012 12:05:22 +0200 [thread overview]
Message-ID: <503F3AE2.2040800@tu-ilmenau.de> (raw)
Hello,
i have two Scientific Linux 5.8 computers and a bluetooth 3.0+HS dongle
at each PC. The bluetooth devices are paired. I want to transmit data
files via bluetooth (more precisely: via HS) but it does not work:
On both PC's I added:
# sdptool add ftp
# sdptool add opush
then I tried:
# nautilus-sendto <data-file>
and choosed the remote device. But I got an error: "gnome-obex-send: the
remote device doesn't support object receiving".
Funny: When I shut down the remote device then i get the same error -.-
On top of that, I tried to start an obex server at the remote PC:
# gnome-obex-server
** (gnome-obex-server:18545): WARNING **: OBEX server register
error: -1
** (gnome-obex-server:18545): WARNING **: Unable to initialize OBEX
source
** (gnome-obex-server:18545): WARNING **: Couldn't initialise OBEX
listener
Does anyone know what to do?
Regards,
Steffen
reply other threads:[~2012-08-30 10:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=503F3AE2.2040800@tu-ilmenau.de \
--to=steffen.becker@tu-ilmenau.de \
--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).