December 2021 - Wine-bugs - list.winehq.org

[Bug 52108] New: user32:monitor breaks user32:win on Win10 1809
by WineHQ Bugzilla 14 Jan '22

14 Jan '22

https://bugs.winehq.org/show_bug.cgi?id=52108 Bug ID: 52108 Summary: user32:monitor breaks user32:win on Win10 1809 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Created attachment 71132 --> https://bugs.winehq.org/attachment.cgi?id=71132 Windows 10 1809 "blurry popup" On 2021-09-01 user32:monitor started breaking user32:win on Windows 10 1809: win.c:3322: Test failed: GetActiveWindow() = 00220510 win.c:3325: Test failed: GetFocus() = 00000000 win.c:3337: Test failed: GetFocus() = 00000000 win.c:3340: Test failed: GetFocus() = 00000000 win.c:3343: Test failed: GetFocus() = 00000000 win.c:3346: Test failed: GetActiveWindow() = 00220510 win.c:3350: Test failed: GetFocus() = 00000000 win.c:3353: Test failed: GetFocus() = 00000000 win.c:4047: Test failed: hwnd 004A050A/003600CA message 0737 win.c:4052: Test failed: hwnd 003600CA/003600CA message 0202 win.c:4057: Test failed: hwnd 003600CA/003600CA message 0203 win.c:4061: Test failed: message 0202 available https://test.winehq.org/data/patterns.html#user32:win A bisect shows that the failures started with this commit: commit 2d51077a22b7d8faa9587d02a84181f58d1203aa Author: Zhiyi Zhang <zzhang(a)codeweavers.com> AuthorDate: Wed Sep 1 14:37:21 2021 +0800 user32/tests: Add DisplayConfigSetDeviceInfo() tests. Test that DisplayConfigSetDeviceInfo() can be used for getting and setting display DPI. Signed-off-by: Zhiyi Zhang <zzhang(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> What happens is that the new display tests cause Windows 10 1809 to display a notification that the "apps might be blurry". This notification stays up after user32:monitor completes and then steals the focus from the user32:win tests and causes them to fail. So there's not really anything wrong in either user32:monitor nor user32:win but this still causes test failures :-( -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 11

[Bug 43494] New: Microsoft Flight Simulator 2000 crashes when losing focus during flight
by wine-bugs＠winehq.org 14 Jan '22

14 Jan '22

https://bugs.winehq.org/show_bug.cgi?id=43494 Bug ID: 43494 Summary: Microsoft Flight Simulator 2000 crashes when losing focus during flight Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: an0n1m0(a)hotmail.it Distribution: --- Created attachment 58873 --> https://bugs.winehq.org/attachment.cgi?id=58873 log of the crash using +loaddll,fixme+all,warn+all,err+all During a flight, on Windows, if the game loses the focus, it is paused automatically (equivalent to pressing P). Under wine, the game crashes. The game behaves normally when a menu is opened (in this case, everything is paused, and the game doesn't crash). If I select in winecfg "emulate a virtual desktop", the game doesn't crash anymore because of this issue. I tested this behaviour on ubuntu with both unity and gnome3, under wine 1.6, wine stable (2.0.2) and wine-devel (2.16). The results were all the same. I attached the result of the following commands: export WINEDEBUG=+loaddll,fixme+all,warn+all,err+all wine start 'C:\Program Files\Microsoft Games\FS2000\FS2000.EXE' &>log.txt Then I started a flight and clicked outside of the game window (so that the crash occurs). -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

2 5

[Bug 43496] New: Microsoft Flight Simulator 2000 : game pauses when tooltips are shown
by wine-bugs＠winehq.org 14 Jan '22

14 Jan '22

https://bugs.winehq.org/show_bug.cgi?id=43496 Bug ID: 43496 Summary: Microsoft Flight Simulator 2000 : game pauses when tooltips are shown Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: an0n1m0(a)hotmail.it Distribution: --- Everytime one hovers the mouse on an instrument, then move the mouse out to let the tooltip disappear, the game pauses. The game normally should pause only when the game window loses focus (but when the whole window lose focus the game crashes, see bug #43494). This happens on all versions of wine from 1.6 to the latest devel (2.16). There is a workaround for this (as in #43494): enable virtual desktop on winecfg. Everytime I reproduce this behaviour (show tooltip, move the mouse, the tooltip disappears => game paused) this shows up in the terminal: warn:dsound:IDirectSound8Impl_SetCooperativeLevel level=DSSCL_PRIORITY not fully supported warn:dsound:DSOUND_PerformMix Probable buffer underrun -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

2 6

[Bug 43495] New: Microsoft Flight Simulator 2000 : blurry and purple text
by wine-bugs＠winehq.org 14 Jan '22

14 Jan '22

https://bugs.winehq.org/show_bug.cgi?id=43495 Bug ID: 43495 Summary: Microsoft Flight Simulator 2000 : blurry and purple text Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: an0n1m0(a)hotmail.it Distribution: --- Created attachment 58874 --> https://bugs.winehq.org/attachment.cgi?id=58874 text rendering comparison The text in the game looks really bad, compared to what it should look. See the attached image for a comparison. This behaviour is present on all versions of wine (tested from 1.6+ to devel). As a side note, it is rendered the same on Virtualbox running Windows XP. On native windows (tested on windows 8.1) it looks good. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

2 4

[Bug 47230] New: Provide hint in crash report module table to distinguish between Wine builtins cross-compiled to PE format and native overrides
by wine-bugs＠winehq.org 13 Jan '22

13 Jan '22

https://bugs.winehq.org/show_bug.cgi?id=47230 Bug ID: 47230 Summary: Provide hint in crash report module table to distinguish between Wine builtins cross-compiled to PE format and native overrides Product: Wine Version: 4.8 Hardware: x86-64 OS: Linux Status: NEW Severity: enhancement Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, as it says. Future Wine releases/builds will provide builtin modules by default in PE format. It will be harder to diagnose crash logs if users put native overrides in place as the modules table no longer provides the obvious hints in case of non-core / overridable dlls (ELF-PE hybrid, DWARF, load address range, 'name-<elf>'). Take bug 47226 for example: --- snip --- ... Modules: Module Address Debug info Name (160 modules) PE 130000- 13d000 Deferred ilmthread-2_2 PE 250000- 29b000 Deferred qt5winextras PE 2a0000- 6f7000 Deferred qt5gui PE 700000- 8f3000 Deferred libglesv2 PE 900000- e51000 Deferred qt5widgets PE e60000- e7e000 Deferred zlibwapi PE e80000- ef6000 Deferred lcms2 PE f00000- 11c2000 Deferred ilmimf-2_2 PE 11d0000- 1219000 Deferred half PE 1220000- 1236000 Deferred iex-2_2 PE 1240000- 1258000 Deferred imath-2_2 PE 1260000- 1389000 Deferred libraw PE 15f0000- 1721000 Deferred qwindows PE 1840000- 184d000 Deferred qico PE 1850000- 1890000 Deferred qjpeg PE 1890000- 18ec000 Deferred qtiff PE 61000000- 61034000 Deferred qt5xml PE 64000000- 640d3000 Deferred qt5network PE 65100000- 651a7000 Deferred msvcp110 PE 66500000- 66523000 Deferred vcomp110 PE 67000000- 67551000 Deferred qt5core ELF 7a800000- 7aa10000 Deferred opengl32<elf> \-PE 7a850000- 7aa10000 \ opengl32 ELF 7b400000- 7b85b000 Dwarf kernel32<elf> \-PE 7b420000- 7b85b000 \ kernel32 ELF 7bc00000- 7bd54000 Deferred ntdll<elf> \-PE 7bc20000- 7bd54000 \ ntdll ELF 7c000000- 7c004000 Deferred <wine-loader> PE 140000000- 1403ee000 Deferred easyhdr3 PE 180000000- 18004a000 Deferred openjp2 ... ELF 7f86d5ec7000- 7f86d5ef3000 Deferred version<elf> \-PE 7f86d5ed0000- 7f86d5ef3000 \ version ELF 7f86d5ef3000- 7f86d6298000 Dwarf libwine.so.1 ELF 7f86d629a000- 7f86d64c3000 Deferred ld-linux-x86-64.so.2 ELF 7ffc37f2a000- 7ffc37f2b000 Deferred [vdso].so Threads: process tid prio (all id:s are in hex) ... 00000058 (D) C:\Program Files\easyHDR 3 Demo\easyHDR3.exe ... 00000070 0 <== ... --- snip --- Here, 'msvcp110.dll' and 'vcomp110.dll' are Wine builtins in PE format. I propose to add a hint in the table for Wine builtin modules in PE format for easier diagnosis of crash reports. $ wine --version wine-4.8-202-g61aea5a987 Regards -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

2 3

[Bug 45540] New: WeGame: password input widget of login interface isn' t useable.
by wine-bugs＠winehq.org 13 Jan '22

13 Jan '22

https://bugs.winehq.org/show_bug.cgi?id=45540 Bug ID: 45540 Summary: WeGame: password input widget of login interface isn't useable. Product: Wine Version: 3.13 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jactry92(a)gmail.com Distribution: --- Created attachment 61946 --> https://bugs.winehq.org/attachment.cgi?id=61946 password input widget was marked by red Steps to reproduce: 1. $ winetricks -q mfc42 cjkfonts 2. $ wine WeGameMiniLoader.3.6.1.5080.gw.exe 3. $ cd .wine/drive_c/Program\ Files/WeGame 4. $ WINEDLLOVERRIDES="msvcr100=n" wine tgp_daemon.exe Expected: Users can input account and password for login. Actually: There is a crash of TASLogin.exe. Account input widget is useable but password doesn't work. Can't give input focus to it. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

2 3

[Bug 50717] New: Wine places 1x1 pixel window on top of fullscreen window, blocking direct scanout on Wayland
by WineHQ Bugzilla 13 Jan '22

13 Jan '22

https://bugs.winehq.org/show_bug.cgi?id=50717 Bug ID: 50717 Summary: Wine places 1x1 pixel window on top of fullscreen window, blocking direct scanout on Wayland Product: Wine-staging Version: 6.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: tempel.julian(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- KWin developer Xaver Hugl found this while investigating the cause of direct scanout getting blocked with Wine fullscreen windows on Wayland: "Wine puts a 1x1 pixel big override-redirect window on top of the fullscreen window that stops direct scanout. I'll add a workaround for now but at first glance looks like a Wine bug to me." https://invent.kde.org/plasma/kwin/-/merge_requests/718#note_191539 "I verified that it isn't caused by Xwayland / happens on a normal X session as well" https://invent.kde.org/plasma/kwin/-/merge_requests/728#note_191637 (this MR also contains the workaround, and indeed it makes direct scanout work with Wine) As a result, performance of fullscreen 3D Wine applications on Kwin Wayland git-master is negatively affected, as unnecessary compositing affects frame presentation and causes lots of dropped frames under high GPU load. It is well possible that this also negatively affects Gnome and Sway Wayland, but also Gnome unredirecting on Xorg. -staging and Proton are affected, might also apply to regular wine. It doesn't matter if WineD3D or DXVK is used (as this probably is very specific to Wine's window management and not the 3D API). It looks like if the proper fix was if Wine wouldn't spawn the 1x1 pixel window on top anymore. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 37332] New: Cannot run Rome Total War (installed / run from Steam)
by wine-bugs＠winehq.org 13 Jan '22

13 Jan '22

https://bugs.winehq.org/show_bug.cgi?id=37332 Bug ID: 37332 Summary: Cannot run Rome Total War (installed / run from Steam) Product: Wine Version: 1.7.25 Hardware: x86-64 OS: Mac OS X Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: winebugz.20.dllahr(a)xoxy.net Created attachment 49642 --> https://bugs.winehq.org/attachment.cgi?id=49642 output from running wine Brief version: I'm using wine 1.7.25 compiled from sources on a Mac probook running OS X 10.9.5. I was able successfully install and run Steam, log in to my Steam account, and have Steam download and install Rome Total War. When I attempt to run Rome Total War (either through the Steam interface or through the command line - which still calls Steam), I have managed to get it to display the initial screen, but then it either hangs (most of the time) or crashes. I tried running in a virtual desktop mode, no change in behavior. More info: I previously installed wine 1.6.2 using HomeBrew. Prior to compiling wine 1.7.25, I used HomeBrew to check for / install listed dependencies. I'm using WINEPREFIX=/opt/no_backup/wine Side note: I was able to get the game working on an ubuntu system running on virtualbox on this same Mac, however the performance was very slow - the mouse response was very, very slow. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

2 11

[Bug 47568] New: Napoleon Total War Steam
by wine-bugs＠winehq.org 13 Jan '22

13 Jan '22

https://bugs.winehq.org/show_bug.cgi?id=47568 Bug ID: 47568 Summary: Napoleon Total War Steam Product: Wine Version: unspecified Hardware: x86-64 OS: other Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: tylerpelletier(a)outlook.com Fresh install of pop os fresh install of wine and steam. I got napoleon total war definitive edition to install. Campaign runs fine. I go to launch a battle and I get a pop up saying "program error" is ready. the program has encountered a serious problem and needs to close I click for more details then it says please wait for details but that stalls I left the window open saying error details tried to launch the game to try to get more details and it says steam error 227 this time. closed it and it now launches. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

2 1

[Bug 47429] New: Medieval 2 total war gold crash on launch
by wine-bugs＠winehq.org 13 Jan '22

13 Jan '22

https://bugs.winehq.org/show_bug.cgi?id=47429 Bug ID: 47429 Summary: Medieval 2 total war gold crash on launch Product: Wine Version: 4.11 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dam.rocchi(a)gmail.com Distribution: --- Created attachment 64777 --> https://bugs.winehq.org/attachment.cgi?id=64777 Debug +loaddll,+module,+wgl in fresh 32 bot prefix Wine crash after launch, with message box "Unspecified error" and exit. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

2 1