[GH-ISSUE #409] ``eis_device_stop_emulating` error in `journalctl`` every time the mouse crosses between devices #215

Open
opened 2026-05-05 22:14:16 -06:00 by gitea-mirror · 2 comments
Owner

Originally created by @lokmac on GitHub (Mar 29, 2026).
Original GitHub issue: https://github.com/feschber/lan-mouse/issues/409

I noticed errors in journalctl. I believe it's coming from lan-mouse.

Mar 30 00:30:41 galaxy kwin_wayland[5298]: Libeis: 🪲  Bug: eis_device_stop_emulating: missing call to eis_device_frame()
Mar 30 00:32:01 galaxy kwin_wayland[5298]: Libeis: 🪲  Bug: eis_device_stop_emulating: missing call to eis_device_frame()
Mar 30 00:32:26 galaxy kwin_wayland[5298]: Libeis: 🪲  Bug: eis_device_stop_emulating: missing call to eis_device_frame()
Mar 30 00:32:29 galaxy kwin_wayland[5298]: Libeis: 🪲  Bug: eis_device_stop_emulating: missing call to eis_device_frame()
Mar 30 00:32:35 galaxy kwin_wayland[5298]: Libeis: 🪲  Bug: eis_device_stop_emulating: missing call to eis_device_frame()
Mar 30 00:32:36 galaxy kwin_wayland[5298]: Libeis: 🪲  Bug: eis_device_stop_emulating: missing call to eis_device_frame()
Mar 30 00:32:36 galaxy kwin_wayland[5298]: Libeis: 🪲  Bug: eis_device_stop_emulating: missing call to eis_device_frame()
Mar 30 00:32:37 galaxy kwin_wayland[5298]: Libeis: 🪲  Bug: eis_device_stop_emulating: missing call to eis_device_frame()
Mar 30 00:32:37 galaxy kwin_wayland[5298]: Libeis: 🪲  Bug: eis_device_stop_emulating: missing call to eis_device_frame()
Mar 30 00:32:38 galaxy kwin_wayland[5298]: Libeis: 🪲  Bug: eis_device_stop_emulating: missing call to eis_device_frame()
Mar 30 00:32:39 galaxy kwin_wayland[5298]: Libeis: 🪲  Bug: eis_device_stop_emulating: missing call to eis_device_frame()
Mar 30 00:32:40 galaxy kwin_wayland[5298]: Libeis: 🪲  Bug: eis_device_stop_emulating: missing call to eis_device_frame()
Mar 30 00:32:40 galaxy kwin_wayland[5298]: Libeis: 🪲  Bug: eis_device_stop_emulating: missing call to eis_device_frame()
Mar 30 00:32:41 galaxy kwin_wayland[5298]: Libeis: 🪲  Bug: eis_device_stop_emulating: missing call to eis_device_frame()
Mar 30 00:32:42 galaxy kwin_wayland[5298]: Libeis: 🪲  Bug: eis_device_stop_emulating: missing call to eis_device_frame()
Mar 30 00:32:43 galaxy kwin_wayland[5298]: Libeis: 🪲  Bug: eis_device_stop_emulating: missing call to eis_device_frame()
Mar 30 00:32:43 galaxy kwin_wayland[5298]: Libeis: 🪲  Bug: eis_device_stop_emulating: missing call to eis_device_frame()
Mar 30 00:32:44 galaxy kwin_wayland[5298]: Libeis: 🪲  Bug: eis_device_stop_emulating: missing call to eis_device_frame()
Mar 30 00:32:45 galaxy kwin_wayland[5298]: Libeis: 🪲  Bug: eis_device_stop_emulating: missing call to eis_device_frame()
Mar 30 00:32:46 galaxy kwin_wayland[5298]: Libeis: 🪲  Bug: eis_device_stop_emulating: missing call to eis_device_frame()

There have been many bursts of this, but at 00:30ish I brought my laptop back online because I thought it was occurring because laptop was asleep, but not the case.

With laptop online, I noticed it was still occurring at 00:32. So I intentionally moved the mouse back and fourth across the screen boundary, alternative devices, and it seems there is one error per crossing of the screen border.

Both running Nobara 43 (43-6.fc43) with lan-mouse 0.10.0-1.fc43

No noticeable impact. Just reporting. I noticed it appearing in journalctl monitoring of 'err' and above.

Originally created by @lokmac on GitHub (Mar 29, 2026). Original GitHub issue: https://github.com/feschber/lan-mouse/issues/409 I noticed errors in journalctl. I believe it's coming from lan-mouse. ``` Mar 30 00:30:41 galaxy kwin_wayland[5298]: Libeis: 🪲 Bug: eis_device_stop_emulating: missing call to eis_device_frame() Mar 30 00:32:01 galaxy kwin_wayland[5298]: Libeis: 🪲 Bug: eis_device_stop_emulating: missing call to eis_device_frame() Mar 30 00:32:26 galaxy kwin_wayland[5298]: Libeis: 🪲 Bug: eis_device_stop_emulating: missing call to eis_device_frame() Mar 30 00:32:29 galaxy kwin_wayland[5298]: Libeis: 🪲 Bug: eis_device_stop_emulating: missing call to eis_device_frame() Mar 30 00:32:35 galaxy kwin_wayland[5298]: Libeis: 🪲 Bug: eis_device_stop_emulating: missing call to eis_device_frame() Mar 30 00:32:36 galaxy kwin_wayland[5298]: Libeis: 🪲 Bug: eis_device_stop_emulating: missing call to eis_device_frame() Mar 30 00:32:36 galaxy kwin_wayland[5298]: Libeis: 🪲 Bug: eis_device_stop_emulating: missing call to eis_device_frame() Mar 30 00:32:37 galaxy kwin_wayland[5298]: Libeis: 🪲 Bug: eis_device_stop_emulating: missing call to eis_device_frame() Mar 30 00:32:37 galaxy kwin_wayland[5298]: Libeis: 🪲 Bug: eis_device_stop_emulating: missing call to eis_device_frame() Mar 30 00:32:38 galaxy kwin_wayland[5298]: Libeis: 🪲 Bug: eis_device_stop_emulating: missing call to eis_device_frame() Mar 30 00:32:39 galaxy kwin_wayland[5298]: Libeis: 🪲 Bug: eis_device_stop_emulating: missing call to eis_device_frame() Mar 30 00:32:40 galaxy kwin_wayland[5298]: Libeis: 🪲 Bug: eis_device_stop_emulating: missing call to eis_device_frame() Mar 30 00:32:40 galaxy kwin_wayland[5298]: Libeis: 🪲 Bug: eis_device_stop_emulating: missing call to eis_device_frame() Mar 30 00:32:41 galaxy kwin_wayland[5298]: Libeis: 🪲 Bug: eis_device_stop_emulating: missing call to eis_device_frame() Mar 30 00:32:42 galaxy kwin_wayland[5298]: Libeis: 🪲 Bug: eis_device_stop_emulating: missing call to eis_device_frame() Mar 30 00:32:43 galaxy kwin_wayland[5298]: Libeis: 🪲 Bug: eis_device_stop_emulating: missing call to eis_device_frame() Mar 30 00:32:43 galaxy kwin_wayland[5298]: Libeis: 🪲 Bug: eis_device_stop_emulating: missing call to eis_device_frame() Mar 30 00:32:44 galaxy kwin_wayland[5298]: Libeis: 🪲 Bug: eis_device_stop_emulating: missing call to eis_device_frame() Mar 30 00:32:45 galaxy kwin_wayland[5298]: Libeis: 🪲 Bug: eis_device_stop_emulating: missing call to eis_device_frame() Mar 30 00:32:46 galaxy kwin_wayland[5298]: Libeis: 🪲 Bug: eis_device_stop_emulating: missing call to eis_device_frame() ``` There have been many bursts of this, but at 00:30ish I brought my laptop back online because I thought it was occurring because laptop was asleep, but not the case. With laptop online, I noticed it was still occurring at 00:32. So I intentionally moved the mouse back and fourth across the screen boundary, alternative devices, and it seems there is one error per crossing of the screen border. Both running Nobara 43 (43-6.fc43) with lan-mouse 0.10.0-1.fc43 No noticeable impact. Just reporting. I noticed it appearing in journalctl monitoring of 'err' and above.
Author
Owner

@feschber commented on GitHub (Apr 9, 2026):

I'm not 100% sure but it seems to be a bug in KDE. The errors are coming from libeis-device.c
@whot can you confirm?

<!-- gh-comment-id:4213022790 --> @feschber commented on GitHub (Apr 9, 2026): I'm not 100% sure but it seems to be a bug in KDE. The errors are coming from [libeis-device.c](https://gitlab.freedesktop.org/libinput/libei/-/blob/main/src/libeis-device.c?ref_type=heads#L1227) @whot can you confirm?
Author
Owner

@whot commented on GitHub (Apr 12, 2026):

This looks to be the same issue as seen in https://github.com/deskflow/deskflow/issues/9423, I'm pretty sure this is a kwin issue but couldn't quickly find a bug filed with kwin yet.

<!-- gh-comment-id:4232980805 --> @whot commented on GitHub (Apr 12, 2026): This looks to be the same issue as seen in https://github.com/deskflow/deskflow/issues/9423, I'm pretty sure this is a kwin issue but couldn't quickly find a bug filed with kwin yet.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/lan-mouse#215
No description provided.