Hello

I can't seem to get my bluetooth USB Dongle working. I'd like to be able to send & receive files from my mobile fone.

When trying to connect it I get the following error messages:

' Failed to connect to the SDP server.

Please make sure that sdpd is running;
without it, other devices will not be able to find out
which services your computer offers. '

Can someone please help?

I need to know how to connect to this ' SDP server ' so my bluetooth device is recognized.

I'm running Mepis 6.0 on x86 AMD Athlon machine with 486mb Ram.

Thanks

Well, you need sdpd (sdp daemon) to be running. Fire up a console (konsole, gnome-terminal, what have you), su to root, and then try running sdpd, /etc/init.d/sdpd. If neither one works you will have to install the sdp daemon. I believe mepis uses apt? If so, apt-get install sdpd might do the trick.

Once that's running, try the bluetooth again. Bluetooth was rather tricky to setup, but lots of fun to play with

Hi, I tried apt-get install sdpd but get this message in konsole 'Couldn't find package sdpd'

When I tried to run sdpd using /etc/init.d/sdpd, it says no such file or directory exists.

any other suggestions please?

Are you running debian? ubuntu?

try apt-getting bluez-sdp.

root@1[shahid]# apt-get install bluez-sdp
Reading package lists... Done
Building dependency tree... Done
Package bluez-sdp is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
bluez-utils
E: Package bluez-sdp has no installation candidate

Hmm? sounds like theirs a similar package already existing. I really don't know what to do with this..

Someone please help! I'm running Mepis 6.0

this means that the sdpd program is in the bluez-utils package. Try installing that one, then look for your sdp program.

root@1[shahid]# apt-get install bluez-utils
Reading package lists... Done
Building dependency tree... Done
bluez-utils is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
root@1[shahid]#

Sounds like thats also already installed, but why can't I still find SDPD?

OK, I'm stumped -- my last thought is that your path isn't right.

I'm on a stock debian system, also with bluez-utils already installed, and sdpd is located at /usr/sbin/sdpd

How are you logging in as root? Maybe your env isn't being updated and /usr/sbin isn't in your path? Being debian based, I think the packages for Mepis ought to be similar, if not identical, to the stock debian packages.

Edit:
Try if you don't find sdpd in /usr/sbin

I was logging in as root as su. Mepis is an awesome linux operating system, but i just couldn't get bluetooth working for some reason & I could have actually lived without it but hated having to boot into XP.

I've now wiped my Mepis 6.0 install and replaced it with kubuntu at first which was nice, but involved too much configuring although bluetooth just worked on kubuntu.

Have erased Kubuntu 6.10 & replaced with Suse 10.2 which is absolutely beautiful to work in, haven't tested my bluetooth on that yet but will later & i'm sure it'll work fine.

But goodbye to Mepis I still think its a great operating system, very nice indeed.

I'll see how i go with Suse for a while now.

Thanks to everyone who contributed to this thread without your help I'd be hopeless & stuck!

Best Wishes
Shahid

Well, I just have to say, you shouldn't have changed distros.
You would have had much more satisfaction when you finally figured out how to use bluetooth in Mepis. My opinion on SUSE, well, I won't go there.

SUSe, IMHO is a great distro for newbies and people who love eye candy and hate the terminal (and those afraid of M$ lawsuits).

If something is too much work, what's wrong with switching distros? I believe wholeheartedly that you would have gotten more satisfaction out of making it work, johngreenwood, but that's just not for everyone.

So what you are saying is, bluetooth is too hard to get working on distro1, so you switch to distro2. With distro2 bluetooth is working fine, but you can't get your printer to work, so you go to distro3, printer works fine in distro3, but bluetooth doesn't, but you need your printer more so you make the compromise. Then you realise that distro3 just keeps crashing all the time, so next is distro4, where nothing works but it doesn't crash.

Is that what you are saying? That when you need to use bluetooth you install a distro, then for printer you install another distro, etc.

Well, there is always dual (or more) booting.

It looks like sdpd is not longer used. Invoking

hcid -s

can be used to enable the internal SDP server,
and at least for me the problem seems to be solved.