On Sun, Aug 28, 2022 at 08:20:34PM +0200, Walter Alejandro Iglesias wrote: > On Aug 27 2022, Crystal Kolipe wrote: > > On Sat, Aug 27, 2022 at 01:07:30PM +0200, Walter Alejandro Iglesias wrote: > > > X crashes when moving cursor from keyboard bindings. I can reproduce > > > the bug with cwm, fvwm or fvwm2 (because this window managers have that > > > option). According to the logs the cause could be in wsmouse. > > > > Can you reproduce this using the window-move and window-resize functions > > of cwm? Or is it strictly the pointer-move functions that cause it? > > > > For example: > > > > bind-key C-Up window-move-up > > bind-key C-Down window-move-down > > bind-key C-Left window-move-left > > bind-key C-Right window-move-right > > bind-key M-Up window-move-up-big > > bind-key M-Down window-move-down-big > > bind-key M-Left window-move-left-big > > bind-key M-Right window-move-right-big > > bind-key 4-Up window-resize-up-big > > bind-key 4-Down window-resize-down-big > > bind-key 4-Left window-resize-left-big > > bind-key 4-Right window-resize-right-big > > That's exactly how I reproduced it the first time. When I noticed that > moving the cursor alone produced the same effect (having in mind that > the commands above also move the cursor) I thought it could be the > cursor, but perhaps it's the keyboard input what makes X crash, I don't > know.
I have not been able to reproduce this problem here so far, and I've used X without a mouse on OpenBSD on various machines for over a decade, on a daily basis. So either the issue has been introduced very recently, or it is only triggerable on particular hardware configurations. Can you test an older -release and see if you can reproduce it? Does it happen if you use the 'Pointer_EnableKeys' directive in .Xmodmap? For example, if you configure the right hand ALT key with: keycode 113 = Pointer_EnableKeys Pointer_Accelerate Then with X running, hit the right ALT key and you should be able to move the mouse pointer with the numeric keypad. > PS: Crystal, your @exoticsilicon.com address returns my messages. Yes, your mailserver doesn't support TLS 1.3, so we reject your connection. This is intentional. Please tell your ISP to upgrade their mailserver.