| 2025-12-05 01:52:07 +0100 | _qw | (~eqw@user/eqw) (Ping timeout: 240 seconds) |
| 2025-12-05 02:39:07 +0100 | _qw | (~eqw@user/eqw) eqw |
| 2025-12-05 04:27:57 +0100 | td_ | (~td@i5387090C.versanet.de) (Ping timeout: 252 seconds) |
| 2025-12-05 04:29:49 +0100 | td_ | (~td@i5387091D.versanet.de) |
| 2025-12-05 04:42:39 +0100 | terrorjack | (~terrorjac@2a01:4f8:c17:9d11::) (Quit: The Lounge - https://thelounge.chat) |
| 2025-12-05 04:45:08 +0100 | terrorjack | (~terrorjac@2a01:4f8:c17:9d11::) terrorjack |
| 2025-12-05 08:28:53 +0100 | ft | (~ft@p508db844.dip0.t-ipconnect.de) (Quit: leaving) |
| 2025-12-05 09:49:29 +0100 | yecinem_ | (~yecinem@p200300ee0f126f000d549c7e946c2941.dip0.t-ipconnect.de) |
| 2025-12-05 12:14:10 +0100 | mkoskar | (~mkoskar@user/mkoskar) (Quit: mkoskar) |
| 2025-12-05 12:15:01 +0100 | Enrico63 | (~Enrico63@host-212-171-79-170.retail.telecomitalia.it) Enrico63 |
| 2025-12-05 12:32:46 +0100 | Enrico63 | (~Enrico63@host-212-171-79-170.retail.telecomitalia.it) (Quit: Client closed) |
| 2025-12-05 12:33:00 +0100 | Enrico63 | (~Enrico63@host-212-171-79-170.retail.telecomitalia.it) Enrico63 |
| 2025-12-05 12:33:59 +0100 | <Enrico63> | Very recently I've started using my laptop keyboard and pad (for the last few years I've mostly used external keyboard and mouse), and quite a few times it happens that the mouse cursor stops moving. The tapping works, it's just that moving one finger across the pad doesn't move the mouse cursor. I'm relatively confident that there's some |
| 2025-12-05 12:33:59 +0100 | <Enrico63> | combination of touching the pad-typing on the keyboard-something else that is causing the issue, but I don't know how to trigger it. Any help? |
| 2025-12-05 12:34:00 +0100 | <Enrico63> | If I put xmonad to sleep and wake it back, the cursor moves again, but obviously doing so is a bit annoying. |
| 2025-12-05 12:56:37 +0100 | mkoskar | (~mkoskar@user/mkoskar) mkoskar |
| 2025-12-05 13:06:20 +0100 | Enrico63 | (~Enrico63@host-212-171-79-170.retail.telecomitalia.it) (Quit: Client closed) |
| 2025-12-05 13:10:09 +0100 | yecinem_ | (~yecinem@p200300ee0f126f000d549c7e946c2941.dip0.t-ipconnect.de) (Ping timeout: 265 seconds) |
| 2025-12-05 13:18:25 +0100 | ChubaDuba | (~ChubaDuba@46.147.217.66) ChubaDuba |
| 2025-12-05 13:44:12 +0100 | Enrico63 | (~Enrico63@host-212-171-79-170.retail.telecomitalia.it) Enrico63 |
| 2025-12-05 13:51:25 +0100 | <deebo> | Enrico63: possibly palm detection gone bad |
| 2025-12-05 13:53:24 +0100 | <Enrico63> | Since everything else works, e.g. the whole keyboard, I can do whatever checks are needed when that happens. Is there anything I can do to check the state of the device? |
| 2025-12-05 13:54:03 +0100 | <Enrico63> | As in, is there any state I can dump to file right now (the cursor is working) vs when the issue happens, and then diff the 2 to see what changed? |
| 2025-12-05 13:54:10 +0100 | <Enrico63> | I mean, assuming anything changes.. |
| 2025-12-05 14:05:03 +0100 | Enrico63 | (~Enrico63@host-212-171-79-170.retail.telecomitalia.it) (Quit: Client closed) |
| 2025-12-05 14:26:20 +0100 | Enrico63 | (~Enrico63@host-212-171-79-170.retail.telecomitalia.it) Enrico63 |
| 2025-12-05 14:47:12 +0100 | yecinem_ | (~yecinem@p200300ee0f126f000d549c7e946c2941.dip0.t-ipconnect.de) |
| 2025-12-05 14:50:32 +0100 | Enrico63 | (~Enrico63@host-212-171-79-170.retail.telecomitalia.it) (Quit: Client closed) |