Bluetooth File Transfer not working on MicroOS Kalpa

[Bird]

Hi Everyone,

I recently installed MicroOS Kalpa on an Intel NUC at my workplace and except for a few things, everything works as expected. I know that the project is still in alpha, but I was encountering an issue with Bluetooth File Transfer and wanted to know if there is any way to fix it myself. The Problem seems to be similar to:

Bluetooth file transfer fails

Hi, did a few new installs of leap 15.5 and so far all has gone very well (my thanks to the opensuse team!). However today I tried to transfer a file via bluetooth to a phone and I get the error: Failed to start org.bluez.obex service: The name org.bluez.obex was not provided by any .service files The bluetooth dongle is recognised as: Bus 002 Device 005: ID 0a5c:21e8 Broadcom Corp. BCM20702A0 Bluetooth 4.0 and used to work fine in leap 15.3 and 15.4. Any suggestions? Thanks.

However, I don’t really know how I would go about it on MicroOS because of transactional-update.

I can connect to a bluetooth device no problem and can even control media (pause, play, skip songs on my phone), but when I try to send or receive a file I get the following error:

[arvidjaar]

@Bird

I don’t really know how I would go about it on MicroOS because of transactional-update.

And what is your question? You install packages using transactional-update, did you try it?

transactional-update pkg install ...

And the last post about enabling user service works exactly the same.

[Bird]

Well I tried, but it seems obex or obexd is not available:

user@localhost:~> systemctl --user status dbus-org.bluez.obex.service
Unit dbus-org.bluez.obex.service could not be found.
user@localhost:~> sudo systemctl --user enable obex
[sudo] Passwort für root:
Failed to connect to bus: No medium found
user@localhost:~> sudo transactional-update pkg install obexd
Checking for newer version.
transactional-update 4.6.8 started
Options: pkg install obexd
Separate /var detected.
2024-05-17 09:57:23 tukit 4.6.8 started
2024-05-17 09:57:23 Options: -c4 open
2024-05-17 09:57:23 Using snapshot 4 as base for new snapshot 5.
2024-05-17 09:57:23 /var/lib/overlay/4/etc
2024-05-17 09:57:23 Syncing /etc of previous snapshot 3 as base into new snapshot "/.snapshots/5/snapshot"
2024-05-17 09:57:23 SELinux is enabled.
ID: 5
2024-05-17 09:57:29 Transaction completed.
Calling zypper install
2024-05-17 09:57:37 tukit 4.6.8 started
2024-05-17 09:57:37 Options: callext 5 zypper -R {} install obexd
2024-05-17 09:57:42 Executing `zypper -R /tmp/transactional-update-0Dvle1 install obexd`:
Loading repository data...
Reading installed packages...
'obexd' not found in package names. Trying capabilities.
No provider of 'obexd' found.
Resolving package dependencies...
Nothing to do.
2024-05-17 09:57:45 Application returned with exit status 104.
ERROR: zypper install on /.snapshots/5/snapshot failed with exit code 104!
Removing snapshot #5...
2024-05-17 09:57:45 tukit 4.6.8 started
2024-05-17 09:57:45 Options: abort 5
2024-05-17 09:57:50 Discarding snapshot 5.
2024-05-17 09:57:50 Transaction completed.
transactional-update finished
user@localhost:~> sudo systemctl --user enable obexd
Failed to connect to bus: No medium found
user@localhost:~> sudo transactional-update pkg install obex
Checking for newer version.
transactional-update 4.6.8 started
Options: pkg install obex
Separate /var detected.
2024-05-17 10:01:39 tukit 4.6.8 started
2024-05-17 10:01:39 Options: -c4 open
2024-05-17 10:01:40 Using snapshot 4 as base for new snapshot 5.
2024-05-17 10:01:40 /var/lib/overlay/4/etc
2024-05-17 10:01:40 Syncing /etc of previous snapshot 3 as base into new snapshot "/.snapshots/5/snapshot"
2024-05-17 10:01:40 SELinux is enabled.
ID: 5
2024-05-17 10:01:47 Transaction completed.
Calling zypper install
2024-05-17 10:01:57 tukit 4.6.8 started
2024-05-17 10:01:57 Options: callext 5 zypper -R {} install obex
2024-05-17 10:02:02 Executing `zypper -R /tmp/transactional-update-Y9d18A install obex`:
Loading repository data...
Reading installed packages...
'obex' not found in package names. Trying capabilities.
No provider of 'obex' found.
Resolving package dependencies...
Nothing to do.
2024-05-17 10:02:05 Application returned with exit status 104.
ERROR: zypper install on /.snapshots/5/snapshot failed with exit code 104!
Removing snapshot #5...
2024-05-17 10:02:05 tukit 4.6.8 started
2024-05-17 10:02:05 Options: abort 5
2024-05-17 10:02:10 Discarding snapshot 5.
2024-05-17 10:02:10 Transaction completed.
transactional-update finished
user@localhost:~> systemctl --user status dbus-org.bluez.obexd.service
Unit dbus-org.bluez.obexd.service could not be found.
user@localhost:~> systemctl --user status dbus-org.bluez.obex.service
Unit dbus-org.bluez.obex.service could not be found.
user@localhost:~>

I could however install bluez.obexd

[hui]

The sevice names are org.bluez.obex.service and obex.service provided by the package bluez-obexd

[Bird]

All right, thanks you two … I struggled a bit, but it turned out I had to leave out sudo. So if anyone has the same issue, here is what to do:

sudo transactional-update pkg install bluez-obexd

If that was successful:

sudo reboot

Then after reboot:

systemctl --user enable obex.service

[arvidjaar]

@Bird

sudo systemctl --user enable obex

This is either

systemctl --user enable

or

sudo systemctl --global enable

Edit: sorry, messed up originally. --global stands alone, not with --user. Both affect user units as opposed to system units.