I have been running winbox under wine for ages. Now I have installed a new Linux system, and I have an interesting new problem…
(it isn’t a winbox problem, the same thing happens when I run e.g. wordpad.exe so it is something related to wine or another system component)
My issue is this: when the monitor is turned OFF, either by power management (DPMS off after some idletime) or by me (pressing the button), the open window is reduced to a 2cm square in the upper left corner. It cannot be resized back either. I have to terminate the program (can be done right-clicking on the taskbar entry and closing it), the re-open it.
It seems to be that the X server aggressively detects power-off monitors, the system has Intel UHD integrated graphics.
Did anyone else see this and find a workaround for it? It is inconvenient as I have my PC on 24h/day and only switch off the monitor when not using it.
Googling for it I found absolutely nothing, but as there probably are a lot of wine users here, maybe someone has a hint?
In some version of wine, maybe ~6 months ago, I saw something similar on Mac. Occasionally.
e.g. Where if you enlarged winbox window by dragging corner — seemingly “too quickly” — it get to some size and winbox still redrawing larger. Not 10cm, but maybe 15-25% of my desktop “real estate” become the max when this happened. Further dragging would allow it to become smaller, but bigger just resize the WM window and leave whitespace beyond that initial size.
I don’t know about Linux… but disto’s wine may be behind, so may be using similar wine version where I saw this… Mikrotik seem to always push using very latest wine…
I’ve also been careful not “aggressively drag” the winbox window size, as you can see redraws lagging when you do.
And I want to say it was generally “long standing windows” (e.g. when I switch back to winbox after a while, & likely after some power mgmt thing). I never say the “lack of resizing” if I was actually using things. So may be onto something there with the power management…
Ok, but in my case it seems related to the display going to sleep, the X server somehow locking the applications (or informing them) and then wine incorrectly handling that.
I remember from the past when I enabled a screen saver in a system where programs were continuously displaying output, there would be an issue when the screen saver was active for too long and requests were apparently buffered somewhere in a limited buffer.
But in this case it can be reproduced just by switching the monitor OFF and ON, without long pause between.
But I have not seen any problem with the other (native) Linux applications running.
I don’t want to reboot at the moment but I think I will experiment with the X server config, at the moment it is running fully autodetect but in the past I have always built a xorg.conf explicitly defining the monitors and resolutions I want. Maybe turning off the monitor makes it lose the auto detected parameters for a while.
I don’t have much experience with winbox in this regard (usually I don’t have winbox open for extended periods of time), but my experience is that all windows applications running natively in windows 10 show similar behaviour. E.g. I have a laptop with two monitors connected (via DP). If any of them “goes missing” (e.g. due to powering it off), all windows jump to the other monitor. If both “go missing” (e.g. due to power black out), all windows shrink to some small window size and herd into upper left corner of workspace (as shown after monitors “come back”). In neither case none of windows restore to original size and/or position when normal desktop (with two monitors) resumes.
So it seems that difference between natively running and wine rinning is only in percieved desktop size when monitor(s), which normally define desktop size, disapear.
Which all indicates that @pe1chl might be right with regard to autodetection … only that in windows there isn’t such thing as manual desktop size (or so it seems to me).
Aha that is an interesting observation!
I will try to configure fixed resolutions to see if that solves it. Maybe it keeps the desktops active when the screen is off.
(I will have to plan some time for that to reboot the system into textmode and fiddle with xorg.conf, always a tedious and frustrating experience)