Bluetooth does little when clicked on from menu.In terminal 'Command not found'.
Blueman-adaptors is found in usr/share/applications but not in menu and also does nothing when clicked.
Quite important in this day and age.
Moderator: Forum moderators
Bluetooth does little when clicked on from menu.In terminal 'Command not found'.
Blueman-adaptors is found in usr/share/applications but not in menu and also does nothing when clicked.
Quite important in this day and age.
@Tahrbaby Oh no...looks like we'll need to pull F96 from the shelf for now. The Bluetooth features were working but I do not have any really intense way of testing out the Bluetooth connectivity. This failure will be looked into.
rockedge wrote: Tue Jan 31, 2023 1:34 pm@Tahrbaby Oh no...looks like we'll need to pull F96 from the shelf for now. The Bluetooth features were working but I do not have any really intense way of testing out the Bluetooth connectivity. This failure will be looked into.
Always possible it could just be down to my PC?
Its an Acer Aspire X Desktop with onboard Bluetooth.
Desktop, Intel 4 core, 4gb ram, using cheap Chinese USB Bluetooth v2.0 adapter.(working on MS W10)
-Menu>System>Bluetooth Manager
Opens bluetooth and will pair & connect with bluetooth speaker and play, only finds one of my phones and will not do file transfers.
Getting bluetooth notifications across the top of the screen
With that said, I've always found bluetooth to be a hassle and I always have trouble finding which device will work with which device. Think maybe is related to hardware, BT version and drivers no matter if it is MS Windows, LInux, or Android.
Thanks
wizard
Big pile of OLD computers
Based on Tahrbaby's statement that bluetooth is working on VanillaDpup, I loaded v9.3.6 on my same hardware.
Sure enough it finds, pairs, and connects to my devices.
BT speaker = OK, plays
Samsung S5 phone = OK, file transfers both directions = OK
Latest version of F96-CE fails on file transfers
Thanks
wizard
Big pile of OLD computers
@wizard Vanilla Dpup was nominated to be the next official Puppy, but that was declined by it's creator it seems.
There is a revision F96-CE being worked on to address and fix some more of the problems, like Bluetooth.
I have not tried to connect an Android device yet.
Vanilla Dpup was nominated to be the next official Puppy, but that was declined by it's creator it seems.
Yes, I followed the tread and saw that dimkr did not consider it qualified as an official Puppy. In my brief tryout, it lacks a lot of the programs, usability and ease of use that is in F96. It's good work, but pretty stripped down at this point.
Looking for differences between the BT functions here's what I've found:
F96 = Blueman v2.1.2
VDP = Blueman v2.1.4
Attached are the contents of the Blueman device info files. Hope it might offer clues.
Thanks
wizard
Big pile of OLD computers
wizard wrote: Thu Feb 02, 2023 7:20 pm@radky
@rockedge
@TahrbabyBased on Tahrbaby's statement that bluetooth is working on VanillaDpup, I loaded v9.3.6 on my same hardware.
Sure enough it finds, pairs, and connects to my devices.
BT speaker = OK, plays
Samsung S5 phone = OK, file transfers both directions = OKLatest version of F96-CE fails on file transfers
Thanks
wizard
Thank you for confirming this.
It would be worth it to attempt a bump up in version to Blueman v2.1.4 and see if it can smooth out and become more reliable.
Downloaded a 2.1.4 deb package and installed it, file transfer still fails. Something still missing.
Thanks
wizard
Big pile of OLD computers
I think F96 uses blueman_2.1.2-1 from the ubuntu-focal-universe repository, but the package is modified by Woof-CE.
Specifically, /usr/bin/blueman-applet and /usr/bin/blueman-manager are modified to allow blueman to run as spot in Puppy. An unmodified upgrade of blueman would not conform to the Puppy configuration.
Maybe dimkr could help us resolve the Bluetooth issue in F96.
@radky Try this:
@wizard If you confirm that fixing the service file followed by reboot fixes file transfer using Blueman, I can integrate this fix into woof-CE.
dimkr wrote: Mon Feb 06, 2023 6:32 am@radky Try this:
cat /usr/share/dbus-1/services/org.bluez.obex.service
Code: Select all
[D-BUS Service] Name=org.bluez.obex Exec=/usr/lib/bluetooth/obexd SystemdService=dbus-org.bluez.obex.service
@wizard If you confirm that fixing the service file followed by reboot fixes file transfer using Blueman, I can integrate this fix into woof-CE.
@dimkr
Thanks for the fix of /usr/share/dbus-1/services/org.bluez.obex.service.
I don't use bluetooth devices, so can't effectively test but I'm sure @Tahrbaby, @wizard and other bluetooth users will test and report soon.
Thanks again !
Ran the command, but my output came back a little different.
File transfer=no
Rebooted,
File transfer=no
Thanks
wizard
Big pile of OLD computers
wizard wrote: Mon Feb 06, 2023 10:35 pmRan the command, but my output came back a little different.
Code: Select all
[D-BUS Service] Name=org.bluez.obex Exec=@libexecdiir@/obexd SystemdService=dbus-org.bluez.obex.service
File transfer=no
Rebooted,
File transfer=noThanks
wizard
@wizard
@dimkr changed the third line.
Try editing the third line in /usr/share/dbus-1/services/org.bluez.obex.service as follows, then reboot.
Code: Select all
[D-BUS Service]
Name=org.bluez.obex
Exec=/usr/lib/bluetooth/obexd
SystemdService=dbus-org.bluez.obex.service
Thanks
radky wrote: Mon Feb 06, 2023 11:07 pmwizard wrote: Mon Feb 06, 2023 10:35 pmRan the command, but my output came back a little different.
Code: Select all
[D-BUS Service] Name=org.bluez.obex Exec=@libexecdiir@/obexd SystemdService=dbus-org.bluez.obex.service
File transfer=no
Rebooted,
File transfer=noThanks
wizard@wizard
@dimkr changed the third line.
Try editing the third line in /usr/share/dbus-1/services/org.bluez.obex.service as follows, then reboot.
Code: Select all
[D-BUS Service] Name=org.bluez.obex Exec=/usr/lib/bluetooth/obexd SystemdService=dbus-org.bluez.obex.service
Thanks
Tried all of the above methods but still Bluetooth won't start for me.
Tahrbaby wrote: Tue Feb 07, 2023 8:39 amTried all of the above methods but still Bluetooth won't start for me.
Have you modified /usr/share/dbus-1/services/org.bluez.obex.service? Did you reboot after the modification?
EDIT: try to run blueman-applet
and blueman-manager
in the terminal - what does it say? Also, you can try to run bluetoothctl
, then type devices
to see if any Bluetooth devices are available.
OK, lack of understanding by me. Dimkr's post was to say:
Edit the file:
/usr/share/dbus-1/services/org.bluez.obex.service
To read:
Code: Select all
[D-BUS Service]
Name=org.bluez.obex
Exec=/usr/lib/bluetooth/obexd
SystemdService=dbus-org.bluez.obex.service
-reboot
When I did this it works. File transfer=OK
Thanks
wizard
Big pile of OLD computers
Thanks @wizard, I will test https://github.com/puppylinux-woof-CE/woof-CE/pull/3890 soon, then merge it to ensure this problem doesn't return.
@dimkr
I don't have bluetooth devices to actually test functionality, file transfer, etc.
However, the following output on F96-CE may be helpful.
First, I modified /usr/share/dbus-1/services/org.bluez.obex.service as follows, then rebooted:
Code: Select all
[D-BUS Service]
Name=org.bluez.obex
Exec=/usr/lib/bluetooth/obexd
SystemdService=dbus-org.bluez.obex.service
Second, in a terminal:
Code: Select all
# blueman-applet
blueman-applet version 2.1.2 starting
blueman-applet 10.11.55 WARNING PluginManager:147 __load_plugin: Not loading DhcpClient because its conflict has higher priority
blueman-tray version 2.1.2 starting
blueman-tray version 2.1.2 starting
There is an instance already running
blueman-applet 10.11.57 WARNING PluginManager:147 __load_plugin: Not loading PPPSupport because its conflict has higher priority
blueman-applet 10.11.57 WARNING TransferService:189 _make_share_path: Failed to get Download dir from XDG
(blueman-tray:13135): Gdk-CRITICAL **: 10:11:58.717: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed
Third, in a terminal:
Code: Select all
# blueman-manager
blueman-manager version 2.1.2 starting
Failed to enable bluetooth
EDIT: one additional terminal command
Fourth, in a terminal:
Code: Select all
#bluetoothctl
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/blueman/main/indicators/GtkStatusIcon.py", line 19, in <lambda>
gtk_item.connect('activate', lambda _, idx=index: activate(idx))
File "/usr/lib/python3/dist-packages/blueman/main/Tray.py", line 37, in _activate_menu_item
return AppletService().ActivateMenuItem('(ai)', indexes)
File "/usr/lib/python3/dist-packages/gi/overrides/Gio.py", line 351, in __call__
result = self.dbus_proxy.call_sync(self.method_name, arg_variant,
gi.repository.GLib.Error: g-io-error-quark: Timeout was reached (24)
The Blueman program does have strange behavior that is not user friendly, I will work up a "howto" for review.
Thanks
wizard
Big pile of OLD computers
radky wrote: Tue Feb 07, 2023 4:00 pm@dimkr
I don't have bluetooth devices to actually test functionality, file transfer, etc.
Do you have a Bluetooth adapter that doesn't see any devices or don't have Bluetooth at all?
I have an old (? broken) Bluetooth portable speaker but currently no Bluetooth adapter for my vintage 2010 laptop.
Note: I added results for one additional terminal command (bluetoothctl) in the above post.