NEW puppybt + bluez-tray + bluez5

[Pro]

On Puppy Tahr 6.0.6 64bit using puppybt-5.7-bluez5.50_64-pr01.sfs

Example for start system session
dbus-uuidgen --ensure
dbus-daemon --system

[tenochslb]

pro

Example for start system session
dbus-uuidgen --ensure
dbus-daemon --system

command:

Code: Select all

dbus-uuidgen --ensure

no problem,

however, the command;

Code: Select all

root# dbus-daemon --system
Failed to start message bus: The pid file "/var/run/dbus/dbus.pid" exists, if the message bus is not running, remove this file 

If I erase the file mentioned, dbus-daemon --system works but puppybt continues to fail.

[Pro]

pro
If I erase the file mentioned, dbus-daemon --system works but puppybt continues to fail.

in my system exist file /var/run/dbus/system_bus_socket

May be for testing you commented string 14 in script puppybt?
Also good test from root:
killall bluetoothd
bluetoothd
if no errors - dbus session work good and my check not need.

[tenochslb]

In my system exist file /var/run/dbus/system_bus_socket

I also have the file /var/run/dbus/system_bus_socket.

May be for testing you commented string 14 in script puppybt?

I commented out line 14 as you suggested and now the feedback from terminal is this,

Code: Select all

root# puppybt 
bluetoothd: /lib/libdbus-1.so.3: no version information available (required by bluetoothd)
D-Bus setup failed: Failed to connect to socket /var/run/dbus/system_bus_socket: Connection refused
Failed to open connection to "system" message bus: Failed to connect to socket /var/run/dbus/system_bus_socket: Connection refused
Scanning ...
Failed to open connection to "system" message bus: Failed to connect to socket /var/run/dbus/system_bus_socket: Connection refused
Failed to open connection to "system" message bus: Failed to connect to socket /var/run/dbus/system_bus_socket: Connection refused
Failed to open connection to "system" message bus: Failed to connect to socket /var/run/dbus/system_bus_socket: Connection refused
/usr/bin/puppybt: line 462: 25357 Terminated              gtkdialog -c --program=process
0

[/quote]

[Pro]

Failed to open connection to "system" message bus: Failed to connect to socket /var/run/dbus/system_bus_socket: Connection refused

puppybt run from root?

[tenochslb]

puppybt run from root?

Yes, always as root.

[Pro]

Failed to open connection to "system" message bus: Failed to connect to socket /var/run/dbus/system_bus_socket: Connection refused

may be need restart dbus for read /etc/dbus-1/system.d/bluetooth.conf
I launch Tahr 6.0.5 virtual machine, use command

Code: Select all

/etc/init.d/messagebus reload

for load config /etc/dbus-1/system.d/bluetooth.conf


you load puppybt.sfs on system boot, or use manual load sfs?

[Pro]

FOR ALL MAINTEINER:
1. I think it's better to load sfs at system startup. sfs have udev rules and startup script /etc/xdg/autostart/bluetooth.desktop for autostart tray applet. For ROX panel may be need change autostart method.
2. The structure of the module will vary slightly for different distributions. This is normal because the location of the files in different distributions is different (for example /lib/udev or /usr/lib/udev)

[gyro]

I'm running upupbb 18.05.

I got "puppybt" to run but I could not get it to pair with my bluetooth mouse.

I edited "puppybt" to change line 14 from

Code: Select all

[ -e /run/dbus/system_bus_socket ]

to

Code: Select all

[ -e /var/run/dbus/system_bus_socket ]

.

I ran "bluetooth.sh", it seemed to run to completion, but it produced no output.
I then ran "puppybt".

A "scanning" thingy appeared on the screen, and it seemed to find something but neither "pair" button produced a sucessful pair.

gyro

[Pro]

I'm running upupbb 18.05.

I got "puppybt" to run but I could not get it to pair with my bluetooth mouse.

sorry i dont now way for connect mouse via bluez5, may be you send me screen puppybt with recognized mouse and bluetoothctl info you_mac_moise

I think that the mouse should be connected automatically at boot time and the configuration should be done only once. We will strive for this, in the script bluetooth.sh reserved string for connect hid (mouse, keyboard etc.).

I edited "puppybt" to change line 14 from

i change script on github, line 14 not need how.

Code: Select all

I ran "bluetooth.sh", it seemed to run to completion, but it produced no output. 

this script for launch applet on start panel ex. Lxpanel. Not needed for puppybt.

[gyro]

sorry i dont now way for connect mouse via bluez5, may be you send me screen puppybt with recognized mouse and bluetoothctl info you_mac_moise

