Description of problem: Connect a bluetooth headset that used to work before (CX 350 in this case). Version-Release number of selected component: blueman-1:2.3.5-8.fc39 Additional info: reporter: libreport-2.17.11 type: Python3 exception_type: KeyError executable: /usr/bin/blueman-applet package: blueman-1:2.3.5-8.fc39 crash_function: _on_battery_property_changed comment: Connect a bluetooth headset that used to work before (CX 350 in this case). interpreter: python3-3.12.2-2.fc39.x86_64 cmdline: /usr/bin/python3 -sPE /usr/bin/blueman-applet runlevel: N 5 reason: ConnectionNotifier.py:57:_on_battery_property_changed:KeyError: '/org/bluez/hci0/dev_00_1B_66_C3_37_D7' uid: 1000 cgroup: 0::/user.slice/user-1000.slice/session-3.scope kernel: 6.8.4-200.fc39.x86_64 Truncated backtrace: ConnectionNotifier.py:57:_on_battery_property_changed:KeyError: '/org/bluez/hci0/dev_00_1B_66_C3_37_D7' Traceback (most recent call last): File "/usr/lib/python3.12/site-packages/blueman/plugins/applet/ConnectionNotifier.py", line 53, in _on_battery_created self._on_battery_property_changed(battery, "Percentage", battery["Percentage"], obj_path) File "/usr/lib/python3.12/site-packages/blueman/plugins/applet/ConnectionNotifier.py", line 57, in _on_battery_property_changed notification = self._notifications[path] ~~~~~~~~~~~~~~~~~~~^^^^^^ KeyError: '/org/bluez/hci0/dev_00_1B_66_C3_37_D7' Local variables in innermost frame: self: <blueman.plugins.applet.ConnectionNotifier.ConnectionNotifier object at 0x7f43d7a3b0e0> _battery: <Battery.Battery object at 0x7f43cff5cb00 (blueman+bluez+Battery+Battery at 0x563b9a9aefc0)> key: 'Percentage' value: 100 path: '/org/bluez/hci0/dev_00_1B_66_C3_37_D7'
Created attachment 2026658 [details] File: namespaces
Created attachment 2026659 [details] File: open_fds
Created attachment 2026660 [details] File: backtrace
Created attachment 2026661 [details] File: mountinfo
Created attachment 2026662 [details] File: environ
Created attachment 2026663 [details] File: cpuinfo
Created attachment 2026664 [details] File: os_info
The issue is probably triggered by https://bugzilla.redhat.com/show_bug.cgi?id=2274769
Or maybe it's more interesting: https://bugzilla.redhat.com/show_bug.cgi?id=2274769 could be a red herring, and it's actually blueman that misleads me about the device status. I'd really like to hear your thoughts on both issues.
Presumably fixed as part of https://bugzilla.redhat.com/show_bug.cgi?id=2274047 *** This bug has been marked as a duplicate of bug 2274047 ***