Description of problem: This has been reported twice, simply on start-up, i.e. logging in, immediately after booting up. No specific actions had been performed. Version-Release number of selected component: solaar-0.9.2-10.20180813gitf0fc63e.fc29 Additional info: reporter: libreport-2.9.6 cmdline: /usr/bin/python3 -s /usr/bin/solaar crash_function: _check exception_type: AssertionError executable: /usr/bin/solaar interpreter: python3-3.7.1-2.fc29.x86_64 kernel: 4.19.2-300.fc29.x86_64 runlevel: N 5 type: Python3 uid: 1000 Truncated backtrace: hidpp20.py:189:_check:AssertionError Traceback (most recent call last): File "/usr/lib/python3.7/site-packages/solaar/ui/__init__.py", line 165, in _status_changed window.update(device, need_popup) File "/usr/lib/python3.7/site-packages/solaar/ui/window.py", line 822, in update _update_info_panel(device, full=full_update) File "/usr/lib/python3.7/site-packages/solaar/ui/window.py", line 703, in _update_info_panel _update_device_panel(device, _info._device, _info._buttons, full) File "/usr/lib/python3.7/site-packages/solaar/ui/window.py", line 674, in _update_device_panel _config_panel.update(device, is_online) File "/usr/lib/python3.7/site-packages/solaar/ui/config_panel.py", line 206, in update for s in device.settings: File "/usr/lib/python3.7/site-packages/logitech_receiver/receiver.py", line 254, in settings _check_feature_settings(self, self._settings) File "/usr/lib/python3.7/site-packages/logitech_receiver/settings_templates.py", line 380, in check_feature_settings check_feature(_FN_SWAP[0], _F.FN_INVERSION) File "/usr/lib/python3.7/site-packages/logitech_receiver/settings_templates.py", line 366, in check_feature if not featureId in device.features: File "/usr/lib/python3.7/site-packages/logitech_receiver/hidpp20.py", line 249, in __contains__ if self._check(): File "/usr/lib/python3.7/site-packages/logitech_receiver/hidpp20.py", line 189, in _check assert self.device AssertionError Local variables in innermost frame: self: <logitech_receiver.hidpp20.FeaturesArray object at 0x7f374fc05a08>
Created attachment 1507682 [details] File: backtrace
Created attachment 1507683 [details] File: cgroup
Created attachment 1507684 [details] File: cpuinfo
Created attachment 1507685 [details] File: environ
Created attachment 1507686 [details] File: mountinfo
Created attachment 1507687 [details] File: namespaces
Created attachment 1507688 [details] File: open_fds
It's been reported to upstream, but they have stopped responding again. There is one upstream commit that's not in the Fedora package. It doesn't appear to be at all related but I guess I can push it just in case. I'm not going to mark it as fixing this bug, though.
*** Bug 1680344 has been marked as a duplicate of this bug. ***
*** Bug 1685371 has been marked as a duplicate of this bug. ***
*** Bug 1713900 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '29'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 29 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.