Thanks for the reply.
Unfortunately it's not a high priority for me at the moment, and I need to research bluetoothctl. So it may be a little while before I get back with more info.

gyro

[gyro]

Ok, I got puppybt to recognise, pair, and connect to my Logitech M337 bluetooth mouse. And the mouse works fine.
The difference is that I unpaired it from Windows 8, on the same machine, before I tried it on Puppy.

But when I reboot, I've got to manually run puppybt and connect to the mouse again.
How do I get it to automatically connect on reboot?

gyro

[gyro]

But when I reboot, I've got to manually run puppybt and connect to the mouse again.
How do I get it to automatically connect on reboot?

Well I sorted this too.
I appended "AutoEnable=true" to /etc/bluetooth/main.conf.
And I made a symbolic link from /usr/bin/bluetooth.sh to /root/Startup/bluetooth.sh.

On reboot, I get a blue bluetooth icon in my tray, and my bluetooth mouse works.

gyro

[Pro]

Jwm not use xdg? I launch bluetooth.sh from /etc/xdg/autostart/ this way work for all standart desktop.

Thanks you, i change main.conf and enable option by default

[gyro]

Jwm not use xdg? I launch bluetooth.sh from /etc/xdg/autostart/ this way work for all standart desktop

No, it does not, at least it doesn't in the Puppies I use, e.g. xenialpup, upupbb.
gyro

[gyro]

After getting my bluetooth mouse to work, my wifi became very slow and flaky.
Apparently this is a known problem with some wifi drivers.
It is reported that the interference is caused by bluetooth and wifi competing for the 2.4GHz wireless.
Fortunately my local wifi acces point (router) provides a network in both 2.4GHz and 5GHz bands.
So I re-configured the laptop to connect to the 5GHz network, problem solved.

gyro

[perdido]

http://murga-linux.com/puppy/viewtopic. ... 90#1015390

it's for bluez4 or bluez5?

I do something like this, maybe it will be useful for you
http://murga-linux.com/puppy/viewtopic.php?t=111331

This looks interesting, will report back.
Thank You

.

[Pro]

.

[perdido]

Thanks for your interest from the other thread.

Report back - no success
Computer Dell E6400 XFR
Bluetooth device(s)
0a5c:5800 Broadcomm BCM2046B1 USB Hub part of BCM2046 Bluetooth I always see this device every boot -{in output from lsusb}
413c:8187 Dell DW375 Bluetooth Module I only see this device when using some versions of bluez 4.xx -{in output from lsusb}
(these two devices are the integrated bluetooth, it is really only one component)

Using upupbb-18.05 bionic beaver (32-bit) Running as ~root
Installed the puppybt-5.7-bluez5.50-pr01.sfs
Installed the Devx
Installed ntf-0.9-any package

Launched puppybt
Got the following error
"Dbus "System" session not started'
check your Dbus launch script or service"

Tried the following commands
-----
dbus-uuidgen --ensure
dbus-daemon --system
-----

Also tried editing puppybt line 14
first time commented out
second time tried changes suggested by gyro -
edited "puppybt" to change line 14 from
Code:
[ -e /run/dbus/system_bus_socket ]
to
Code:
[ -e /var/run/dbus/system_bus_socket ]

Ran bluetooth.sh
Killall found no processes to kill

Tried to launch puppybt again
Got the following error
"Error
Local bluetooth device not found"
- --̶ ̶-̶L̶o̶o̶k̶s̶ ̶l̶i̶k̶e̶ ̶t̶h̶e̶ ̶D̶b̶u̶s̶ ̶s̶e̶s̶s̶i̶o̶n̶ ̶i̶s̶ ̶s̶t̶a̶r̶t̶e̶d̶ ̶n̶o̶w̶!̶-̶ ̶-̶ ̶- -
-------------------------------------------------------
I have never seen the 413c:8187 Dell DW375 bluetooth device listed in lsusb when trying any version of bluez 5.xx
I have seen the 413c:8187 Dell DW375 listed in lsusb when trying some versions of bluez 4.xx

There are problems with this bluetooth device, there are problem reports all over the internet.
https://linux-hardware.org/index.php?id=usb:413c-8187


.

[Pro]

-------------------------------------------------------
I have never seen the 413c:8187 Dell DW375 bluetooth device listed in lsusb when trying any version of bluez 5.xx
I have seen the 413c:8187 Dell DW375 listed in lsusb when trying some versions of bluez 4.xx

check lsmod or dmesg (btusb, bluetooth kernel module launched?)
lsusb not guarantee that the device works!

bluetooth.sh - script for autolaunch with xorg starts, run only puppybt for testing.
Check update puppybt from github, i not upload latest module because I need to solve the problem with simple pair device.