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

[Bug 46104] New: winepulse-PulseAudio_Support patch cause application to hang with native dsound.dll
by wine-bugs＠winehq.org 31 Mar '19

31 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=46104 Bug ID: 46104 Summary: winepulse-PulseAudio_Support patch cause application to hang with native dsound.dll Product: Wine-staging Version: 3.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lorenzofer(a)live.it CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Hi. Recently I wanted to play to some old games that were using DirectMusic. In particular "Imperivm Great Battles of Rome" So following the procedures I installed the directmusic component and the native dsound.dll However when I tried the game I was encountered by an hanged application. (the application opened it's window and rendered the cursor, but nothing else) I was on wine-staging as I have some games that require staging patches. However as I recalled this game worked before, so I tried vanilla wine. It worked almost flawless (encountering bug Bug 44540 with quartz.dll as native). Then I tried with older wine-staging version. I started with the wine-staging 3.3 that was the older one in my pacman package cache, and worked flawless. I then discovered that the first bad wine-staging release is the 3.13 release. After checking the patch modified between the 3.12 and 3.13 releases, I found that if I compile wine-staging from source without applying the winepulse-PulseAudio_Support the issue disappears. Unfortunatly Imperivm GBR doesn't have an aviable demo, but recently an udated version was released on steam, and you can ask for a key at FX Interactive for free. Check the FAQ in the Imperium World forum on Discord. Normal Log is totally unhelpful as the only thing it give is a: 0009:fixme:thread:create_user_shared_data_thread Creating user shared data update thread. Two others affected application are: Rise of Nation Rise of Nation Throne and Patriots Others bug associated with winepulse-PulseAudio_Support and 3.13 Release (potentially not duplicates): Bug 45582 - Bug 45623 - Bug 45502 -- 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 40060] New: Crash dialog button unclickable
by wine-bugs＠winehq.org 31 Mar '19

31 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=40060 Bug ID: 40060 Summary: Crash dialog button unclickable Product: Wine-staging Version: 1.9.2 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: isakov-sl(a)bk.ru CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Created attachment 53538 --> https://bugs.winehq.org/attachment.cgi?id=53538 The windows in question If a game crashes (for example elevated_1024x768.exe) then dialog windows appeared with two buttons "Show details" and "Close". These buttons are unclickable because of patch https://github.com/wine-compholio/wine-staging/blob/master/patches/user32-M… Reverting the patch resolves the issue. -- 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 45856] New: wine stuck installing python in silent mode
by wine-bugs＠winehq.org 31 Mar '19

31 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=45856 Bug ID: 45856 Summary: wine stuck installing python in silent mode Product: Wine-staging Version: 3.16 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: sbonazzo(a)redhat.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: Fedora On Fedora 28: download https://www.python.org/ftp/python/2.7.14/python-2.7.14.msi $ wine msiexec /i /tmp/python-2.7.14.msi /qn ADDLOCAL=ALL 000b:fixme:winediag:start_process Wine Staging 3.16 is a testing version containing experimental patches. 000b:fixme:winediag:start_process Please mention your exact version when filing bug reports on winehq.org. 0028:fixme:dwmapi:DwmIsCompositionEnabled 0x6dc825d4 002d:fixme:iphlpapi:NotifyIpInterfaceChange (family 0, callback 0x69ec7e28, context 0x91e480, init_notify 0, handle 0x11dfa10): stub 003f:fixme:dwmapi:DwmIsCompositionEnabled 0x6dc825d4 0041:fixme:iphlpapi:NotifyIpInterfaceChange (family 0, callback 0x69ec7e28, context 0x91e480, init_notify 0, handle 0x11dfa10): stub wine: configuration in '/home/sbonazzo/.wine' has been updated. 0009:fixme:ntdll:NtLockFile I/O completion on lock not implemented yet 0053:err:msiexec:custom_action_server Failed to create custom action server pipe: 2 wine get stuck here and doesn't complete the silent install. Reproducible 100% with wine 3.14-1.fc28 and 3.16-1.fc28 Worked fine in wine 3.8-1.fc28 (https://jenkins.ovirt.org/job/ovirt-guest-agent_master_build-artifacts-fc28…) -- 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 45578] New: GTA 5 doesn't launch in 3.13, works in 3.12
by wine-bugs＠winehq.org 31 Mar '19

