kbluetooth4 for slackware 13-current
 

Here's a little guide and the slackbuilds for kbluetooth4 and its dependents.

First you are going to have to remove the old bluez-libs and bluez-utils packages. Bluez have merged both these packages into one.

All SlackBuilds have been optimized for x86_64. Change to suit your needs...

UPDATE!!!:
All SlackBuilds have now been fixed. Sorry me rushing things again lol :D
Fixed doinst.sh and SlackBuild in bluez to copy all the configuration files to /etc/bluetooth.
Added libusb-1* udev was not able to start the bluetooth daemon with the old legacy package.

Click here to download the packages.

Please build and install libusb and openobex before trying to compile the other packages.

PS:

You may want to make a symlink to the daemon startup scripts as if you have a internal bluetooth adapter it will initialize before the udev daemon and the bluetooth daemon will fail to load. Alternatively just start the bluetooth daemon from terminal.


Screenshot ..

kdebluetooth4 AFAIK needs updated bluez packages as well as obex-data-server (not yet in Slackware)

Everything is included in the first post. If you would like to try it out let me know how you get on. Cheers

Thanks for the above... This is still something in my 'todo' 'totry' list :)

But why not this app: http://kde-apps.org/content/show.php...content=112110

Not sure, but kdebluetooth seems down for a while. and this looks like a renewed project...

Hey dolphin77,

The link you provided is kbluetooth :D Just noticed there is a newer version, I'll update the package TY :D

I just noticed you are talking about kbluetooth, not kdebluetooth http://kde-apps.org/content/show.php...?content=84761

Hey again sahko. Yes I was talking about kbluetooth sorry I got confused because of the two being so similar.

Its all a bit confusing because there's kdebluetooth, kbluetooth and kbluetooth4 over on gitorious :/

Still both need the bluez-4* and obex packages.

drgr33n:

I mailed you about this. All things considered, not bad at all. I've got a "works for me" bluez4 stack (with blueman, a gtk app) up and running here, so I was curious as to any differences in your stuff and mine. Aside from style issues and a few minor nits here and there, we pretty much arrived to the same place from different directions, and that's a good sign :-)

I don't think it's necessary to have bluetoothd start at boot any more (so no need for rc.bluetooth), but I addressed that in the email, so we can continue this conversation there - I just wanted to offer some public kudos first :-)

Thanks for the scripts!

However, when I run kbluetooth4, I get errors like:
I don't get an icon in the task bar unless I run rc.bluetooth and in that case the icon is just jumbled pixels. No bluetooth devices are ever detected.

I get that same thing here with kbluetooth; that's why I use blueman :-)

I'm not *sure* about this, but *maybe* rebuilding kde with bluez4 installed will fix that. I've had more important things on my TODO list, so I haven't had a chance to find out...

Yikes! No thanks... Do you have a SlackBuild available for blueman?

Good job!

I have tried to get kbluetooth working before but never succeded. Hopefully it will work with your stuff.

/Magnus

rlworkman:

Why not publish working solution (I understood, it is bluez4 + gtk app blueman) on slackbuilds.org?

best regards,
Vladimir

EDIT: oops, you already posted while I was typing. Thank you.

@ rworkman,

EDIT: Sorry rworkman I found your email in my spam folder :( I've mailed you back.

lol we were thinking down the same lines on rc.bluetooth too :D I wasn't sure if it was necessary to add rc.bluetooth to start the daemon at startup ?. I left it as a matter of convenience and lack of testing ;)

@ everyone else

As for the error's I don't know if I will carry on with kbluetooth or also go down the blueman route?. kbluetooth seemed fine on my system but as I'm testing I'm finding more than a few issues as its far from a finished project.

Cheers,

Zarren