Version-Release number of selected component: blueman-1:2.2.1-1.fc34 Additional info: reporter: libreport-2.15.2 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/blueman-manager.service cmdline: /usr/bin/python3 /usr/bin/blueman-manager crash_function: _update_power_levels exception_type: gi.repository.GLib.GError executable: /usr/bin/blueman-manager interpreter: python3-3.9.6-2.fc34.x86_64 kernel: 5.13.7-200.fc34.x86_64 runlevel: N 5 type: Python3 uid: 1000 Truncated backtrace: ManagerDeviceList.py:438:_update_power_levels:gi.repository.GLib.GError: g-file-error-quark: Failed to open file “/usr/share/blueman/pixmaps/blueman-tpl-0.png”: No such file or directory (4) Traceback (most recent call last): File "/usr/lib/python3.9/site-packages/blueman/gui/manager/ManagerDeviceList.py", line 360, in _check_power_levels self._update_power_levels(tree_iter, device, cinfo) File "/usr/lib/python3.9/site-packages/blueman/gui/manager/ManagerDeviceList.py", line 438, in _update_power_levels icon = GdkPixbuf.Pixbuf.new_from_file_at_scale(os.path.join(PIXMAP_PATH, icon_name), w, h, True) gi.repository.GLib.GError: g-file-error-quark: Failed to open file “/usr/share/blueman/pixmaps/blueman-tpl-0.png”: No such file or directory (4) Local variables in innermost frame: self: <ManagerDeviceList.ManagerDeviceList object at 0x7fba9da89e40 (blueman+gui+manager+ManagerDeviceList+ManagerDeviceList at 0x561ea53983f0)> tree_iter: <Gtk.TreeIter object at 0x7fba9c7c0f40 (GtkTreeIter at 0x561ea5205080)> device: <Device.Device object at 0x7fba9c7a3480 (blueman+bluez+Device+Device at 0x7fba98004be0)> cinfo: <_blueman.conn_info object at 0x7fba9c7ac750> row: {'cell_fader': <GtkAnimation.CellFade object at 0x7fba9c7a3100 (blueman+gui+GtkAnimation+CellFade at 0x561ea51bc740)>, 'battery': 0.0, 'rssi': 37.40157480314961, 'lq': 50.0, 'tpl': 10.0} bars: {'rssi': 50, 'lq': 50, 'tpl': 0} w: 14 h: 48 name: 'tpl' perc: 0 icon_name: 'blueman-tpl-0.png' icon: <GdkPixbuf.Pixbuf object at 0x7fba9c7c4340 (GdkPixbuf at 0x561ea53209e0)>
Created attachment 1811036 [details] File: backtrace
Created attachment 1811037 [details] File: cpuinfo
Created attachment 1811038 [details] File: environ
Created attachment 1811039 [details] File: mountinfo
Created attachment 1811041 [details] File: namespaces
Created attachment 1811042 [details] File: open_fds
FEDORA-2021-bcf71bd831 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-bcf71bd831
FEDORA-2021-7d333eedd6 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-7d333eedd6
FEDORA-2021-7d333eedd6 has been pushed to the Fedora 33 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-7d333eedd6` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-7d333eedd6 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-bcf71bd831 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-bcf71bd831` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-bcf71bd831 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-bcf71bd831 has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2021-7d333eedd6 has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report.