31 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=45578 Bug ID: 45578 Summary: GTA 5 doesn't launch in 3.13, works in 3.12 Product: Wine-staging Version: 3.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: electrodexsnet(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 61994 --> https://bugs.winehq.org/attachment.cgi?id=61994 crash log - crash at line 19,541 I have GTA5 installed in a wine prefix with dxvk. Using wine builtin vulkan (vulkan-1.dll). In wine-staging 3.12, GTA 5 runs without issue. In 3.13, it now hangs at a blank screen after the police siren intro. You can close it by pressing Alt F4, then Enter. After reverting to 3.12, it works as expected again. Versions/System: GPU: Nvidia GTX 970 | proprietary driver: 396.45 OS: Manjaro stable DXVK: tested 0.54, 0.63, 0.64 - no difference winetricks: allfonts, steam Noteable error messages (line 19,541 in gta5_wine-staging-3.13-crash01): wine: Unhandled page fault on write access to 0x00000000 at address 0x141275cbc (thread 013c), starting debugger... Unhandled exception: page fault on write access to 0x00000000 in 64-bit code (0x0000000141275cbc). -- 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 4

[Bug 46148] New: In World of Warcraft 8 background and water are solid color and flashes of various color appear many times per second
by wine-bugs＠winehq.org 31 Mar '19

