Version-Release number of selected component: blueman-1:2.3.5-7.fc39 Additional info: reporter: libreport-2.17.11 interpreter: python3-3.12.0-1.fc39.x86_64 cmdline: /usr/bin/python3 -sPE /usr/bin/blueman-applet reason: DBusProxies.py:58:_activate:NameError: name 'logging' is not defined. Did you forget to import 'logging' uid: 1000 executable: /usr/bin/blueman-applet kernel: 6.5.6-300.fc39.x86_64 crash_function: _activate package: blueman-1:2.3.5-7.fc39 type: Python3 exception_type: gi.repository.GLib.GError runlevel: N 5 cgroup: 0::/user.slice/user-1000.slice/session-2.scope Truncated backtrace: DBusProxies.py:58:_activate:NameError: name 'logging' is not defined. Did you forget to import 'logging' Traceback (most recent call last): File "/usr/lib/python3.12/site-packages/blueman/main/DBusProxies.py", line 53, in _activate self.call_sync("Activate", param, Gio.DBusCallFlags.NONE, -1, None) gi.repository.GLib.GError: g-io-error-quark: Timeout was reached (24) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.12/site-packages/blueman/plugins/applet/StandardItems.py", line 57, in <lambda> self.parent.Plugins.StatusIcon.connect("activate", lambda _status_icon: self.on_devices()) ^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/blueman/plugins/applet/StandardItems.py", line 81, in on_devices m.startstop() File "/usr/lib/python3.12/site-packages/blueman/main/DBusProxies.py", line 80, in startstop self._activate() File "/usr/lib/python3.12/site-packages/blueman/main/DBusProxies.py", line 58, in _activate logging.error("Call to %s failed", self.get_name(), exc_info=True) ^^^^^^^ NameError: name 'logging' is not defined. Did you mean: 'self.logging'? Or did you forget to import 'logging' Local variables in innermost frame: self: <DBusProxies.ManagerService object at 0x7f8a01097a00 (blueman+main+DBusProxies+ManagerService at 0x55731634d760)> param: GLib.Variant('(a{sv})', ({},))
Created attachment 1996084 [details] File: cpuinfo
Created attachment 1996085 [details] File: environ
Created attachment 1996086 [details] File: mountinfo
Created attachment 1996087 [details] File: os_info
Created attachment 1996088 [details] File: namespaces
Created attachment 1996089 [details] File: backtrace
Created attachment 1996090 [details] File: open_fds
FEDORA-2023-79e39eaeb2 has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2023-79e39eaeb2
FEDORA-2023-79e39eaeb2 has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2023-71624bbb98 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-71624bbb98
FEDORA-2023-3e7f0859d4 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-3e7f0859d4
FEDORA-2023-c245566a89 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-c245566a89
FEDORA-2023-3e7f0859d4 has been pushed to the Fedora 38 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-3e7f0859d4` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-3e7f0859d4 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-71624bbb98 has been pushed to the Fedora 39 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-71624bbb98` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-71624bbb98 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-c245566a89 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-2023-c245566a89` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-c245566a89 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
This happend connecting to a Huawei phone via BT for audio and for tethering. reporter: libreport-2.17.11 kernel: 6.5.9-300.fc39.x86_64 cmdline: /usr/bin/python3 -sPE /usr/bin/blueman-applet cgroup: 0::/user.slice/user-1000.slice/session-5.scope uid: 1000 reason: DBusProxies.py:58:_activate:NameError: name 'logging' is not defined. Did you forget to import 'logging' executable: /usr/bin/blueman-applet type: Python3 package: blueman-1:2.3.5-7.fc39 runlevel: N 5 exception_type: gi.repository.GLib.GError crash_function: _activate interpreter: python3-3.12.0-1.fc39.x86_64 comment: This happend connecting to a Huawei phone via BT for audio and for tethering.
FEDORA-2023-c245566a89 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2023-71624bbb98 has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2023-3e7f0859d4 has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.