Bug 1405745 - [abrt] solaar: settings.py:63:__call__:AssertionError
Summary: [abrt] solaar: settings.py:63:__call__:AssertionError
Keywords:
Status: CLOSED DUPLICATE of bug 1376879
Alias: None
Product: Fedora
Classification: Fedora
Component: solaar
Version: 25
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Eric Smith
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:b497be9c15ca0d9519a2510adc4...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-18 02:35 UTC by Edward Donovan
Modified: 2016-12-18 02:40 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-12-18 02:40:38 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (1.22 KB, text/plain)
2016-12-18 02:35 UTC, Edward Donovan
no flags Details
File: environ (956 bytes, text/plain)
2016-12-18 02:35 UTC, Edward Donovan
no flags Details

Description Edward Donovan 2016-12-18 02:35:03 UTC
Description of problem:
Woke the laptop up from suspend.  Then turned on my logitech wireless keyboard.  

The notification that the keyboard was detected appeared, then the note that solaar had crashed, pretty much immediately.

The solaar process with the listed PID is still running, and the UI is available and functioning in the Plasma system tray.  I guess I don't understand this situation. or assertions, enough.  I would think that with this assertion the process would terminate.

I think this has happened very occasionally before.  I'm not yet aware of any different circumstances on the rare times it crashes when I turn on the external keyboard.

I've tried to remove the references to my hostname and username from the generated bug report. I don't think they're important here?  I probably missed some, anyway. :/

Version-Release number of selected component:
solaar-0.9.2-4.20150528gitcf27328.fc25.4

Additional info:
reporter:       libreport-2.8.0
cmdline:        /usr/bin/python /usr/bin/solaar
executable:     /usr/bin/solaar
kernel:         4.8.13-300.fc25.x86_64
pkg_fingerprint: 4089 D8F2 FDB1 9C98
pkg_vendor:     Fedora Project
runlevel:       N 5
type:           Python
uid:            1000

Truncated backtrace:
settings.py:63:__call__:AssertionError

Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/solaar/ui/window.py", line 387, in _device_selected
    _update_info_panel(device, full=True)
  File "/usr/lib/python2.7/site-packages/solaar/ui/window.py", line 704, in _update_info_panel
    _update_device_panel(device, _info._device, _info._buttons, full)
  File "/usr/lib/python2.7/site-packages/solaar/ui/window.py", line 675, in _update_device_panel
    _config_panel.update(device, is_online)
  File "/usr/lib/python2.7/site-packages/solaar/ui/config_panel.py", line 182, in update
    for s in device.settings:
  File "/usr/lib/python2.7/site-packages/logitech_receiver/receiver.py", line 254, in settings
    _check_feature_settings(self, self._settings)
  File "/usr/lib/python2.7/site-packages/logitech_receiver/settings_templates.py", line 190, in check_feature_settings
    already_known.append(smooth_scroll(device))
  File "/usr/lib/python2.7/site-packages/logitech_receiver/settings.py", line 63, in __call__
    assert self.device_kind is None or self.device_kind == device.kind
AssertionError

Local variables in innermost frame:
device: <PairedDevice(1,4024,K400)>
self: <Setting([feature:toggle] smooth-scroll)>

Potential duplicate: bug 1376879

Comment 1 Edward Donovan 2016-12-18 02:35:08 UTC
Created attachment 1233019 [details]
File: backtrace

Comment 2 Edward Donovan 2016-12-18 02:35:09 UTC
Created attachment 1233020 [details]
File: environ

Comment 3 Edward Donovan 2016-12-18 02:38:59 UTC
Oh, cripes, I've reported this bug before!  Sorry, I'm sleepy.  And I hoped the bug tools would catch that before submitting it.  Instead I only saw a link after the dupe was created.  Now I'll see if I have the privileges to mark it as a dupe.  Sigh.

Comment 4 Edward Donovan 2016-12-18 02:40:38 UTC

*** This bug has been marked as a duplicate of bug 1376879 ***


Note You need to log in before you can comment on or make changes to this bug.