[Solved] Bluetooth File Transfer not working in antiX 21…

[Member rfinco]

I think I’ve found an issue with Bluetooth in antiX 21

A situation came up where I would need to transfer a file from my tablet to a laptop or cell phone away from any other kind of support. Bluetooth seemed to be ideal for this, and I wanted to assure that I understood the Bluetooth file transfer process by performing the operation between my Samsung Android Tab 10.1 and a laptop with antiX 21 installed.

I tried several times to transfer a small (9MB) .mp4 file from the tablet to the laptop. The tablet and laptop were able to pair OK, but the file transfer attempt kept failing with the following error message at the tablet:

Connection failed!
Unable to start Service Discovery

After failing several times to transfer a file from the tablet to the laptop, I decided to try transferring a file from the laptop to the tablet. That attempt also failed with the following error message at the laptop:

Error occured
name org.bluez.obex was not provided by any .service files

After concluding that I may not be doing something wrong, I tried a couple of other distros (antiX 19 and MX Linux 21) in live sessions, both of which were able to transfer files using Bluetooth OK.

In the previously mentioned “situation”, I was able to transfer the .mp4 file from my tablet to another person’s cell phone without any problem. I guess nobody else has a need to use antiX 21 for Bluetooth file transfer, but things should work, so I thought it worth putting on the table.

Here’s what my laptop looks like:

$ inxi -v 5
System:
  Host: ao722 Kernel: 5.10.57-antix.1-amd64-smp x86_64 bits: 64 
  compiler: gcc v: 10.2.1 Desktop: IceWM 2.9.5 
  Distro: antiX-21_x64-full Grup Yorum 31 October 2021 
  base: Debian GNU/Linux 11 (bullseye) 
Machine:
  Type: Laptop System: Acer product: AO722 v: V1.06 
  serial: <superuser required> 
  Mobo: Acer model: JE10-BZ serial: <superuser required> BIOS: Acer v: 1.06 
  date: 09/19/2011 
Battery:
  ID-1: BAT1 charge: 45.3 Wh (100.0%) condition: 45.3/48.8 Wh (92.7%) 
  volts: 12.1 min: 11.1 model: Sanyo AL10A31 status: Full 
Memory:
  RAM: total: 3.57 GiB used: 486.6 MiB (13.3%) 
  RAM Report: 
  permissions: Unable to run dmidecode. Root privileges required. 
CPU:
  Info: Dual Core model: AMD C-60 APU with Radeon HD Graphics bits: 64 
  type: MCP arch: Bobcat rev: 0 cache: L2: 512 KiB 
  flags: lm nx pae sse sse2 sse3 sse4a ssse3 svm bogomips: 3990 
  Speed: 1145 MHz min/max: 800/1000 MHz boost: enabled Core speeds (MHz): 
  1: 1145 2: 1283 
Graphics:
  Device-1: AMD Wrestler [Radeon HD 6290] vendor: Acer Incorporated ALI 
  driver: radeon v: kernel bus-ID: 00:01.0 
  Device-2: Chicony 1.3M Webcam type: USB driver: uvcvideo bus-ID: 2-1:2 
  Display: x11 server: X.Org 1.20.11 driver: loaded: ati,radeon 
  unloaded: fbdev,modesetting,vesa resolution: 1366x768~60Hz 
  OpenGL: 
  renderer: AMD PALM (DRM 2.50.0 / 5.10.57-antix.1-amd64-smp LLVM 11.0.1) 
  v: 3.3 Mesa 20.3.5 direct render: Yes 
Audio:
  Device-1: AMD Wrestler HDMI Audio vendor: Acer Incorporated ALI 
  driver: snd_hda_intel v: kernel bus-ID: 00:01.1 
  Device-2: AMD SBx00 Azalia vendor: Acer Incorporated ALI 
  driver: snd_hda_intel v: kernel bus-ID: 00:14.2 
  Sound Server-1: ALSA v: k5.10.57-antix.1-amd64-smp running: yes 
Network:
  Device-1: Qualcomm Atheros AR8152 v2.0 Fast Ethernet 
  vendor: Acer Incorporated ALI driver: atl1c v: kernel port: 2000 
  bus-ID: 06:00.0 
  IF: eth0 state: down mac: dc:0e:a1:08:cc:91 
  Device-2: Broadcom BCM4313 802.11bgn Wireless Network Adapter 
  vendor: Foxconn driver: wl v: kernel port: 2000 bus-ID: 07:00.0 
  IF: wlan0 state: up mac: 60:d8:19:7f:d4:39 
Bluetooth:
  Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) type: USB 
  driver: btusb v: 0.8 bus-ID: 1-3.1:3 
  Report: hciconfig ID: hci0 rfk-id: 2 state: up address: 00:1A:7D:DA:71:13 
  bt-v: 2.1 lmp-v: 4.0 
Drives:
  Local Storage: total: 447.13 GiB used: 7.08 GiB (1.6%) 
  ID-1: /dev/sda vendor: Kingston model: SQ500S37480G size: 447.13 GiB 
  Message: No optical or floppy data found. 
Partition:
  ID-1: / size: 97.87 GiB used: 6.1 GiB (6.2%) fs: ext4 dev: /dev/sda1 
  label: rootantiX21 uuid: 92835424-de94-43be-9deb-cb18bb9ee6fa 
Swap:
  ID-1: swap-1 type: partition size: 2 GiB used: 0 KiB (0.0%) dev: /dev/sda2 
  label: N/A uuid: 21bfb7f5-7298-4381-a8ab-dc13eb916d1f 
