ERROR: got Future <Future pending> attached to a different loop

[alfem]

Hi!

Thanks for this app, really necessary in the linux metaverse.

I'd like to use it with my Logitech Triathlon, but when I try to record any button, nothing happens in the UI.

The output of debug mode is:

08:07:29.576086 36103 reader-service DEBUG reader_service.py:195: Received command "Logitech M720 Triathlon"
08:07:29.576177 36064 GUI DEBUG message_broker.py:76: from reader_client.py:178: Signal=recording_started: Signal: MessageType.recording_started
08:07:29.591737 36103 reader-service DEBUG system_mapping.py:128: Gathering available keycodes
08:07:29.600063 36103 reader-service DEBUG system_mapping.py:114: Writing "/home/acala/.config/input-remapper-2/xmodmap.json"
08:07:29.600844 36103 reader-service DEBUG system_mapping.py:128: Gathering available keycodes
08:07:29.607123 36103 reader-service DEBUG system_mapping.py:114: Writing "/home/acala/.config/input-remapper-2/xmodmap.json"
08:07:29.614807 36103 reader-service DEBUG event_reader.py:191: Starting to listen for events from /dev/input/event14, fd 18
08:07:29.615453 36103 reader-service DEBUG event_reader.py:108: read loop stopped
Task exception was never retrieved
future: <Task finished name='Task-5' coro=<Event.wait() done, defined at /usr/lib/python3.8/asyncio/locks.py:296> exception=RuntimeError("Task <Task pending name='Task-5' coro=<Event.wait() running at /usr/lib/python3.8/asyncio/locks.py:309> cb=[_wait.<locals>._on_completion() at /usr/lib/python3.8/asyncio/tasks.py:518]> got Future <Future pending> attached to a different loop")>
Traceback (most recent call last):
  File "/usr/lib/python3.8/asyncio/locks.py", line 309, in wait
    await fut
RuntimeError: Task <Task pending name='Task-5' coro=<Event.wait() running at /usr/lib/python3.8/asyncio/locks.py:309> cb=[_wait.<locals>._on_completion() at /usr/lib/python3.8/asyncio/tasks.py:518]> got Future <Future pending> attached to a different loop
08:07:29.616176 36103 reader-service INFO event_reader.py:207: read loop for /dev/input/event14 stopped
08:07:32.319584 36064 GUI DEBUG system_mapping.py:128: Gathering available keycodes
08:07:32.319734 36064 GUI DEBUG system_mapping.py:128: Gathering available keycodes
08:07:32.327421 36064 GUI DEBUG system_mapping.py:114: Writing "/home/acala/.config/input-remapper-2/xmodmap.json"
08:07:32.328315 36064 GUI DEBUG system_mapping.py:128: Gathering available keycodes
08:07:32.335140 36064 GUI DEBUG system_mapping.py:114: Writing "/home/acala/.config/input-remapper-2/xmodmap.json"
08:07:32.346125 36064 GUI DEBUG system_mapping.py:114: Writing "/home/acala/.config/input-remapper-2/xmodmap.json"
08:07:34.259943 36064 GUI DEBUG controller.py:615: Stopping Recording Keys
08:07:34.260475 36064 GUI DEBUG reader_client.py:185: Stopping recorder.
08:07:34.260854 36064 GUI DEBUG reader_client.py:120: Sending "stop-reading" to ReaderService
08:07:34.262258 36103 reader-service DEBUG reader_service.py:195: Received command "stop-reading"

I am using release 2.0.1

I also checked mouse button events with xev and evtest, and I can see all of them.

Please, tell me if I can help with the diagnostic.

[jonasBoss]

Please Update your Python version and check if the error persists.

[alfem]

Umm, I am afraid I use an enterprise linux solution and I am not allowed to change system installed Python.