From: tmp@nitwit.de
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Error connecting transport
Date: Sun, 27 Mar 2005 18:45:15 +0200 [thread overview]
Message-ID: <200503271845.15263.tmp@nitwit.de> (raw)
Hi!
This happens with the KDE bluetooth OBEX push client so I'm not sure whether
it belongs here. I try to transfer a JAR and get "Error connecting
transport". Well, I have no clue what this is about :) Is it a configuration
fault?
BTW if I click "OBEX FileTransfer" it goes: Could not connect to host xx:xx:..
Thanks
Timo
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next reply other threads:[~2005-03-27 16:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-27 16:45 tmp [this message]
2005-03-27 16:59 ` [Bluez-users] Error connecting transport tmp
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=200503271845.15263.tmp@nitwit.de \
--to=tmp@nitwit.de \
--cc=bluez-users@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox