[Bug 31245] New: xrandr12 warcraft 3 regression

http://bugs.winehq.org/show_bug.cgi?id=31245

Bug #: 31245
           Summary: xrandr12 warcraft 3 regression
           Product: Wine
           Version: 1.5.9
          Platform: x86
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: winex11.drv
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]
    Classification: Unclassified

When i trying to change screen resolution in Warcraft 3 options, it show me
confirmation window "All ok, do you realy want to save this resolution", but
realy nothing happens, resolution does not change.

This is printed to stdout:

fixme:win:EnumDisplayDevicesW ((null),0,0x33f354,0x00000000), stub!
err:xrandr:xrandr12_set_current_mode Resolution change not successful --
perhaps display has changed?

In wine 1.5.8 all was ok.

[Bug 31245] xrandr12 warcraft 3 regression

http://bugs.winehq.org/show_bug.cgi?id=31245

--- Comment #1 from Henri Verbeet  2012-07-18 12:16:45 CDT ---
Seems to work fine here, could you attach a +xrandr log? Also, which video
card, drivers, etc. is that?

[Bug 31245] xrandr12 warcraft 3 regression

http://bugs.winehq.org/show_bug.cgi?id=31245

yves64  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #2 from yves64  2012-07-18 13:16:25 CDT ---
in Skyrim, I have this message

err:xrandr:xrandr12_init_modes Failed to get CRTC info.
fixme:win:EnumDisplayDevicesW ((null),0,0x32f784,0x00000000), stub!

I see the games but the screen resolution than the screen

I kill the game but I can not do xrandr-s 0

I am forced to use nvidia-settings

I will restart the game and it works, it just do it at boot sytem

[Bug 31245] xrandr12 warcraft 3 regression

http://bugs.winehq.org/show_bug.cgi?id=31245

Austin English  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |regression

[Bug 31245] xrandr12 warcraft 3 regression

http://bugs.winehq.org/show_bug.cgi?id=31245

--- Comment #3 from Fedor Fortochkin  2012-07-19 02:27:42 CDT ---
Sorry, i am not exactly put it...

My monitor have FullHD 1920x1080 resolution, but when xrandr enumerate list of
avalible modes it add 1920x1200 mode, that not valid.

When i run Warcraft 3 with "-opengl" parameter, and try to change resolution to
1920x1200 its say me that all is okay, but really nothing happens.

This is printed to console:

fixme:win:EnumDisplayDevicesW ((null),0,0x33f354,0x00000000), stub!
err:xrandr:xrandr12_set_current_mode Resolution change not successful --
perhaps display has changed?

When i run Warcraft 3 in Direct3D mode, when i trying to set invalid 1920x1200
mode, this drop me from game(may be segfault, i dont sure).

Sorry but now i can't to provide log, try to do it next week.

[Bug 31245] xrandr12 warcraft 3 regression

http://bugs.winehq.org/show_bug.cgi?id=31245

Jonathan Strander  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #4 from Jonathan Strander  2012-07-23 00:38:01 CDT ---
I wonder if this is related to a result I get with Wine 1.5.9 and NVIDIA Binary
304.22.

If I start a game (say, The Witcher 2, which I've been using to test Wine
changes) in a resolution other than the desktop's native resolution I end up
back at the native resolution but with a borderless window.

In 1.5.8 it would/does correctly give me an aspect-scaled fullscreen view.

The log doesn't give any indication that anything has gone wrong. I can however
attempt a regression test if requested.

Again, not sure if it's the exact same bug at play here but it sounds similar
enough to make me wonder (I had been planning on filing a separate bug).

[Bug 31245] xrandr12 warcraft 3 regression

http://bugs.winehq.org/show_bug.cgi?id=31245

--- Comment #5 from Jonathan Strander  2012-07-23 20:31:13 CDT ---
I talked to a NVIDIA dev and there's multiple things at play here. Partially
NVIDIA and partially a combination of Wine and a combination of GNOME. It's all
related however. I'll try and break it down:

First, with "org.gnome.settings-daemon.plugins.xrandr active" set to true
(check dconf-editor) it appears that for whatever reason the mode is restored
as soon as its set by another application (likely a GNOME bug but maybe
exacerbated by the NVIDIA driver). There's probably multiple things at work
there but setting it to "false" will allow Wine to set the resolution.

As far as not using any metamodes/gpu-scaling that has to do with how Wine uses
Randr 1.3 directly. Doing this bypasses anything the GPU driver would like to
do. The developer I spoke to didn't specify how to correct/work around this
behavior however, perhaps a talk with NVIDIA is in order.

A possible workaround for now (without any ./configure switches or registry
keys that I noticed to do the same) would be something like:

in dlls/winex11.drv/xrandr.c
+#ifdef HAVE_XRRGETSCREENRESOURCES
+    if (ret >= 2 && (major > 1 || (major == 1 && minor >= 2)))
+        xrandr12_init_modes();
+    else
+#endif
+        xrandr10_init_modes();

Removing the ifdef block.

[Bug 31245] xrandr12 warcraft 3 regression

http://bugs.winehq.org/show_bug.cgi?id=31245

--- Comment #6 from Jonathan Strander  2012-07-23 20:32:30 CDT ---
Erm, just to note that would revert wine to the old Randr 1.1 behavior. Which
isn't a "fix" so much as a hack.

[Bug 31245] xrandr12 warcraft 3 regression

http://bugs.winehq.org/show_bug.cgi?id=31245

yves64  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|[e-mail]        |

[Bug 31245] xrandr12 warcraft 3 regression

http://bugs.winehq.org/show_bug.cgi?id=31245

--- Comment #7 from Henri Verbeet  2012-07-24 04:19:18 CDT ---
(In reply to comment #5)
> First, with "org.gnome.settings-daemon.plugins.xrandr active" set to true
> (check dconf-editor) it appears that for whatever reason the mode is restored
> as soon as its set by another application (likely a GNOME bug but maybe
> exacerbated by the NVIDIA driver). There's probably multiple things at work
> there but setting it to "false" will allow Wine to set the resolution.

Yeah, from your description that sounds like it would be some kind of GNOME
issue, although it's perhaps mildly surprising that it would only do that for
RandR 1.2 / 1.3 mode changes. In principle that would mean you'd see the same
behaviour if you used the xrandr utility to change the display mode. You don't
mention if you have a multihead setup or not, but I suppose that could be a
factor as well.
> As far as not using any metamodes/gpu-scaling that has to do with how Wine uses
> Randr 1.3 directly. Doing this bypasses anything the GPU driver would like to
> do. The developer I spoke to didn't specify how to correct/work around this
> behavior however, perhaps a talk with NVIDIA is in order.

Well, the standard / correct way to control scaling mode is through the
corresponding RandR property. Wine doesn't touch the scaling mode in any way
though, so the reasonable thing for the driver to do would be to just keep
whatever scaling mode was previously set by the user.

[Bug 31245] xrandr12 warcraft 3 regression

http://bugs.winehq.org/show_bug.cgi?id=31245

--- Comment #8 from Jonathan Strander  2012-07-24 06:50:05 CDT ---
For the first part(In reply to comment #7)
> (In reply to comment #5)
> > First, with "org.gnome.settings-daemon.plugins.xrandr active" set to true
> > (check dconf-editor) it appears that for whatever reason the mode is restored
> > as soon as its set by another application (likely a GNOME bug but maybe
> > exacerbated by the NVIDIA driver). There's probably multiple things at work
> > there but setting it to "false" will allow Wine to set the resolution.
>
> Yeah, from your description that sounds like it would be some kind of GNOME
> issue, although it's perhaps mildly surprising that it would only do that for
> RandR 1.2 / 1.3 mode changes. In principle that would mean you'd see the same
> behaviour if you used the xrandr utility to change the display mode. You don't
> mention if you have a multihead setup or not, but I suppose that could be a
> factor as well.

No, only a single monitor/display.
> > As far as not using any metamodes/gpu-scaling that has to do with how Wine uses
> > Randr 1.3 directly. Doing this bypasses anything the GPU driver would like to
> > do. The developer I spoke to didn't specify how to correct/work around this
> > behavior however, perhaps a talk with NVIDIA is in order.
>
> Well, the standard / correct way to control scaling mode is through the
> corresponding RandR property. Wine doesn't touch the scaling mode in any way
> though, so the reasonable thing for the driver to do would be to just keep
> whatever scaling mode was previously set by the user.

I really couldn't say how NVIDIA does it, although I do know that a user can
set both [say] 1920x1080 or 1920x1200 with a 1920x1080 region. I'm not sure how
it distinguishes (although obviously it automatically does the correct thing 
when set by old versions of RandR). Which is another reason why I suggested
talking to NVIDIA since only they can tell you what's going on behind the
scenes.

[Bug 31245] xrandr12 warcraft 3 regression

http://bugs.winehq.org/show_bug.cgi?id=31245

Sandor Geller  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #9 from Sandor Geller  2012-12-18 04:04:20 CST ---
commit cf6f8d2eb50aa28829ee2b76c61aab411f8730ae broke Warcraft III on my system
as well but with a different symptom: the game starts but the menus don't
appear, all I can do is quit using the ESC key. I'm using OpenGL mode for the
game otherwise my system is quite different from the first reporter's: AMD
HD6850 card (driven by fglrx 12.11beta11), KDE 4.9.4 is the DE.

[Bug 31245] xrandr12 warcraft 3 regression

http://bugs.winehq.org/show_bug.cgi?id=31245

jcp  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #10 from jcp  2013-04-11 16:42:48 CDT ---
I confirm the regression with wine 1.5.27 (it's ok with the 1.5.8 version).
I'm under Gentoo x86_64, KDE 4.10.2, Nvidia-drivers-313.30, xrand-1.3.5 with a
GTX-260 from Nvidia.

About the /etc/X11/xorg.conf, I've got the following lines:

Section "Screen"

Identifier  "Screen 1"
    Device      "260GTX"
    Monitor     "AX3818UTC"
    DefaultDepth 24

SubSection "Display"
        Depth           24
        Modes           "1680x1050" "1440x900" "1400x1050" "1280x1024"
"1280x960" "1152x864" "1024x768" "800x600" "640x480"
        ViewPort        0 0
    EndSubsection

Option "ConnectToAcpid" "false"
    Option  "metamodes" "DVI-I-3: nvidia-auto-select { ViewPortIn=1680x1050 };
DVI-I-3: nvidia-auto-select { ViewPortIn=1400x1050, ViewPortOut=1400x1050+140+0
}"

EndSection

My native resolution is 1680x1050 and Warcraft III works in 4:3 mode in
1400x1050 with the wine-1.5.8.
Under wine-1.5.27, the 1400x1050 resolution is not active in the game and all
is stretched.

[Bug 31245] xrandr12 warcraft 3 regression

http://bugs.winehq.org/show_bug.cgi?id=31245

--- Comment #11 from Sandor Geller  2013-05-02 16:10:46 CDT ---
TEsted using wine 1.5.29 using a new WINEPREFIX to ensure that other apps won't
mess up settings. The game installed and ran fine, even in-game videomode
switching worked perfectly until I used it in OpenGL mode. My monitor is set to
its native 1920x1200 resolution while the game supports up to 1600x1200 so I
set this resolution in the menu. I noticed that selecting 1400x1050 resolution
(which is supported by the monitor) I got 1600x1200 instead.

Running the game using OpenGL the video was stretched and clipped so the menu
displayed on the right side was only partially visible. The mouse cursor was in
the 1600x1200 rectangle so couldn't enter the dead / invisible area.

Using WINEDEBUG=+opengl,+xrender I got the following logs:

trace:xrandr:X11DRV_XRandR_Init Found XRandR 1.4.
trace:xrandr:xrandr12_init_modes CRTC 0: mode 0xa1, 1920x1200+0+0.
trace:xrandr:xrandr12_init_modes OUTPUT 0: name "DFP6".
trace:xrandr:xrandr12_init_modes Adding mode 0xa1: 1920x1200@60.
trace:xrandr:xrandr12_init_modes Adding mode 0xa2: 1920x1080@60.
trace:xrandr:xrandr12_init_modes Adding mode 0xa3: 1600x1200@60.
[ more modes follow, then the whole gets repeated 5 more times ]
fixme:win:EnumDisplayDevicesW ((null),0,0x33f258,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x33f5a0,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x33f5d0,0x00000000), stub!
trace:xrandr:xrandr12_set_current_mode CRTC 0: mode 0xa1, 1920x1200+0+0.
trace:opengl:glGetIntegerv (34018, 0x6fae36a8)
trace:opengl:glMatrixMode (5888)
[ ... ]
trace:opengl:glViewport (0, 0, 1920, 1200)
trace:opengl:glDepthRange (0.000000, 1.000000)
trace:opengl:glScissor (0, 0, 1920, 1200)

Looks like the original 1920x1200 resolution was used for the OpenGL context
however the resolution was switched to 1600x1200 mode. Surprisingly this mode
switch wasn't logged anywhere, only the last but one logline (when the game was
exiting) showed a mode switch:

[ .. lots of texture deletion messages ]
trace:opengl:glDeleteTextures (1, 0x3bf0108)
trace:xrandr:xrandr12_set_current_mode CRTC 0: mode 0xa3, 1600x1200+0+0.
fixme:msvcrt:__clean_type_info_names_internal (0x150591a0) stub

If I use xrandr to switch to the resolution set in the game then OpenGL mode
works as long as I'm using that resolution, the first in-game mode switch
results in  stretching / clipping, choosing some resolutions could cause such
clipping that the whole menu gets missing similarly to my previous report.

[Bug 31245] xrandr12 warcraft 3 regression

http://bugs.winehq.org/show_bug.cgi?id=31245

Benjamin Hodgetts  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
                 CC|                            |[e-mail]
     Ever Confirmed|0                           |1

--- Comment #12 from Benjamin Hodgetts  2013-05-18 18:20:49 CDT ---
This actually affects pretty much anything that tries to change screenmode,
leaving you with a broken mess. NVidia binary driver specific.

[Bug 31245] xrandr12 warcraft 3 regression

http://bugs.winehq.org/show_bug.cgi?id=31245

--- Comment #13 from Benjamin Hodgetts  2013-05-18 18:44:11 CDT ---
Created attachment 44497
  --> http://bugs.winehq.org/attachment.cgi?id=44497
Diablo 2 video test log

Diablo 2 for example, fails the Video test and assumes you can't run the game
because of this. After it tries to run the test it just leaves the screen
640x480, pannable to your original resolution, and horribly corrupted.

Will attach console log.

[Bug 31245] xrandr12 warcraft 3 regression

http://bugs.winehq.org/show_bug.cgi?id=31245

Sebastian Riemer  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #14 from Sebastian Riemer  2013-06-07 01:38:34 CDT ---
*** Bug 33702 has been marked as a duplicate of this bug. ***

[Bug 31245] xrandr12 warcraft 3 regression

http://bugs.winehq.org/show_bug.cgi?id=31245

--- Comment #15 from Sebastian Riemer  2013-06-07 01:55:04 CDT ---
Carmageddon TDR 2000 with nvidia proprietary driver and single monitor is also
affected.

It starts at the intro videos where one has to move the mouse pointer into the
upper left corner in order to see the videos completely. Afterwards there are
no further issues with that.

[Bug 31245] xrandr12 warcraft 3 regression

http://bugs.winehq.org/show_bug.cgi?id=31245

Sven  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

[Bug 31245] xrandr12 warcraft 3 regression

http://bugs.winehq.org/show_bug.cgi?id=31245

CommonOddity  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #16 from CommonOddity  2013-09-11 06:00:00 CDT ---
This seems to still persist with 1.7.1:

commonoddity@linux-1uy2:~/Desktop> sh wc
err:ole:CoCreateInstance apartment not initialised
fixme:win:EnumDisplayDevicesW ((null),0,0x33f2f8,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x33f598,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x33f5c8,0x00000000), stub!
commonoddity@linux-1uy2:~/Desktop> err:xrandr:xrandr12_set_current_mode
Resolution change not successful -- perhaps display has changed?

Just tried running Warcraft 3, and it borks weirdly. It supposedly attempts to
change the resolution to 1024x768, but instead it turns it into a large desktop
where the resolution is "zoomed in" (if that makes any sense).

OpenSuSE 12.3, 32-bit
Packages from update repo
Nvidia Blob 325.08, single screen (1920x1080 60hz capable- usual res)
Vanilla kernel from update repos (kernel-desktop in particular)

[Bug 31245] xrandr12 warcraft 3 regression

http://bugs.winehq.org/show_bug.cgi?id=31245

--- Comment #17 from Henri Verbeet  2013-09-11 09:39:56 CDT ---
This bug is pretty messy, but afaik this is mostly caused by the
"org.gnome.settings-daemon.plugins.xrandr active" setting mentioned in comment
#5, so the easiest way to get this fixed may be to ask the GNOME people to look
into that.

[Bug 31245] xrandr12 warcraft 3 regression

http://bugs.winehq.org/show_bug.cgi?id=31245

Lara Maia  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

[Bug 31245] xrandr12 warcraft 3 regression

http://bugs.winehq.org/show_bug.cgi?id=31245

[e-mail] changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #18 from [e-mail] ---
I can confirm that this bug also exists when using WindowMaker as the window
manager, so I am unsure as to whether or not this a GNOME specific bug.(In
reply to Henri Verbeet from comment #17)

[Bug 31245] xrandr12 warcraft 3 regression

https://bugs.winehq.org/show_bug.cgi?id=31245

--- Comment #19 from Lara Maia  ---
This bug affect others apps like Carmageddon TDR 2000 and Battle City Remake.
Please, remove "warcraft 3" from bug title.

[Bug 31245] xrandr12 warcraft 3 regression

https://bugs.winehq.org/show_bug.cgi?id=31245

Maxime Buffa  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #20 from Maxime Buffa  ---
I can confirm this bug occuring with:

- Age of Wonders (downloaded from GOG),
- a freshly installed Manjaro 64 bits,
- XFCE 4.10,
- in a single monitor setup,
- nvidia proprietary drivers (340.32),
- either wine 1.6.2 or 1.7.27.

I got the same result as Comment #16 (a sort-of magnified and broken up version
of my desktop environment).

+xrandr log: http://pastebin.com/Q8j9HzF9

[Bug 31245] xrandr12 warcraft 3 regression

https://bugs.winehq.org/show_bug.cgi?id=31245

Fab  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #21 from Fab  ---
Confirming on gentoo with :
 - old good Driver : http://en.wikipedia.org/wiki/Driver_%28video_game%29
 - wine 1.7.28
 - a new WINEPREFIX
 - single monitor setup
 - nvidia-drivers-346.47
 - Xfce-4.10

In logs I got :
> err:xrandr:xrandr12_set_current_mode Resolution change not successful -- perhaps display has changed?

However seems to work fine into virtual desktop.

[Bug 31245] xrandr12 warcraft 3 regression

https://bugs.winehq.org/show_bug.cgi?id=31245

wine user  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]
                   |                            |m

--- Comment #22 from wine user  ---
This is very nasty old bug and, besides Warcraft 3, it's affects too many
applications and users due to its nature (probably NVIDIA only related).

Can it be fixed or at least workaround to *normally* work on vanilla wine ?
It's impossible to use *any* wine version after 1.5.8 (commit
cf6f8d2eb50aa28829ee2b76c61aab411f8730ae) without the hack from
https://bugs.winehq.org/show_bug.cgi?id=31245#c5 and recompiling wine version
manually.

It is not GNOME related in general, since I start wine application in separate
X server without DM.

[Bug 31245] xrandr12 warcraft 3 regression

https://bugs.winehq.org/show_bug.cgi?id=31245

[e-mail]  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #23 from [e-mail]  ---
Very surprising: Blizzard has updated "Warcraft III". 
How to update:
you have to use a legal copy of "Warcraft III" and the serial key.
Launch Warcraft III and click on "Battle.net" button, this will launch the
update.
Next time you launch the game, verify again you have the last update on
clicking again on "Battle.net" button.

With this new version, no need to launch Warcraft III with -opengl or -window
options, no crash at start neither.

I updated my Warcraft III version with WIne 2.16 staging.
The last update installed the 1.28.5.7680 Warcraft III version.

Could you still reproduce this bug with the last Warcraft III and Wine version?

[Bug 31245] xrandr12 warcraft 3 regression

https://bugs.winehq.org/show_bug.cgi?id=31245

--- Comment #24 from Sandor Geller  ---
The current game version (1.28.5.7680 downloaded from battle.net by the
auto-updater) works quite differently than the version installed from the CD.
The new version doesn't even seem to change the resolution of the display in
fullscreen mode but seems to use software scaling. I'll try to reproduce the
original issue but it involves reinstalling the CD version and disabling the
auto-updater somehow so could take some time.

BTW the cinematics aren't working for me (I installed every gstreamer 32-bit
plugins I found on Ubuntu 17.04 so at least the game doesn't crash when
cinematics would get played): the screen is blank, sound is playing though.

[Bug 31245] xrandr12 warcraft 3 regression

https://bugs.winehq.org/show_bug.cgi?id=31245

--- Comment #25 from Sandor Geller  ---
Reinstalled Warcraft III: Reign of Chaos without an active internet connection
so it remained at v1.14. This version changes the screen resolution instead of
scaling and worked prefectly both in windowed and in OpenGL mode so I can
confirm that the issue I had is no longer present. I tested using wine version
2.21.

[Bug 31245] xrandr12 warcraft 3 regression

https://bugs.winehq.org/show_bug.cgi?id=31245

tokktokk  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

[Bug 31245] xrandr12 warcraft 3 regression

https://bugs.winehq.org/show_bug.cgi?id=31245

Fernando Martins  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #26 from Fernando Martins  ---
This bug also appears to affect Conquest Frontier Wars on wine 3.10 with nvidia
prorietary drivers (384.130). Complete messages:

0009:err:richedit:ReadStyleSheet skipping optional destination
0009:fixme:win:EnumDisplayDevicesW ((null),0,0x32f2c4,0x00000000), stub!
0009:fixme:ddraw:DirectDrawEnumerateExA flags 0x00000006 not handled
0009:fixme:win:EnumDisplayDevicesW ((null),0,0x32c824,0x00000000), stub!
0009:fixme:ddraw:DirectDrawEnumerateExA flags 0x00000006 not handled
0009:fixme:win:EnumDisplayDevicesW ((null),0,0x3289f4,0x00000000), stub!
0009:fixme:win:EnumDisplayDevicesW ((null),0,0x328d74,0x00000000), stub!
0009:err:xrandr:xrandr12_set_current_mode Resolution change not successful --
perhaps display has changed?
0009:err:xrandr:xrandr12_set_current_mode Resolution change not successful --
perhaps display has changed?

