Bluetooth for KDE in Porteus 5.0

[rchase]

I built this module out of the packages listed as runtime dependencies of https://github.com/blueman-project/bluemannot found in Porteus 5.0rc1 xfce. It doesn't seem to do anything in xfce (when I included the packages listed as necessary to build blueman as well, both blueman and "bluetooth adapters" showed up as applications, but neither would run), but when included in /modules of Porteus kde, I am able to find, connect to, and use a bluetooth headset on my Kangaroo (z8500-based PC with integral bluetooth). How can I get this to work in xfce?

Bluetooth for KDE:
http://www.mediafire.com/file/1lw789xoz ... 1.xzm/file

[jssouza]

rchase, blueman is not necessary for KDE, because KDE already has bluez, bluez-qt and bluedevil packages installed.

Code: Select all

[guest:~]$ ls /var/lib/pkgtools/packages/blue*
/var/lib/pkgtools/packages/bluedevil-5.15.5-x86_64-1jss
/var/lib/pkgtools/packages/bluez-5.50-x86_64-2
/var/lib/pkgtools/packages/bluez-qt-5.58.0-x86_64-1jss

You can either start bluetooth from the menu or you can use the "bluetooth" cheatcode to start bluetooth during bootup.

[rchase]

rchase, blueman is not necessary for KDE, because KDE already has bluez, bluez-qt and bluedevil packages installed.
...
You can either start bluetooth from the menu or you can use the "bluetooth" cheatcode to start bluetooth during bootup.

Except that doesn't work -- no bluetooth adapters are found; my module may include redundant packages, but bluetooth does not work without it loaded. I think there should be bluetooth support across the board -- I particularly want a bluetooth module for xfce. I'll reassemble this module without the redundant packages and upload that.

[ncmprhnsbl]

my module may include extraneous packages,

libnm-qt-0.9.8.4-x86_64-1 wouldn't be needed for blueman ... strange things sometimes get pulled in..

i'll have a look at making blueman for xfce

[jssouza]

Seems what is missing, is the documentation to the user to use the bluetooth cheatcode, or to use the bluetooth option from the Porteus Settings Center, if not.

[rchase]

I thought that when I located "Bluetooth Adapters" and it said there weren't any that that could be relied upon. You're right -- KDE supports bluetooth once the daemon is activated; my module must have turned it on. Since I don't want to use KDE, but XFCE, my problem remains; turning on the daimon in XFCE didn't seem to help, regardless of whether or not I activated my module.

[rchase]

my module may include extraneous packages,

libnm-qt-0.9.8.4-x86_64-1 wouldn't be needed for blueman ... strange things sometimes get pulled in..

i'll have a look at making blueman for xfce

libnm is identified as a runtime dependency of blueman at https://github.com/blueman-project/blue ... dencies.md. Thanks -- I'm interested in learning the process myself, but I have had minimal success so far.

[ncmprhnsbl]

fyi libnm is part of the NetworkManager package in porteus
libnm-qt is some qt bindings for it

and BLUETOOTH (Post by ncmprhnsbl #74885)

[evergreen]

I did it work, with this packages selection for Porteus 5 xfce. Maybe it's useful if someone will make a module with everything.

./ignis/bluetooth/dbus-python-1.2.8-x86_64-2.xzm
./ignis/bluetooth/pygobject3-3.32.2-x86_64-1.xzm
./ignis/bluetooth/gobject-introspection-1.60.2-x86_64-1.xzm
./ignis/bluetooth/bluez-firmware-1.2-x86_64-2.xzm
./ignis/bluetooth/bluez-5.50-x86_64-2.xzm
./ignis/bluetooth/blueman-2.0.8-x86_64-2.xzm

[ncmprhnsbl]

shouldn't need bluez since it's included in 002-xorg .. bluez-firmware could be handy tho .. didn't appear to need it for my hardware..

[evergreen]

Good to know that bluez it's included in 002-xorg, I know now to fix it to my next build... May be I didnt notice that is included now because In Porteus 4 xfce, bluez was missing.

Thanks

[ncmprhnsbl]

pretty sure bluez was in 4.0 too

[evergreen]

In any case this doesn't have sense that bluez is included in the previous or in the actual release if we are not allowed to handle our Bluetooth device because there are missing some packages. So I couldn't connect before according this thread and I fixed it in my way. I can understand that the reason is to keep Porteus clean and small but we wasn't with a solution before. Thanks
Lenovo S41-35

pretty sure bluez was in 4.0 too