I have a new 15.6 install on an x86 laptop. Initially, I thought that Bluetooth was working. However: …
Although I am able to connect devices (Mouse, Phone, Headphones etc), the file transfer is not working?
Any tip to debug this problem will be most welcome.
Regards, Martin
Check if bluez-obexd is installed. If not so, install it and test again.
Yep It is installed. But no, it doesn’t work::
mprowe@localhost:~> zypper search -i bluez
Repository : Time since last refresh
Dead Mozay : 14 s
Update repository of openSUSE Backports : 13 s
Non-OSS Repository : 13 s
Open H.264 Codec (openSUSE Leap) : 13 s
Main Repository : 13 s
Update repository with updates from SUSE Linux Enterprise 15 : 12 s
Main Update Repository : 12 s
Update Repository (Non-Oss) : 12 s
Note: Running with user privileges. From time to time run 'zypper refresh' as root to make sure
the repository metadata are complete and up-to-date.
Loading repository data...
Reading installed packages...
S | Name | Summary | Type
---+---------------------------+----------------------------------------------------------------+--------
i+ | bluez | Bluetooth Stack for Linux | package
i+ | bluez-auto-enable-devices | Configuration that automatically enables all bluetooth devices | package
i | bluez-cups | CUPS Driver for Bluetooth Printers | package
i+ | bluez-deprecated | Bluez tools that upstream considers obsolete | package
i+ | bluez-firmware | Bluetooth(TM) Firmware | package
i+ | bluez-obexd | Object Exchange daemon for sharing binary objects | package
i+ | bluez-qt-imports | Async Bluez wrapper library | package
i+ | bluez-qt-udev | bluez-qt integration with udev | package
i+ | bluez-test | Tools for testing of various Bluetooth-functions | package
i+ | bluez-tools | A set of tools to manage bluetooth devices | package
i+ | libKF5BluezQt6 | Async Bluez wrapper library - development files | package
mprowe@localhost:~>
Regards, M.
I just updated a minimal Leap 15.6 Gnome install and can confirm that while I can connect e.g. a phone, I cannot transfer files in either direction.
No obvious difference with my Tumbleweed install that works properly with the same HW.
Will keep you informed if I find something useful.
Create bug report.
Try
systemctl --user enable obex
systemctl --user start obex
Thanks for the suggestion:
mprowe@localhost:~> systemctl --user enable obex
mprowe@localhost:~>
mprowe@localhost:~> systemctl --user start obex
Job for obex.service failed because the control process exited with error code.
See "systemctl --user status obex.service" and "journalctl --user -xeu obex.service" for details.
mprowe@localhost:~>
mprowe@localhost:~> systemctl --user status obex.service
× obex.service - Bluetooth OBEX service
Loaded: loaded (/usr/lib/systemd/user/obex.service; enabled; preset: disabled)
Active: failed (Result: exit-code) since Tue 2024-06-18 06:47:31 BST; 16s ago
Process: 2878 ExecStart=/usr/lib/bluetooth/obexd (code=exited, status=1/FAILURE)
Main PID: 2878 (code=exited, status=1/FAILURE)
CPU: 9ms
Jun 18 06:47:31 localhost.localdomain systemd[1679]: Starting Bluetooth OBEX service...
Jun 18 06:47:31 localhost.localdomain obexd[2878]: OBEX daemon 5.71
Jun 18 06:47:31 localhost.localdomain obexd[2878]: Name already in use
Jun 18 06:47:31 localhost.localdomain obexd[2878]: manager_init failed
Jun 18 06:47:31 localhost.localdomain systemd[1679]: obex.service: Main process exited, code=exited, status=1/FAILURE
Jun 18 06:47:31 localhost.localdomain systemd[1679]: obex.service: Failed with result 'exit-code'.
Jun 18 06:47:31 localhost.localdomain systemd[1679]: Failed to start Bluetooth OBEX service.
mprowe@localhost:~>
mprowe@localhost:~> journalctl --user -xeu obex.service
No journal files were found.
~
-- No entries --
mprowe@localhost:~>
Any thoughts on above…?
Regards, M.
Noted that in Leap 15.6 gnome-bluetooth is still at version 42.7 with major Gnome components at 45.x.
I don’t really know if that is the culprit, but in Tumbleweed I see everything at 46.0 and bluetooth works as expected.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.