https://bugzilla.suse.com/show_bug.cgi?id=1220991 Bug ID: 1220991 Summary: After the latest BT bluez updates the whole BT functionality seems broken included file transfer, pairing, holding the connection Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs@suse.de Reporter: stakanov@disroot.org QA Contact: qa-bugs@suse.de Target Milestone: --- Found By: --- Blocker: --- I did install bluez, obex-ftp and the dependent library, activated for each user by using # systemctl --user status dbus-org.bluez.obex.service but: entropia@p200300c96f4d3b00eeac83d1db4c69e9:~> systemctl --user status dbus-org.bluez.obex.service ● obex.service - Bluetooth OBEX service Loaded: loaded (/usr/lib/systemd/user/obex.service; enabled; preset: disabled) Active: active (running) since Tue 2024-03-05 17:19:59 CET; 1min 10s ago Main PID: 26291 (obexd) Tasks: 1 (limit: 4915) Memory: 948.0K CPU: 7ms CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/obex.service └─26291 /usr/libexec/bluetooth/obexd mar 05 17:19:59 p200300c96f4d3b00eeac83d1db4c69e9.dip0.t-ipconnect.de systemd[25855]: Starting Bluetooth OBEX service... mar 05 17:19:59 p200300c96f4d3b00eeac83d1db4c69e9.dip0.t-ipconnect.de obexd[26291]: OBEX daemon 5.71 mar 05 17:19:59 p200300c96f4d3b00eeac83d1db4c69e9.dip0.t-ipconnect.de systemd[25855]: Started Bluetooth OBEX service. Now obex is active but filetransfer with a Xiaomi PocoX3 Pro fail, be it on a PC with dongle were it fails too. With an ASUS X515K the behavior is now: does see the phone, does pair, but connects with extreme difficulty and drops the connection when one tries to use the file transfer. On the PC the file transfer first fails, then suddenly it may run, saying file transmitted, but no file arrived. Sometimes with the notebook not even the type of hardware is recognized correctly. That is: the notebook was first recognized by the smartphone as audio device. Now it sees a notebook, but....does not hold the connection. Well as I write there is no possibility to connect any more to the notebook. BT is simply broken. Following is the only trace I found in journalctl: mar 05 17:38:55 p200300c96f4d3b00eeac83d1db4c69e9.dip0.t-ipconnect.de plasmashell[26049]: Could not find the Plasmoid for Plasma::FrameSvgItem(0x55f3f1d38dc0) QQmlContext(0x55f3f0769030) QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasm> mar 05 17:38:55 p200300c96f4d3b00eeac83d1db4c69e9.dip0.t-ipconnect.de plasmashell[26049]: Could not find the Plasmoid for Plasma::FrameSvgItem(0x55f3f1d38dc0) QQmlContext(0x55f3f0769030) QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasm> mar 05 17:38:55 p200300c96f4d3b00eeac83d1db4c69e9.dip0.t-ipconnect.de plasmashell[26049]: kf.bluezqt: PendingCall Error: "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security> mar 05 17:38:53 p200300c96f4d3b00eeac83d1db4c69e9.dip0.t-ipconnect.de plasmashell[26049]: qml: temp unit: 0 The Xiaomi client claims: connect did fail -- You are receiving this mail because: You are on the CC list for the bug.