https://bugs.winehq.org/show_bug.cgi?id=42978
Bug ID: 42978 Summary: Softwares are sometimes running out of virtual desktop Product: Wine Version: 2.6 Hardware: x86-64 OS: FreeBSD Status: UNCONFIRMED Severity: trivial Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: adrien_fernandes2@hotmail.com
I always set all my PREFIXs with a virtual desktop to the size of my screen resolution (1920x1080). I'm using i3 and I don't know if this problem occurs with desktop environment but it happens on i3 for sure.
It happens since at least 2 years now and it really starts to be annoying. The workaround is to build Wine without xrandr support so games can not be started out of the virtual desktop. The thing is that it will still try to run the game out of the virtual desktop, in that case, it won't start and Wine will stop and will tell me that xrandr support is disabled or something like that (of course it is ! You shouldn't even have to tell me that cause I set a virtual desktop to avoid the problem, idiot).
The problem can occurs at any time when running a software. Just close it and restart the software will make Wine run enough fast to display the virtual desktop BEFORE the software so it will be displayed inside (it's just supposition, I have no idea if it is the reason to be honest but closing and restarting always do the trick). It won't happen everytime. Sometimes it will correctly run in the virtual desktop but, at around a bit more than 50%, it will run out of the virtual desktop.
If the virtual desktop is already running, the problem will NEVER occur (if, for example, I'm running Steam and starting a game from it or if I am using "explorer" and double clicking on an EXE).
It happens on Arch Linux, FreeBSD and NetBSD so it's not BSD related.
I use the workaround because I really hate when games change the resolution of my screen. "xrandr -s 1920x1080" will put the resolution back to its native resolution.
It can happen on ANYTHING, even winecfg or explorer. No error message, it seems to be a "normal" behavior of Wine, it just seems to be a matter of loading speed of Wine's virtual desktop but it already happened that even closing and running the software again still run it out of virtual desktop, it happens less than the first time but it can happen.