31 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=46148 Bug ID: 46148 Summary: In World of Warcraft 8 background and water are solid color and flashes of various color appear many times per second Product: Wine-staging Version: 3.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: kgrittn(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- World of Warcraft 8.0.1 (28153)(Release x64) OS is Ubuntu, both show the same symptoms and were fine before Wine 3.20 (Staging): Linux kevin-desktop 4.15.0-39-generic #42~16.04.1-Ubuntu SMP Wed Oct 24 17:09:54 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz 16GB Intel HD Graphics 4000 (Ivybridge) (on motherboard, no expansion slot) Linux kgrittn-Precision-7720 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Intel(R) Xeon(R) CPU E3-1505M v6 @ 3.00GHz 32GB RAM NVIDIA GeForce GTX 470 Symptoms in WoW: - Backgrounds such as terrain show as a single color (always black?) with no "litter" or detail -- a roadway looks the same as wild ground which is the same as the side of a cliff. - Water shows as a single block of color with no shorline features, reflection, or transparency to underlying features. - Random patches of color appear, apparently changing with each screen draw. - Small animated areas like torch flames show lots of rectangle enclosing the area with little or none of the normal animation. -- 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 30

[Bug 44032] New: Diablo 3 2.6.1: Mouse-downs register as mouse clicks
by wine-bugs＠winehq.org 31 Mar '19

31 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=44032 Bug ID: 44032 Summary: Diablo 3 2.6.1: Mouse-downs register as mouse clicks Product: Wine Version: 2.20 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: sts33nvyb(a)gmail.com Distribution: --- Created attachment 59696 --> https://bugs.winehq.org/attachment.cgi?id=59696 Terminal output (not that I expect this to be useful) In Diablo 3, mouse-downs (pressing and holding the mouse button) often register as mouse clicks (pressing and immediately releasing the mouse button). This happens for approximately 50% of the mouse-downs when playing the game, which dramatically changes how the game plays, since holding down the mouse button is used for both moving and attacking continuously in the game. I'm running wine-staging 2.20 on OpenSuse 42.3 x86_64. This is for the current version of Diablo 3, version 2.6.1.47919 32-bit. Note that Diablo 3 recently dropped support for Windows XP; since this change, Diablo 3 no longer works in non-staging wine at all. Also, the 64-bit version of Diablo 3 has severe performance problems in wine-staging 2.20, so this is using the 32-bit version of Diablo 3. I speculate that some bug in wine is causing bogus mouse-up events to sometimes be generated immediately after mouse-down events. Note that this is a completely different bug from bug 31262. Note that user "pakos" has mistakenly commented about this bug in that bug report, dated 2017-11-13. He reports that this problem is present in versions of wine-staging at least back to 2.5. There has been some discussion of this bug on the application page. Some users have reported that changing wine's virtual desktop setting, forcing 32-bit using setarch, or changing Diablo 3's settings to windowed-fullscreen instead of fullscreen alleviated the problem. None of these helped for me. -- 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 33

[Bug 45826] New: Doom 2016 - Rendering issues
by wine-bugs＠winehq.org 31 Mar '19

31 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=45826 Bug ID: 45826 Summary: Doom 2016 - Rendering issues Product: Wine-staging Version: 3.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ahmed.com(a)aol.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 62283 --> https://bugs.winehq.org/attachment.cgi?id=62283 wine error log I can't run Doom 2016 with Mesa 18.1.7 or Mesa 18.1.8, so I tried Mesa 18.2.0-1 and the game started but it look so weird, and I can hear the menu sounds but I can't see the menu. System information: Operating system: Manjaro KDE GPU: AMD HD 8750M Driver: Mesa 18.2.0-1 Wine version: 3.15 staging-nine -- 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 30

[Bug 46224] New: ddraw-Create-rendering-targets-in-video-memory patch got borked between 3.19 and 3.20
by wine-bugs＠winehq.org 31 Mar '19

31 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=46224 Bug ID: 46224 Summary: ddraw-Create-rendering-targets-in-video-memory patch got borked between 3.19 and 3.20 Product: Wine-staging Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: sashok.olen(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Testing application - The Sims Complete Collection With 3.19, the game launches just fine, and I get `0009:fixme:ddraw:ddraw_surface_create Application wants to create rendering target in system memory, using video memory instead` fixmes in the terminal output, and the game starts. In 3.20, the game aborts the launch, and I don't get the fixmes. I suspect this rebase might have broke it: https://github.com/wine-staging/wine-staging/commit/a423a7087ff2dad6f2def0c… -- 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 41107] New: Total Commander 8.52a Final has VERY slow folder icons rendering
by wine-bugs＠winehq.org 31 Mar '19

31 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=41107 Bug ID: 41107 Summary: Total Commander 8.52a Final has VERY slow folder icons rendering Product: Wine Version: 1.9.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: shell32 Assignee: wine-bugs(a)winehq.org Reporter: katsunori.kumatani(a)gmail.com Distribution: --- Created attachment 55313 --> https://bugs.winehq.org/attachment.cgi?id=55313 Terminal Output, not very useful Using the 32-bit version of Total Commander 8.52a Final (latest non-beta), when drawing/rendering the icons for folders, it is VERY slow. Download the 32-bit version here: http://totalcmd2.s3.amazonaws.com/tcmd852ax32.exe After installing and launching it, please do the following to reproduce: 1) Maximize the Window to have more folders on screen. 2) Near the top-left, to the right of the green "Refresh" button, click on the "Source: Only file names" button, this enables more folders visible at once to show the slow effect more. 3) Go/navigate to a folder which has around 200 folders, such as Z:\usr\share (depends on your Linux distro), it doesn't matter, just make sure it has a lot of folders to see how painfully slow it is. This problem of course is not present in Windows. Terminal output has been attached, however I don't think it has any useful information because [b]Total Commander version 7 exhibits almost the same terminal output, but IT IS NOT SLOW like 8.52a![/b] In fact it is almost instant when rendering folder icons, which look the exact same. If you turn off folder icons in Preferences, it is fast, so I know that they are the culprit, 100%. Btw, the version 9 beta does not seem to have this problem because it uses the system's folder icons (which are blue on my system) instead of internal. The internal ones are yellow. I hope you can track down and fix this bug with this information. -- 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 26

[Bug 45278] New: Vietcong: invisible objects (staging 3.9)
by wine-bugs＠winehq.org 31 Mar '19

31 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=45278 Bug ID: 45278 Summary: Vietcong: invisible objects (staging 3.9) Product: Wine-staging Version: 3.9 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: havran.jan(a)email.cz CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: ArchLinux Created attachment 61538 --> https://bugs.winehq.org/attachment.cgi?id=61538 Wine staging 3.9 rendering issues in Vietcong Wine-staging 3.9 has an issue with rendering objects in Vietcong - some parts of soldier models are invisible (see attachment). This problem does not exist in Wine-testing and all other Wine-staging versions (so its only Wine-staging 3.9 issue). Reproducible in Vietcong full [1] and demo [2] versions. See notes in AppDB how to run the game. Tested SW Kernel 4.16.11 Mesa 18.0.4 Tested HW Processor: Intel(R) Core(TM) i5-4210M CPU @ 2.60GHz GPU 1: Intel HD Graphics 4600 GPU 2: AMD Radeon R7 M265 PS: Different Vietcong rendering bug occured also in Wine-staging 3.3, but it has been fixed: bug #44712 PPS: Also note that some missions will crash without stagged "wined3d-Indexed_Vertex_Blending" patch, see bug #39057 or #9337 [1] https://appdb.winehq.org/objectManager.php?sClass=version&iId=8864 [2] https://appdb.winehq.org/objectManager.php?sClass=version&iId=35621 -- 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 16