You are not logged in.
Pages: 1
Topic closed
I haven't been using dosbox in a while, but it seems that some recent upgrade (certainly within last month) made all my games, on two different machines, unable to capture mouse (ctrl+f10 doesn't work either). I have tried to downgrade some of the packages (like xorg-xinput, libinput), but the list of potential candidates is couple dozen long. Any clue which direction I should look? Anyone noticing the same issue?
Last edited by kmiernik (2018-06-01 10:01:18)
Offline
Which general environment? Most logical connection would be that you run on Wayland and that the corresponding XWayland implementation that got updated with xorg-server 1.20 doesn't implement the mouse capture as expected.
Online
I've also been having this issue with dosbox. I can get the mouse to work if I make dosbox fullscreen, but then theres a constant cursor flickering in the middle of the screen. I had fixed the issue by downgrading my packages to 5/16/2018.
[2018-05-21 22:33] [ALPM] downgraded xdg-utils (1.1.3-1 -> 1.1.2-2)
[2018-05-21 22:33] [ALPM] downgraded libdrm (2.4.92-1 -> 2.4.91-3)
[2018-05-21 22:33] [ALPM] downgraded libinput (1.10.7-1 -> 1.10.6-1)
[2018-05-21 22:33] [ALPM] downgraded wayland (1.15.0-1 -> 1.14.0-1)
[2018-05-21 22:33] [ALPM] downgraded mesa (18.0.3-4 -> 18.0.3-1)
[2018-05-21 22:33] [ALPM] downgraded ndctl (60.2-1 -> 60.1-1)
[2018-05-21 22:33] [ALPM] downgraded wayland-protocols (1.14-1 -> 1.13-1)
[2018-05-21 22:33] [ALPM] downgraded xorg-server-common (1.20.0-2 -> 1.19.6+13+gd0d1a694f-2)
[2018-05-21 22:33] [ALPM] downgraded xorg-server (1.20.0-2 -> 1.19.6+13+gd0d1a694f-2)
So I think it has to be one of these packages causing the issue for me, but I'm not sure exactly which.
Offline
Which general environment? Most logical connection would be that you run on Wayland and that the corresponding XWayland implementation that got updated with xorg-server 1.20 doesn't implement the mouse capture as expected.
I tested the following environments: lxde, lxqt, gnome-xorg, gnome-wayland. All the same, so it is not connected to the Wayland directly.
I've also been having this issue with dosbox. I can get the mouse to work if I make dosbox fullscreen, but then theres a constant cursor flickering in the middle of the screen. I had fixed the issue by downgrading my packages to 5/16/2018.
(...)
So I think it has to be one of these packages causing the issue for me, but I'm not sure exactly which.
Thanks, I confirm that in the full screen mode, the mouse works. I will try to downgrade packages from your list and figure out which one is causing the trouble.
Offline
The troublesome package is the xorg-server. After downgrade to 1.19.6+13+gd0d1a694f-2, mouse is being captured in the window mode, and there is no flickering in either mode. This downgrade also requires removal of xf86-video-intel. Should this be reported as a bug in dosbox or rather xorg-server?
Offline
Hard to say, if this is just in dosbox it might be an issue with how dosbox implements that, or it's a unexpected regression in xorg-server. I'd probably initially go for xorg to be at fault unless it is shown that dosbox uses wrong/outdated API
Online
I also have this problem. Are we expecting it to get fixed in a future version of xorg-server?
Offline
Are we expecting it to get fixed in a future version of xorg-server?
Not until someone troubleshoots the issue further*.
Some comments :
try running xorg 1.20 with modesetting (remove any xf86-video-* packages)
What type of mouse is this happening with : usb , ps2 , touchpad ?
If dosbox is started on it's own x-server, does this also happen ?
* atm all we know is that dosbox + xorg server 1.20 mouse capturing is not working, while same dosbox + xorg-server 1.19 works
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Hi,
I don't know how much this helps, but I'm having the same problem on Void Linux with dosbox and xorg-server 1.20, and setting
autolock=false
in ~/.dosbox/dosbox-0.74.conf circumvents the problem for me.
Offline
I just found that I face the same issue. Running the game that requires mouse will crash immediately. My only solution is to use the DOSBox for Windows, extract, and run with Wine.
wine ./DOSBox.exe -conf game.conf
Offline
Setting
autolock=false
worked for me also.
Last edited by Scritch (2018-11-24 19:00:12)
Offline
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
Pages: 1
Topic closed