Hi.
Since several updates ago I cannot transfer files by bluetooth. Only call and audio. From other MXlinux installation I can transfer files so it seems the problem is somewhere in the tumbleweed configuration.
Mpow BH456A dongle. Chipset rtl8771 or 8761 for the Mpow driver (outdated from Dec. 2020):
lsusb
Bus 002 Device 003: ID 0bda:8771 Realtek Semiconductor Corp. Bluetooth Radio
[17:27][da@:~]$:inxi -xxx -E
Bluetooth: Device-1: Realtek Bluetooth Radio type: USB driver: btusb v: 0.8 bus-ID: 2-2:4 chip-ID: 0bda:8771
class-ID: e001 serial: 00E04C239987
Report: bt-adapter ID: hci0 rfk-id: 2 state: down bt-service: enabled,running rfk-block: hardware: no
software: yes address: 44:01:BB:A3:82:13
file transfer still not working. Maybe i need to find a working driver, but not sure where because Mpow doesn’t update the driver since 2020.
Thank you.
I installed that .63 version but no systray icon for bluetooth. Looked for blueberry and it’s now in a separated repo. Installed then blueman but file transfers still not working.
systemctl returns some errors:
$ sudo systemctl status bluetooth
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
Active: active (running) since Sun 2022-03-13 10:36:02 GMT; 13min ago
Docs: man:bluetoothd(8)
Main PID: 779 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 4915)
CPU: 399ms
CGroup: /system.slice/bluetooth.service
└─779 /usr/libexec/bluetooth/bluetoothd
Mar 13 10:41:10 localhost.localdomain bluetoothd[779]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 94:7B:E7:01:8F:1C: Permission denied (13)
Mar 13 10:42:17 localhost.localdomain bluetoothd[779]: src/adv_monitor.c:btd_adv_monitor_offload_supported() Manager is NULL, get offload support failed
Mar 13 10:42:17 localhost.localdomain bluetoothd[779]: src/adv_monitor.c:btd_adv_monitor_offload_supported() Manager is NULL, get offload support failed
Mar 13 10:42:17 localhost.localdomain bluetoothd[779]: src/adv_monitor.c:btd_adv_monitor_offload_supported() Manager is NULL, get offload support failed
Mar 13 10:42:17 localhost.localdomain bluetoothd[779]: src/adv_monitor.c:btd_adv_monitor_offload_supported() Manager is NULL, get offload support failed
Mar 13 10:42:17 localhost.localdomain bluetoothd[779]: src/adv_monitor.c:btd_adv_monitor_offload_supported() Manager is NULL, get offload support failed
Mar 13 10:42:18 localhost.localdomain bluetoothd[779]: src/adv_monitor.c:btd_adv_monitor_offload_supported() Manager is NULL, get offload support failed
Mar 13 10:42:18 localhost.localdomain bluetoothd[779]: src/adv_monitor.c:btd_adv_monitor_offload_supported() Manager is NULL, get offload support failed
Mar 13 10:42:21 localhost.localdomain bluetoothd[779]: src/adv_monitor.c:btd_adv_monitor_offload_supported() Manager is NULL, get offload support failed
Mar 13 10:43:41 localhost.localdomain bluetoothd[779]: /org/bluez/hci0/dev_94_7B_E7_01_8F_1C/fd1: fd(30) ready
.
.
I didn’t try to deal with those firmware issues yet.
Thanks.
This is a little mess. Seems obex.service doesn’t exist. But too complicated for me to fix. could be it fixed and leave all the services running? Sometimes you need to transfer files by bluetooth.
[11:16][da@:~]$:sudo systemctl start dbus-org.bluez.obex.service
Failed to start dbus-org.bluez.obex.service: Unit dbus-org.bluez.obex.service not found.
[11:16][da@:~]$:sudo systemctl enable /usr/lib/systemd/user/obex.service
Created symlink /etc/systemd/system/dbus-org.bluez.obex.service → /usr/lib/systemd/user/obex.service.
Created symlink /etc/systemd/system/obex.service → /usr/lib/systemd/user/obex.service.
[11:17][da@:~]$:sudo systemctl start obex.service
Job for obex.service failed because the control process exited with error code.
See "systemctl status obex.service" and "journalctl -xeu obex.service" for details.
[11:17][da@:~]$:systemctl status obex.service
× obex.service - Bluetooth OBEX service
Loaded: loaded (/etc/systemd/system/obex.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Fri 2022-04-08 11:17:38 BST; 30s ago
Process: 31207 ExecStart=/usr/libexec/bluetooth/obexd (code=exited, status=1/FAILURE)
Main PID: 31207 (code=exited, status=1/FAILURE)
CPU: 5ms
$:sudo journalctl -xeu obex.service
░░
░░ A start job for unit obex.service has begun execution.
░░
░░ The job identifier is 7043.
Apr 08 11:17:38 localhost.localdomain obexd[31207]: OBEX daemon 5.64
Apr 08 11:17:38 localhost.localdomain obexd[31207]: manager_init failed
Apr 08 11:17:38 localhost.localdomain obexd[31207]: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
Apr 08 11:17:38 localhost.localdomain systemd[1]: obex.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ An ExecStart= process belonging to unit obex.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Apr 08 11:17:38 localhost.localdomain systemd[1]: obex.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit obex.service has entered the 'failed' state with result 'exit-code'.
Apr 08 11:17:38 localhost.localdomain systemd[1]: Failed to start Bluetooth OBEX service.
░░ Subject: A start job for unit obex.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit obex.service has finished with a failure.
░░
░░ The job identifier is 7043 and the job result is failed.
and what about this:
Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
is it supposed obex should be working by default in tumbleweed because is important?. why in my system are the things messed (for me as a normal user) this way?.
thanks.
$:sudo systemctl start dbus-org.bluez.obex.service
Failed to start dbus-org.bluez.obex.service: Unit dbus-org.bluez.obex.service failed to load properly, please adjust/correct and reload service manager: File exists
See system logs and 'systemctl status dbus-org.bluez.obex.service' for details.
[11:41][da@:~]$:sudo systemctl enable dbus-org.bluez.obex.service
Failed to enable unit: Refusing to operate on alias name or linked unit file: dbus-org.bluez.obex.service
[11:41][da@:~]$:systemctl status dbus-org.bluez.obex.service
○ dbus-org.bluez.obex.service - Bluetooth OBEX service
Loaded: error (Reason: Unit dbus-org.bluez.obex.service failed to load properly, please adjust/correct and reload >
Active: inactive (dead)
Hi.
Could someone who can use blueman to transfer files to his phone (maybe better if a samsung) with no issues leave here a list of services running and related to obex, bluez, and dbus?
Thanks.
As i already stated in post #5 I discovered the same problem as you and my current workaround is to use bluez 5.61 and libell0 0.44 to circumvent that problem.
I was lucky to lock those packages so that I still can use them but I have no idea where you could get those packages from. They are no longer available at https://download.opensuse.org/history/.
However I just searched bugzilla and found this what sounds quite similar to our problem.
And on my system /home is a symlink. So i will try the fix mentioned by the bug-reporter.
$ rpm -q --changelog bluez | grep -C 1 obex
* Tue Nov 23 2021
- Stop nuking the obex service, we support user systemd services
just fine now. Following this, no longer hack the dbus service,
leave it as a systemd service as upstream intended.
- Split out obex in own package with it's needed enabledment as a
systemd user service.
To fix this in TW:
$ sudo zypper in bluez-obex
$ systemctl --user start obex
Auto start doesn’t seem to be working, so a bug report is warranted.
Although in the meantime after installing the latest bluez version I had already discovered that a package bluez-obex was missing and I installed it. But I had not sorted out yet how to get that service started.
Could you please share a link to that bug report so that i can remove my own “auto start mechanism” as soon as the problem is solved?
this instruction that created a symlink from dbus-org.bluez.obex.service to obex.service:
[LEFT]sudo systemctl --global enable obex
or the export DBUS_SESSION_BUS_ADDRESS=/run/user/$(id -u)/bus
because in my system /usr/lib/systemd/user/dbus.socket doesn't look for .../dbus/user_bus_socket but only for bus (in /run/user/1000/)
actually I have duplicate dbus.service and dbus.socket files in these two locations:
/usr/lib/systemd/system/
/usr/lib/systemd/user/
and obex.service is in:
[LEFT][FONT=sans-serif]/usr/lib/systemd/user/[/LEFT][/FONT]
[/LEFT]
hope this helps, and thank you very much to everybody.rotfl!
Now transfer of files to the phone via bluetooth is working properly with bluez 5.64-1.9, blueman 2.2.4-41.1 on xfce 4.16.4 and kernel 5.17.4-1. [size=4]I leave here what I found out after a little researching:
[/size] It seems the only service active and running is bluetooth.service, and dbus-org.bluez.service is a link to it:
[13:03][da@:~]$:sudo systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
Active: active (running) since Wed 2022-05-04 09:02:32 BST; 4h 1min ago
Docs: man:bluetoothd(8)
Main PID: 871 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 4915)
CPU: 1.765s
CGroup: /system.slice/bluetooth.service
└─871 /usr/libexec/bluetooth/bluetoothd
May 04 09:04:15 localhost.localdomain bluetoothd[871]: Endpoint registered: sender=:1.60 path=/MediaEndpoint/A2DPSource>
May 04 09:04:15 localhost.localdomain bluetoothd[871]: Endpoint registered: sender=:1.60 path=/MediaEndpoint/A2DPSource>
May 04 09:04:15 localhost.localdomain bluetoothd[871]: Endpoint registered: sender=:1.60 path=/MediaEndpoint/A2DPSource>
May 04 09:04:15 localhost.localdomain bluetoothd[871]: Endpoint registered: sender=:1.60 path=/MediaEndpoint/A2DPSource>
May 04 09:04:15 localhost.localdomain bluetoothd[871]: Endpoint registered: sender=:1.60 path=/MediaEndpoint/A2DPSource>
May 04 09:04:15 localhost.localdomain bluetoothd[871]: Endpoint registered: sender=:1.60 path=/MediaEndpoint/A2DPSource>
May 04 09:04:15 localhost.localdomain bluetoothd[871]: Endpoint registered: sender=:1.60 path=/MediaEndpoint/A2DPSource>
May 04 09:57:18 localhost.localdomain bluetoothd[871]: /org/bluez/hci0/dev_94_7B_E7_01_8F_1C/sep1/fd0: fd(40) ready
May 04 09:58:37 localhost.localdomain bluetoothd[871]: src/profile.c:ext_io_disconnected() Unable to get io data for He>
May 04 12:19:40 localhost.localdomain bluetoothd[871]: /org/bluez/hci0/dev_94_7B_E7_01_8F_1C/sep1/fd1: fd(40) ready
[13:03][da@:~]$:sudo systemctl status dbus-org.bluez.service
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
Active: active (running) since Wed 2022-05-04 09:02:32 BST; 4h 1min ago
Docs: man:bluetoothd(8)
Main PID: 871 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 4915)
CPU: 1.785s
CGroup: /system.slice/bluetooth.service
└─871 /usr/libexec/bluetooth/bluetoothd
May 04 09:04:15 localhost.localdomain bluetoothd[871]: Endpoint registered: sender=:1.60 path=/MediaEndpoint/A2DPSource>
May 04 09:04:15 localhost.localdomain bluetoothd[871]: Endpoint registered: sender=:1.60 path=/MediaEndpoint/A2DPSource>
May 04 09:04:15 localhost.localdomain bluetoothd[871]: Endpoint registered: sender=:1.60 path=/MediaEndpoint/A2DPSource>
May 04 09:04:15 localhost.localdomain bluetoothd[871]: Endpoint registered: sender=:1.60 path=/MediaEndpoint/A2DPSource>
May 04 09:04:15 localhost.localdomain bluetoothd[871]: Endpoint registered: sender=:1.60 path=/MediaEndpoint/A2DPSource>
May 04 09:04:15 localhost.localdomain bluetoothd[871]: Endpoint registered: sender=:1.60 path=/MediaEndpoint/A2DPSource>
May 04 09:04:15 localhost.localdomain bluetoothd[871]: Endpoint registered: sender=:1.60 path=/MediaEndpoint/A2DPSource>
May 04 09:57:18 localhost.localdomain bluetoothd[871]: /org/bluez/hci0/dev_94_7B_E7_01_8F_1C/sep1/fd0: fd(40) ready
May 04 09:58:37 localhost.localdomain bluetoothd[871]: src/profile.c:ext_io_disconnected() Unable to get io data for He>
May 04 12:19:40 localhost.localdomain bluetoothd[871]: /org/bluez/hci0/dev_94_7B_E7_01_8F_1C/sep1/fd1: fd(40) ready
and obex.service and dbus-org.bluez.obex.service are enabled but inactive (maybe because they are used by bluetooth.service when are needed):
[13:04][da@:~]$:sudo systemctl status obex.service
○ obex.service - Bluetooth OBEX service
Loaded: loaded (/etc/systemd/system/obex.service; enabled; vendor preset: disabled)
Active: inactive (dead)
[13:07][da@:~]$:sudo systemctl status dbus-org.bluez.obex.service
○ dbus-org.bluez.obex.service - Bluetooth OBEX service
Loaded: loaded (/etc/systemd/system/dbus-org.bluez.obex.service; alias)
Active: inactive (dead)
Hi. Now transfer of files to the phone via bluetooth is working properly with bluez 5.64-1.9, blueman 2.2.4-41.1 on xfce 4.16.4 and kernel 5.17.4-1. [size=4]I leave here what I found out after a little researching:
[/size] It seems the only service active and running is bluetooth.service, and dbus-org.bluez.service is a link to it:
[13:03][da@:~]$:**sudo systemctl status bluetooth.service **
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
Active: **active (running)** since Wed 2022-05-04 09:02:32 BST; 4h 1min ago
Docs: man:bluetoothd(8)
Main PID: 871 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 4915)
CPU: 1.765s
CGroup: /system.slice/bluetooth.service
└─871 /usr/libexec/bluetooth/bluetoothd
May 04 09:04:15 localhost.localdomain bluetoothd[871]: Endpoint registered: sender=:1.60 path=/MediaEndpoint/A2DPSource>
May 04 09:04:15 localhost.localdomain bluetoothd[871]: Endpoint registered: sender=:1.60 path=/MediaEndpoint/A2DPSource>
May 04 09:04:15 localhost.localdomain bluetoothd[871]: Endpoint registered: sender=:1.60 path=/MediaEndpoint/A2DPSource>
May 04 09:04:15 localhost.localdomain bluetoothd[871]: Endpoint registered: sender=:1.60 path=/MediaEndpoint/A2DPSource>
May 04 09:04:15 localhost.localdomain bluetoothd[871]: Endpoint registered: sender=:1.60 path=/MediaEndpoint/A2DPSource>
May 04 09:04:15 localhost.localdomain bluetoothd[871]: Endpoint registered: sender=:1.60 path=/MediaEndpoint/A2DPSource>
May 04 09:04:15 localhost.localdomain bluetoothd[871]: Endpoint registered: sender=:1.60 path=/MediaEndpoint/A2DPSource>
May 04 09:57:18 localhost.localdomain bluetoothd[871]: /org/bluez/hci0/dev_94_7B_E7_01_8F_1C/sep1/fd0: fd(40) ready
May 04 09:58:37 localhost.localdomain bluetoothd[871]: src/profile.c:ext_io_disconnected() Unable to get io data for He>
May 04 12:19:40 localhost.localdomain bluetoothd[871]: /org/bluez/hci0/dev_94_7B_E7_01_8F_1C/sep1/fd1: fd(40) ready
[13:03][da@:~]$:**sudo systemctl status dbus-org.bluez.service **
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
Active: active (running) since Wed 2022-05-04 09:02:32 BST; 4h 1min ago
Docs: man:bluetoothd(8)
Main PID: 871 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 4915)
CPU: 1.785s
CGroup: /system.slice/bluetooth.service
└─871 /usr/libexec/bluetooth/bluetoothd
May 04 09:04:15 localhost.localdomain bluetoothd[871]: Endpoint registered: sender=:1.60 path=/MediaEndpoint/A2DPSource>
May 04 09:04:15 localhost.localdomain bluetoothd[871]: Endpoint registered: sender=:1.60 path=/MediaEndpoint/A2DPSource>
May 04 09:04:15 localhost.localdomain bluetoothd[871]: Endpoint registered: sender=:1.60 path=/MediaEndpoint/A2DPSource>
May 04 09:04:15 localhost.localdomain bluetoothd[871]: Endpoint registered: sender=:1.60 path=/MediaEndpoint/A2DPSource>
May 04 09:04:15 localhost.localdomain bluetoothd[871]: Endpoint registered: sender=:1.60 path=/MediaEndpoint/A2DPSource>
May 04 09:04:15 localhost.localdomain bluetoothd[871]: Endpoint registered: sender=:1.60 path=/MediaEndpoint/A2DPSource>
May 04 09:04:15 localhost.localdomain bluetoothd[871]: Endpoint registered: sender=:1.60 path=/MediaEndpoint/A2DPSource>
May 04 09:57:18 localhost.localdomain bluetoothd[871]: /org/bluez/hci0/dev_94_7B_E7_01_8F_1C/sep1/fd0: fd(40) ready
May 04 09:58:37 localhost.localdomain bluetoothd[871]: src/profile.c:ext_io_disconnected() Unable to get io data for He>
May 04 12:19:40 localhost.localdomain bluetoothd[871]: /org/bluez/hci0/dev_94_7B_E7_01_8F_1C/sep1/fd1: fd(40) ready
and obex.service and dbus-org.bluez.obex.service are enabled but inactive (maybe because they are used by bluetooth.service when are needed):
[13:04][da@:~]$:**sudo systemctl status obex.service **
○ obex.service - Bluetooth OBEX service
Loaded: loaded (/etc/systemd/system/obex.service; enabled; vendor preset: disabled)
Active: inactive (dead)
[13:07][da@:~]$:**sudo systemctl status dbus-org.bluez.obex.service**
○ dbus-org.bluez.obex.service - Bluetooth OBEX service
Loaded: loaded (/etc/systemd/system/dbus-org.bluez.obex.service; alias)
Active: inactive (dead)
file in /etc/systemd/user:
**dbus-org.bluez.obex.service** -as a link to- /usr/lib/systemd/user/obex.service
files in /etc/systemd/system:
**obex.service ** -as a link to- /usr/lib/systemd/user/obex.service
**dbus-org.bluez.obex.service** -as a link to- /usr/lib/systemd/user/obex.service
**dbus-org.bluez.service** -as a link to- /usr/lib/systemd/system/bluetooth.service
An update here because after a fresh install file transfers via bluetooth didn’t work again:
$:sudo zypper in bluez-obexd (obexd wasn't installed).
and I needed to enable and start it:
systemctl --user start obex.service
systemctl --user enable obex.service
sometimes if it doesn't work:
- disconnect and delete the device from the devices window (bluez applet/devices).
- switch off bluetooth.
- switch off bluetooth in the phone too.
- start the pairing process again: switch on both bluetooths, search for devices, connect/pair...
