bam
(Andrey)
March 19, 2026, 1:16pm
1
This is continuation of original issue .
As I checked, the information and workarounds there are still actual.
If someone has something more to add, e.g. which workaround you see more appropriate or any other solution, please share.
opened 06:08PM - 18 Mar 26 UTC
bug
f43
**Describe the bug**
```
journalctl -e
...
мар 18 20:19:57 box-master obexd[2809… 34]: open(/home/bam/.cache/obexd/5Z0HM3): No such file or directory (2)
```
**To Reproduce**
1. Connect Android device over Bluetooth.
2. Try to send any appropriate files to the PC.
**Expected behavior**
The files should appear in Downloads folder, with appropriate notification.
**Actual behavior**
Nothing happens, see above log for the obexd error.
**OS version:**
```
● fedora:fedora/43/x86_64/silverblue
Version: 43.20260311.0 (2026-03-11T00:29:36Z)
BaseCommit: a05a19110b2551410511878be0b9aae2f64c12001f500d03e545023eca5d06e0
GPGSignature: Valid signature by C6E7F081CF80E13146676E88829B606631645531
RemovedBasePackages: ibus-typing-booster 2.30.4-1.fc43 nano default-editor nano-default-editor 8.5-2.fc43 vim-minimal 2:9.2.112-2.fc43
LayeredPackages: dconf-editor edk2-ext4 edk2-ovmf efifs git-subtree gnome-shell-extension-appindicator gnome-shell-extension-dash-to-dock gnome-tweaks goldendict gvim intel-media-driver
levien-inconsolata-fonts libavcodec-freeworld libva-utils lm_sensors rpmfusion-free-release rpmfusion-nonfree-release smartmontools systemd-boot-unsigned terminus-fonts translate-shell
zsh
```
**Additional context**
The problem is probably that `/home` is a symlink to `/var/home/`.
Possible solutions:
1. run `obexd` with `--symlinks` option:
https://discussion.fedoraproject.org/t/cannot-receive-file-over-bluetooth/1813/5
2. make `$HOME` on `/var/home/$USER`, not `/home/$USER` as it is now.
@hricky @jurf @mildred593
hricky
(Hristo Marinov)
March 19, 2026, 2:05pm
6
I kindly ask that you do not modify the category or tags of this topic. The Project Discussion category is reserved specifically for high-level Fedora Project discourse, as you can see here . As the maintainers have already acknowledged the issue and are working toward a resolution, keeping the post in its current location with the appropriate tags ensures it remains discoverable for other users facing the same problem. Furthermore, please refrain from directly pinging inactive contributors; this is ineffective and results in unnecessary notifications for individuals no longer monitoring this forum.