Sensors:
  System Temperatures: cpu: 66.1 C mobo: N/A gpu: radeon temp: 66.0 C 
  Fan Speeds (RPM): N/A 
Info:
  Processes: 145 Uptime: 1h 23m Init: SysVinit runlevel: 5 Compilers: 
  gcc: 10.2.1 Packages: 1656 Shell: Bash v: 5.1.4 inxi: 3.3.06 

• This topic was modified 1 year, 2 months ago by Brian Masinick. Reason: SOLVED

[Moderator Brian Masinick]

Helpful

Up

0

::

I’ve had on and off problems with various Bluetooth features too, but it’s not limited to just antiX; I have mixed results elsewhere too. Sometimes it works, sometimes it doesn’t, and I’ve not had a lot of success isolating a consisent, reproducible reason, especially since SOMETIMES it works!

If you ARE having success with one distribution, I’d suggest using that distribution, but if you ARE interested in helping out, if you can come up with a reproducible set of scenarios which always fail AND decent logs, proving precisely what happens, it may be possible to file defect reports with the upstream source. I’m really not positive it’s an antiX issue, though it could be the combination of binaries and libraries that we offer that do not function well with the utilities. Anyway, some definitive diagnostics, sent and followed up with the right people might help -I would have done this a long time ago, but the failure to get consistent, reproducible failing scenarios prevented me from sending in a useful defect report.

--
Brian Masinick

[Member olsztyn]

Helpful

Up

0

::

rfinco wrote:

I tried a couple of other distros (antiX 19 and MX Linux 21) in live sessions, both of which were able to transfer files using Bluetooth OK.

Sounds this clearly shows that something is missing in antiX 21 to support Bluetooth transfer.

@rfinco:
Is the failure on antiX traditionally installed or Live? If it is on traditionally installed antiX 21 and Live antiX 19 works fine, I would just attempt the same using antiX Live 21, just to narrow down…

Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

[Member rfinco]

Helpful

Up

0

::

Hello Brian and olsztyn,

Thanks for getting back with me quickly.

Good call on trying antiX 21 live. It does the Bluetooth file transfer OK.

I installed antiX 19 on a spare PC, and (as expected), it does the file transfer OK too.

Here’s what I have:

All of the distros that I tried worked OK, except for the installed version of antiX 21. The distros that work are (antiX 19[installed and live], antix 21[live], MX Linux 21[installed and live]).

Digging a little deeper, I found that all of the distros, except the installed antiX 21, had the file “/usr/share/dbus-1/services/org.bluez.obex.service”, as suggested by the error message when the PC to tablet transfer failed.

Apparently, there is some part of the OBEX service that doesn’t get installed when antiX 21 is installed.

[Moderator caprea]

Helpful

Up

0

::

I think you are right, there seems to be a problem with the bluez-obexd version.

On the live-usb it’s 5.55-3.1 (works properly)
after update it is 5.55-3.1.0antix1 , which doesn’t install the /usr/share/dbus-1/services/org.bluez.obex.service file, which you already mentioned.

[Forum Admin anticapitalista]

Helpful

Up

0

::

I’ll repackage it as soon as possible – good catch caprea!

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Moderator caprea]

Helpful

Up

0

::

It is definitely the merit of rfinco, so thank you very much for taking a closer look at it.

[Member rfinco]

Helpful

Up

0

::

Hello caprea and anticapitalista,

caprea: Thank you very much for confirming the problem.

anticapitalista: When the repackaging has been completed, will the fix be available via (normal update, version point release, re-install, etc.)?

Thanks..

[Forum Admin anticapitalista]

Helpful

Up

0

::

normal update

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Member rfinco]

Helpful

Up

0

::

Hello anticapitalista,

Thanks for the quick response.

I update regularly, so after I am able to do a Bluetooth file transfer, I’ll mark this issue [Solved].

[Forum Admin anticapitalista]

Helpful

Up

0

::

rfinco wrote:

Hello anticapitalista,

Thanks for the quick response.

I update regularly, so after I am able to do a Bluetooth file transfer, I’ll mark this issue [Solved].

Let’s hope the update manages to fix it!
Thanks for your posts to get it fixed.

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Moderator Brian Masinick]

Helpful

Up

0

::

caprea wrote:

I think you are right, there seems to be a problem with the bluez-obexd version.

On the live-usb it’s 5.55-3.1 (works properly)
after update it is 5.55-3.1.0antix1 , which doesn’t install the /usr/share/dbus-1/services/org.bluez.obex.service file, which you already mentioned.

Thank you for this detail! I was fumbling around trying to figure out what was wrong in the implementations that did not work.
(antiX is NOT the only distribution that has experienced defects with Bluetooth, but thanks to this, we should have ours working properly)!

--
Brian Masinick

[Member olsztyn]

Helpful

Up

0

::

anticapitalista wrote:

I’ll repackage it as soon as possible – good catch caprea!

I think anticapitalista just posted the fixed modules… I cannot confirm if working fine as I am running Live and rfinco confirmed already that Live worked fine for him, just traditionally installed did not…

Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

[Member rfinco]

Helpful

Up

0

::

I updated 2 PCs with antiX 21 installed using the normal APT update, 1 64bit and 1 32bit. There were several Bluetooth files in the updates of both PCs.

After updating, I was able to successfully perform Bluetooth file transfer in both directions on both the 32bit and 64bit PCs.

Thank you guys very much for your quick response and getting this problem fixed.

I’ll mark this problem [Solved], if I can figure out how to edit the title.

[Author]

Posts