Created attachment 1883520 [details] Message when I try to transfer from Fedora 36 Silverblue to my POCO X3 Pro phone Description of problem: Hi, with the latest updates I lost the ability to transfer files through Bluetooth between Fedora 36 Silverblue and my POCO X3 PRO phone in both directions, when I try to transfer from PC to the phone and from the phone to the PC. Version-Release number of selected component (if applicable): I use GNOME Bluetooth 42, but I'm not sure if it's the real root of the problem because that component wasn't updated the latest days. I suspect of NetworkManager, ModemManager and the kernel. How reproducible: Just pair your Android phone (or a least a Xiaomi phone) with Fedora 36 Silverblue and try to transfer a file from one system to the other. Steps to Reproduce: 1. Pair your Android phone with Fedora 36 Silverblue using GNOME Bluetooth. 2. After pairing correctly, try to transfer a file. 3. You can see that you can't transfer any file. Actual results: Now I can't transfer files through Bluetooth, but I could do it in previous days. I tried to TP-LINK UB500 USB Bluetooth, the Intel Bluetooth of my Acer laptop and another USB Bluetooth from Realtek and all of them fails when I try to transfer files, so I think the problem is from the system. My 8BitDo Pro 2 controller seems to work properly through Bluetooth. Expected results: Obviously, I hope to transfer files through Bluetooth with Fedora 36 Silverblue. I'm waiting for instructions if you need my help.
Installing bluez-obexd package solved the issue. https://www.reddit.com/r/Fedora/comments/uw2kyl/comment/intyczv/?utm_source=reddit&utm_medium=web2x&context=3 Sorry if I sound harsh, but I would like to see some warning about this kind of things in the future. A little post on Fedora Magazine would be enough for me. This can be closed.
FEDORA-2022-d2bb98654a has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-d2bb98654a
(In reply to Eduardo Medina from comment #1) > Installing bluez-obexd package solved the issue. > https://www.reddit.com/r/Fedora/comments/uw2kyl/comment/intyczv/ > ?utm_source=reddit&utm_medium=web2x&context=3 > > Sorry if I sound harsh, but I would like to see some warning about this kind > of things in the future. A little post on Fedora Magazine would be enough > for me. I'm really not sure why we would spend the time to write an article to document a bug that we could just fix, and now have fixed. You might also want to set your expectations to a level commensurate to the price you paid for the technical support being provided, it will certainly help not sounding harsh :)
FEDORA-2022-35b9eff1e1 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-35b9eff1e1
FEDORA-2022-d2bb98654a has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-d2bb98654a` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-d2bb98654a See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-35b9eff1e1 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-35b9eff1e1` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-35b9eff1e1 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-d2bb98654a has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-35b9eff1e1 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.