UbuntuThis forum is for the discussion of Ubuntu Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I wonder if that's why the right click on file Send to with bluettoth no longer works. I've found that right clickinging the bluetooth applet icon offers a send to that does work. I upgraded from 8.04 and all my pared buetooth devices were carried forward.
I've been trying to do the same thing via fedora 9, and now fedora 10. Same basic problems... the 'hcitool cc' is working, though, the connection just fails immediately. Try this and you'll see:
hcitool cc <bdaddr>; hcitool con
(wait 3 seconds)
It looks like the connection gets established, but then immediately dies. I've been playing with dbus-send and the bluetoothd dbus interface, but I haven't been able to work out a better solution.
Gnome's bluetooth-applet seems to work, which means they must be doing things differently than hcitool. Maybe if we can work out how bluetooth-applet does it, we can craft a CLI script that uses dbus-send to achieve the same result.
I'd like to thank you
for your competent post!
Originally Posted by jpwigan
I've been trying to do the same thing via fedora 9, and now fedora 10. Same basic problems... the 'hcitool cc' is working, though, the connection just fails immediately.
This induces me to suppose
it's a BlueZ bug.
Originally Posted by jpwigan
Gnome's bluetooth-applet seems to work, which means they must be doing things differently than hcitool.
I don't use, now, Gnome, anyway
I totally agree with you.
I tried kbtobexclient and
it seems to bypass the problem
binding rfcomm on channel 5,
so it works (without asking
for a pairing password!!).
Unfortunately if I try to,
manually, bind rfcomm on
channel 5, it asks for
a password, but it doesn't
use nor the default one, nor
the one in pin or bluepin
file in /etc/bluetooth,
so, in the end, it isn't
able to do the pairing.
On further inspection, bluez-4.x is just *weird*... /etc/bluetooth/main.conf is a completely different configuration file, and if there's a place for a default pin, it doesn't seem to be documented.
In addition, gnome's bluetooth-applet *doesn't* work in f10. I jumped the gun on that one. So now, no bluetooth at all for me, even with the gui (and I agree with your approach - I would far prefer to stick with the command line).
I'll continue experimenting with it as time allows. If I discover anything, I'll post it here.