[Bug 31245] xrandr12 warcraft 3 regression

https://bugs.winehq.org/show_bug.cgi?id=31245

Ilya Basin  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

[Bug 31245] xrandr12 warcraft 3 regression

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=31245

Linards  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #27 from Linards  ---
Is this issue still present?

[Bug 31245] xrandr12 warcraft 3 regression

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=31245

--- Comment #28 from CommonOddity  ---
That depends on your perspective... If you're looking at the original client
prior to the post Warcraft 3 reforged re-work? The issue appeared to persist
last time I ran it.

Mind you, that was 2 years ago and quite a few wine versions ago (I believe out
of the 4.x series branch? I can't recall the exact version).

Post Warcraft 3 reforged re-work? Nope. The client behaves as it should.
Resolutions and alt-tabbing are no longer an issue, really. It works well.

[Bug 31245] xrandr12 warcraft 3 regression

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=31245

joaopa  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #29 from joaopa  ---
Does the bug still occur with vanilla wine-7.0-rc5?

[Bug 31245] xrandr12 warcraft 3 regression

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=31245

--- Comment #30 from Ken Sharp  ---
(In reply to CommonOddity from comment #28)
> That depends on your perspective... If you're looking at the original client
> prior to the post Warcraft 3 reforged re-work? The issue appeared to persist
> last time I ran it.

In all cases the original client should be checked against the bug report (if
possible).

Does this still occur in Wine 9.8 or later?