proxy_method.py:97:__call__:gi.repository.GLib.GError: g-io-error-quark: GDBus.Error:unknown.PicklingError: Can't pickle local object <class 'ctypes.CDLL.__init__.<locals>._FuncPtr'> (36) Traceback (most recent call last): File "/usr/lib/python3.14/site-packages/inputremapper/gui/user_interface.py", line 254, in <lambda> "clicked", lambda *_: self.controller.start_injecting() ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^ File "/usr/lib/python3.14/site-packages/inputremapper/gui/controller.py", line 673, in start_injecting if not self.data_manager.start_injecting(): ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^ File "/usr/lib/python3.14/site-packages/inputremapper/gui/data_manager.py", line 569, in start_injecting if self._daemon.start_injecting(self.active_group.key, self.active_preset.name): ~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.14/site-packages/pydbus/proxy_method.py", line 102, in __call__ raise error File "/usr/lib/python3.14/site-packages/pydbus/proxy_method.py", line 97, in __call__ result = instance._bus.con.call_sync(*call_args) gi.repository.GLib.GError: g-io-error-quark: GDBus.Error:unknown.PicklingError: Can't pickle local object <class 'ctypes.CDLL.__init__.<locals>._FuncPtr'> (36) Local variables in innermost frame: self: <function inputremapper.Control.start_injecting at 0x7f4c0d6bb250> instance: <DBUS.<CompositeObject>(inputremapper.Control+org.freedesktop.DBus.Properties+org.freedesktop.DBus.Introspectable+org.freedesktop.DBus.Peer) object at 0x7f4c0d6aa900> args: ('Logitech USB Receiver', 'Nuova preinpostazione') kwargs: {} argdiff: 0 timeout: None callback: None callback_args: () call_args: ('inputremapper.Control', '/inputremapper/Control', 'inputremapper.Control', 'start_injecting', GLib.Variant('(ss)', ('Logitech USB Receiver', 'Nuova preinpostazione')), <GLib.VariantType object at 0x7f4c0d5e1650 (GVariantType at 0x5641bff888d0)>, 0, 2147483647, None) result: None error: GLib.Error('GDBus.Error:unknown.PicklingError: Can't pickle local object <class 'ctypes.CDLL.__init__.<locals>._FuncPtr'>', 'g-io-error-quark', 36) Reproducible: Always Steps to Reproduce: 1. Open the input-remapper app 2. Select the input target 3. Add a new input 4. Register a new input 5. Apply the input Actual Results: I get the error an error message Expected Results: It have to register the input
Hello, Thanks for taking the time to report this. I think I might have to contact upstream about your issue, but first I have a few questions. I have the MX Master 2S, which uses a different receiver from 3S. In the main Input Remapper window I only see the mouse, not its receiver, which I think makes sense. I would expect any actions/remapping to be done on the mouse itself. Do you see both devices in the window, or only the receiver? What kind of action do you want to configure for the receiver? Can you remap any inputs of the mouse, or do you get the same problem?
Hi. All I can see is the receiver. Before the latest software update, the tool worked perfectly, allowing me to map different keyboard shortcuts to any button. However, since updating the system, I have noticed that they no longer work. When I analysed the app, I saw that when I tried to apply the recorded inputs, I received the error shown. Unfortunately, I don't remember the Python and Re-mapper versions before the update.
The program itself hasn't been updated in 7 months, but it was rebuilt a few times for the different Python 3.14 release candidates. I will check with the Python maintainers to see if they have any insights.
It appears indeed that the problem is compatibility with Python 3.14, see: https://github.com/sezanzeb/input-remapper/issues/1163 I had contacted upstream before the summer, they were going to work on some changes around this time, I hope they have the cycles to deal with this soon.
I understand. If it's just a matter of Python compatibility, they might resolve it in the near future.
(In reply to giovi.gurri from comment #5) > I understand. > If it's just a matter of Python compatibility, they might resolve it in the > near future. Since you are on F43, do you think you could try the solution(s) proposed by the developer in the GitHub issue?
Upstream will tag a new release sometime next week, so as to give people time to test the master branch. If all goes well, I will push an update next weekend.
*** Bug 2408420 has been marked as a duplicate of this bug. ***
FEDORA-2025-ed1f62a873 (input-remapper-2.2.0-1.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2025-ed1f62a873
Tried pressing the "load" button and nothing happened next reporter: libreport-2.17.15 reason: proxy_method.py:97:__call__:gi.repository.GLib.GError: g-io-error-quark: GDBus.Error:unknown.PicklingError: Can't pickle local object <class 'ctypes.CDLL.__init__.<locals>._FuncPtr'> (36) exception_type: gi.repository.GLib.GError kernel: 6.17.5-300.fc43.x86_64 comment: Tried pressing the "load" button and nothing happened next type: Python3 uid: 1000 crash_function: __call__ cmdline: /usr/bin/python3 /usr/bin/input-remapper-gtk runlevel: /bin/sh: line 1: runlevel: command not found executable: /usr/bin/input-remapper-gtk cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-input\x2dremapper\x2dgtk interpreter: python3-3.14.0-1.fc43.x86_64 package: input-remapper-2.1.1-6.fc43
(In reply to theplayer1604 from comment #10) > Tried pressing the "load" button and nothing happened next > […] > > package: input-remapper-2.1.1-6.fc43 You are still using the older version of the package.
FEDORA-2025-34059be292 (input-remapper-2.2.0-1.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2025-ed1f62a873 (input-remapper-2.2.0-1.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.