Newest at the top
| 2025-12-05 16:41:04 +0100 | ft | (~ft@p508db844.dip0.t-ipconnect.de) ft |
| 2025-12-05 16:13:51 +0100 | Enrico63 | (~Enrico63@host-212-171-79-170.pool212171.interbusiness.it) (Quit: Client closed) |
| 2025-12-05 15:53:41 +0100 | Enrico63 | (~Enrico63@host-212-171-79-170.pool212171.interbusiness.it) Enrico63 |
| 2025-12-05 14:50:32 +0100 | Enrico63 | (~Enrico63@host-212-171-79-170.retail.telecomitalia.it) (Quit: Client closed) |
| 2025-12-05 14:47:12 +0100 | yecinem_ | (~yecinem@p200300ee0f126f000d549c7e946c2941.dip0.t-ipconnect.de) |
| 2025-12-05 14:26:20 +0100 | Enrico63 | (~Enrico63@host-212-171-79-170.retail.telecomitalia.it) Enrico63 |
| 2025-12-05 14:05:03 +0100 | Enrico63 | (~Enrico63@host-212-171-79-170.retail.telecomitalia.it) (Quit: Client closed) |
| 2025-12-05 13:54:10 +0100 | <Enrico63> | I mean, assuming anything changes.. |
| 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: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:51:25 +0100 | <deebo> | Enrico63: possibly palm detection gone bad |
| 2025-12-05 13:44:12 +0100 | Enrico63 | (~Enrico63@host-212-171-79-170.retail.telecomitalia.it) Enrico63 |
| 2025-12-05 13:18:25 +0100 | ChubaDuba | (~ChubaDuba@46.147.217.66) ChubaDuba |
| 2025-12-05 13:10:09 +0100 | yecinem_ | (~yecinem@p200300ee0f126f000d549c7e946c2941.dip0.t-ipconnect.de) (Ping timeout: 265 seconds) |
| 2025-12-05 13:06:20 +0100 | Enrico63 | (~Enrico63@host-212-171-79-170.retail.telecomitalia.it) (Quit: Client closed) |
| 2025-12-05 12:56:37 +0100 | mkoskar | (~mkoskar@user/mkoskar) mkoskar |
| 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: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: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:00 +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:15:01 +0100 | Enrico63 | (~Enrico63@host-212-171-79-170.retail.telecomitalia.it) Enrico63 |
| 2025-12-05 12:14:10 +0100 | mkoskar | (~mkoskar@user/mkoskar) (Quit: mkoskar) |
| 2025-12-05 09:49:29 +0100 | yecinem_ | (~yecinem@p200300ee0f126f000d549c7e946c2941.dip0.t-ipconnect.de) |
| 2025-12-05 08:28:53 +0100 | ft | (~ft@p508db844.dip0.t-ipconnect.de) (Quit: leaving) |
| 2025-12-05 04:45:08 +0100 | terrorjack | (~terrorjac@2a01:4f8:c17:9d11::) terrorjack |
| 2025-12-05 04:42:39 +0100 | terrorjack | (~terrorjac@2a01:4f8:c17:9d11::) (Quit: The Lounge - https://thelounge.chat) |
| 2025-12-05 04:29:49 +0100 | td_ | (~td@i5387091D.versanet.de) |
| 2025-12-05 04:27:57 +0100 | td_ | (~td@i5387090C.versanet.de) (Ping timeout: 252 seconds) |
| 2025-12-05 02:39:07 +0100 | _qw | (~eqw@user/eqw) eqw |
| 2025-12-05 01:52:07 +0100 | _qw | (~eqw@user/eqw) (Ping timeout: 240 seconds) |
| 2025-12-04 23:55:05 +0100 | <geekosaur> | wrong channel's bot 😛 |
| 2025-12-04 23:54:57 +0100 | <lambdabot> | Consider it noted. |
| 2025-12-04 23:54:57 +0100 | <geekosaur> | @tell vitis make sure nothing else is grabbing the keys |
| 2025-12-04 23:54:32 +0100 | <geekosaur> | !tell vitis make sure nothing else is grabbing the keys |
| 2025-12-04 23:53:54 +0100 | vitis | (~vitis@109-81-17-4.rct.o2.cz) (Quit: WeeChat 4.8.0) |
| 2025-12-04 23:53:46 +0100 | <vitis> | anyway it's late i need to sleep |
| 2025-12-04 23:53:42 +0100 | <vitis> | no errors but when i press the key it did nothing |
| 2025-12-04 23:53:25 +0100 | <vitis> | i already did import that and the bind still wasn't working |
| 2025-12-04 21:36:29 +0100 | <geekosaur> | *ExtraTypes |
| 2025-12-04 21:36:18 +0100 | <geekosaur> | two of those would be type errors, two of them might also raise "undefined symbol" errors unless you import Graphics.X11.EtraTypes.XF86 |
| 2025-12-04 21:34:09 +0100 | <L29Ah> | works here |
| 2025-12-04 21:34:07 +0100 | <L29Ah> | XF86AudioLowerVolume |
| 2025-12-04 21:34:07 +0100 | <L29Ah> | XF86AudioRaiseVolume |
| 2025-12-04 21:34:07 +0100 | <L29Ah> | ‰ grep -i volume ~/.xbindkeysrc |
| 2025-12-04 21:33:14 +0100 | <geekosaur> | what is "doesn't work"? |
| 2025-12-04 21:26:12 +0100 | <vitis> | i've tried (0,xF86XK_AudioRaiseVolume) , keysymToString xF86XK_AudioRaiseVolume , "XF86AudioRaiseVolume" and some other ways to bind it and it just doesn't work |
| 2025-12-04 21:24:31 +0100 | <vitis> | anyone here can help me getting XF86AudioRaiseVolume and LowerVolume keybinds to work? I've tried multiple different solutions and the keybinds never work |
| 2025-12-04 21:20:24 +0100 | vitis | (~vitis@109-81-17-4.rct.o2.cz) |
| 2025-12-04 19:09:25 +0100 | ft | (~ft@p508db844.dip0.t-ipconnect.de) ft |