April 2019 - Wine-Bugs - list.winehq.org

[Bug 46954] New: Relay trace causes crash in wine_dbgstr_wn helper due to invalid string pointer access
by wine-bugs＠winehq.org April 12, 2019

April 12, 2019

https://bugs.winehq.org/show_bug.cgi?id=46954 Bug ID: 46954 Summary: Relay trace causes crash in wine_dbgstr_wn helper due to invalid string pointer access Product: Wine Version: 4.5 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, found while checking a patch for bug 46903 Relay tracing crashes the app: --- snip --- $ WINEDEBUG=+seh,+loaddll,+relay,+ntdll wine ./ADHOCSIGNER.EXE ./TouchInputPC.exe >>log.txt 2>&1 ... 00ac:Call user32.SetPropA(00060044,7cd7c748 "__wine_x11_whole_window",05400001) ret=7cd53e2e ... 00ac:Ret user32.SetPropA() retval=00000001 ret=7cd53e2e .... 00ac:Call user32.EnumPropsW(00060044,004018cb) ret=00401b3e ... 00ac:Call KERNEL32.GlobalGetAtomNameW(0000c06a,0033f91c,00000100) ret=7e7a26a7 00ac:Call ntdll.NtQueryInformationAtom(0000c06a,00000000,0033f67e,00000206,00000000) ret=7b42fe3f 00ac:Ret ntdll.NtQueryInformationAtom() retval=00000000 ret=7b42fe3f 00ac:Ret KERNEL32.GlobalGetAtomNameW() retval=00000017 ret=7e7a26a7 00ac:Call user32.RemovePropW(00060044,0033f91c L"__wine_x11_whole_window") ret=004018e5 00ac:Ret user32.RemovePropW() retval=05400001 ret=004018e5 00ac:Call oleaut32.SysFreeString(code=c0000005 flags=0 addr=0x7bc7c011 ip=7bc7c011 tid=00ac 00ac:trace:seh:raise_exception info[0]=00000000 00ac:trace:seh:raise_exception info[1]=05400001 00ac:trace:seh:raise_exception eax=7bd0d000 ebx=7bd0d000 ecx=00000000 edx=05400001 esi=0033f880 edi=0033fb88 00ac:trace:seh:raise_exception ebp=0033f778 esp=0033f630 cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00010202 00ac:trace:seh:call_stack_handlers calling handler at 0x7b4980f1 code=c0000005 flags=0 ... wine: Unhandled page fault on read access to 0x05400001 at address 0x7bc7c011 (thread 00ac), starting debugger... ... Unhandled exception: page fault on read access to 0x05400001 in 32-bit code (0x7bc7c011). Register dump: CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b EIP:7bc7c011 ESP:0033f630 EBP:0033f778 EFLAGS:00010202( R- -- I - - - ) EAX:7bd0d000 EBX:7bd0d000 ECX:00000000 EDX:05400001 ESI:0033f880 EDI:0033fb88 Stack dump: 0x0033f630: 00000000 00000000 0033f6fc f7d9c2e2 0x0033f640: f7d88680 00000000 00000000 7bc42361 0x0033f650: 7bd0d000 ffffffff 0033f888 7bc42b08 0x0033f660: 7bd18922 0033f6c8 00000017 7bc42a86 0x0033f670: 0033f91c 00000017 7bd18600 0000031a 0x0033f680: f7d88680 00000000 0033f6a8 0033f6b0 Backtrace: =>0 0x7bc7c011 wine_dbgstr_wn+0x74() [/home/focht/projects/wine/mainline-src/include/wine/debug.h:277] in ntdll (0x0033f778) 1 0x7bc7c2b3 debugstr_w+0x1c() [/home/focht/projects/wine/mainline-src/include/wine/debug.h:515] in ntdll (0x0033f798) 2 0x7bc7cc57 trace_string_w+0x4e() [/home/focht/projects/wine/mainline-src/dlls/ntdll/relay.c:321] in ntdll (0x0033f7c8) 3 0x7bc7cf02 relay_trace_entry+0x237() [/home/focht/projects/wine/mainline-src/dlls/ntdll/relay.c:357] in ntdll (0x0033f868) 4 0x7bc7d2eb relay_call+0x16() in ntdll (0x0033f8a0) 5 0x7d6d6276 __wine_stub_OleLoadPictureFileEx+0xed() in oleaut32 (0x0033f8b8) 6 0x004018fe EntryPoint+0xffffffff() in adhocsigner (0x0033f8b8) 7 0x7e7a205a EnumPropsW_relay+0x32() [/home/focht/projects/wine/mainline-src/dlls/user32/property.c:92] in user32 (0x0033f8e8) 8 0x7e7a26d4 EnumPropsExW+0xa2() [/home/focht/projects/wine/mainline-src/dlls/user32/property.c:248] in user32 (0x0033fb38) 9 0x7e7a20da EnumPropsW+0x31() [/home/focht/projects/wine/mainline-src/dlls/user32/property.c:110] in user32 (0x0033fb68) --- snip --- The app provided callback for user32.EnumPropsW() tries to remove Wine internal window properties. User32.RemovePropW() returns 0x05400001 which in turn gets passed to oleaut32.SysFreeString(). This should obviously fail due to invalid parameter. Unfortunately the relay debug print functionality no longer catches invalid string pointer access. Quick inspection of Wine changes hint at this: https://source.winehq.org/git/wine.git/commitdiff/9f75f7189935aeec55df79a5a… ("include: Make wine_dbgstr_an()/wine_dbgstr_wn() into inline functions.") _NTSYSTEM_ is always defined for ntdll (relay) which leaves the pointer test/access without SEH protection. https://source.winehq.org/git/wine.git/blob/HEAD:/include/wine/debug.h#l267 $ wine --version wine-4.5-138-g8268c47462 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.

1 4

[Bug 42572] New: Revenant has some graphical issues with official Nvidia drivers & hardware
by wine-bugs＠winehq.org April 12, 2019

April 12, 2019

https://bugs.winehq.org/show_bug.cgi?id=42572 Bug ID: 42572 Summary: Revenant has some graphical issues with official Nvidia drivers & hardware Product: Wine Version: 2.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fjfrackiewicz(a)gmail.com Distribution: --- Created attachment 57483 --> https://bugs.winehq.org/attachment.cgi?id=57483 Screenshot to show the graphics issues in the game In Wine-2.2-276-ge6f8f136fa Revenant no longer crashes at start but it still has some graphics issues. 1. The player character's model is completely black as are other characters in the game. 2. Some characters instead of being completely black are displayed with a "ghostly" white color. 3. Lastly, the player's paper doll (see the flesh colored model on the right side in the screenshot) is animated but the graphics for the frames of the paper doll are not cleared so you have this sort of "hall of mirrors" effect. Hopefully the attached screenshot will illustrate what I mean. My hardware and driver info: Nvidia 970 GTX Driver version 378.13 -- 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 27

[Bug 34237] New: Jenkins fails to install (dogfood)
by wine-bugs＠winehq.org April 12, 2019

April 12, 2019

http://bugs.winehq.org/show_bug.cgi?id=34237 Bug #: 34237 Summary: Jenkins fails to install (dogfood) Product: Wine Version: 1.7.0 Platform: x86 URL: http://jenkins-ci.org/ OS/Version: Linux Status: NEW Keywords: download, Installer, source Severity: normal Priority: P2 Component: programs AssignedTo: wine-bugs(a)winehq.org ReportedBy: austinenglish(a)gmail.com Classification: Unclassified Looks like its service related: err:service:service_send_start_message service L"Jenkins" failed to start err:msi:ITERATE_StartService Failed to start service L"Jenkins" (1053) err:msi:ITERATE_Actions Execution halted, action L"StartServices" returned 1627 err:msi:ITERATE_Actions Execution halted, action L"ExecuteAction" returned 1627 I'll attach a log. austin(a)aw25 ~ $ wine --version wine-1.7.0 austin(a)aw25 ~ $ sha1sum jenkins-1.526.zip 1658d7cba2cd1bdc5ac521a806957df7ef0610ea jenkins-1.526.zip austin(a)aw25 ~ $ du -h jenkins-1.526.zip 84M jenkins-1.526.zip -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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 40544] New: Ultimate Unwrap Pro v3.50.14 x64 demo: Fails to run
by wine-bugs＠winehq.org April 12, 2019

April 12, 2019

https://bugs.winehq.org/show_bug.cgi?id=40544 Bug ID: 40544 Summary: Ultimate Unwrap Pro v3.50.14 x64 demo: Fails to run Product: Wine Version: 1.9.8 Hardware: x86-64 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: rajveer_aujla(a)hotmail.com Fails to run the x64 version of the application on OSX (using the new experimental x64 support found in 1.9.8 devel), producing the following: err:module:attach_process_dlls "uulib_64.dll" failed to initialize, aborting err:module:LdrInitializeThunk Main exe initialization for L"C:\\Program Files\\Ultimate Unwrap3D Pro (x64)\\unwrap3d_64.exe" failed, status c0000005 I believe uulib_64.dll is a dll specific to the application. Download link (unfortunately I cannot get an exact link): http://www.unwrap3d.com/u3d/downloads.aspx -- 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 8

[Bug 46829] New: Wizard101 crashes after playing the game after awhile.
by wine-bugs＠winehq.org April 12, 2019

April 12, 2019

https://bugs.winehq.org/show_bug.cgi?id=46829 Bug ID: 46829 Summary: Wizard101 crashes after playing the game after awhile. Product: Wine Version: 4.3 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jamesgryffindor99(a)gmail.com Created attachment 63859 --> https://bugs.winehq.org/attachment.cgi?id=63859 Wizard101 crash logs for Wine 4.3 on macOS Mojave. After playing Wizard101 (anywhere from 30 minutes to an hour or more), it crashes unexpectedly. I have attached the terminal log below. This is a clean install of wine 4.3 on macOS Mojave 10.14.3. -- 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

[Bug 27629] New: Pride of Nations Demo:
by wine-bugs＠winehq.org April 12, 2019

April 12, 2019

http://bugs.winehq.org/show_bug.cgi?id=27629 Summary: Pride of Nations Demo: Product: Wine Version: 1.3.23 Platform: x86 URL: http://www.gamershell.com/download_74618.shtml OS/Version: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: austinenglish(a)gmail.com Potentially workaround 27628 (winetricks -q d3dx9_36, or don't remove the native dll). Start the app, choose new game, choose the only campaign option. Choose any country (tried UK and Russia). The game will either immediately exit, or maybe pop up a map and an error dialog. Nothing shows in the terminal. Looking at the game's log, I see: 7:08:56 PM [Critical ] TParticlesDef.Fetch Data container for particles definitions has some discrepancies, for UID 1 7:08:56 PM [Critical ] TParticlesDef.Fetch Data container for particles definitions has some discrepancies, for UID 1 -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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 18

[Bug 46979] New: Winecfg hangs (winedevice.exe 100% CPU usage) when removing an assigned drive
by wine-bugs＠winehq.org April 12, 2019

April 12, 2019

https://bugs.winehq.org/show_bug.cgi?id=46979 Bug ID: 46979 Summary: Winecfg hangs (winedevice.exe 100% CPU usage) when removing an assigned drive Product: Wine Version: 4.5 Hardware: x86 OS: Linux Status: NEW Keywords: download, regression, source Severity: normal Priority: P2 Component: wineserver Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com CC: jacek(a)codeweavers.com Regression SHA1: b4f78d6896a7fc85b3ec29d3db30d5d8e9b790e8 Distribution: ArchLinux Steps to reproduce: 1. create a new wineprefix by running winecfg. Go to the <Drives> tab and add a new drive pointing to any existing directory on your filesystem e.g. your home directory. Click <Apply> then <OK> to accept the changes and quit winecfg. 2. re-run winecfg, visit the <Drives> tab and remove the previously created drive from the list then click <Apply>....winecfg hangs (no visible terminal output, winedevice consumes 100% CPU). Another scenario (an external USB hard drive was mounted then unmounted between those 2 steps). When the external hdd is mounted on my system, existing partitions on the drive are automatically added to the drive list in winecfg. Exit winecfg and unmount the partition(s) from your system then re-run winecfg and try to open the <Drives> tab: Wine hangs again, now something like this is present in the terminal: 0017:err:ntdll:RtlpWaitForCriticalSection section 0xf7d67700 "../../../dlls/mountmgr.sys/device.c: device_section" wait timed out in thread 0017, blocked by 0019, retrying (60 sec) Reverting commit b4f78d6896a7fc85b3ec29d3db30d5d8e9b790e8 fixes the problem for me. Tested and reproduced in wine-4.5-222-g8ee1e3453e. -- 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 2

[Bug 45854] New: Magic the Gathering demo graphical glitch with virtual desktop
by wine-bugs＠winehq.org April 12, 2019

April 12, 2019

https://bugs.winehq.org/show_bug.cgi?id=45854 Bug ID: 45854 Summary: Magic the Gathering demo graphical glitch with virtual desktop Product: Wine Version: 3.16 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: spzakulec(a)gmail.com Distribution: --- Created attachment 62340 --> https://bugs.winehq.org/attachment.cgi?id=62340 Console output when running the Magic the Gathering demo with a virtual desktop Hi, the Magic the Gathering demo (the one by Microprose) works fine in a 32 bit wine prefix on 3.16 devel with OS set to Win 95, but key parts of the interface disappear or are solid black if the program is run in a virtual desktop. While I am not totally sure this is the same issue that affects all of the Microprose Magic the Gathering games, in practice the issue and the symptoms are identical. You can download the demo here: https://archive.org/details/mtgdemo I'm on Kubuntu 17.10 64 bit, using the official WineHQ repository. To reproduce this: Run mtgdemo.exe, which extracts to a folder. In the extracted folder, run DUEL.EXE in a 32 bit wine prefix with OS set to Win95. You'll see a screen without any black boxes or blobs on it- most importantly, the large Magic card on the left is visible. Click exit. Set DUEL.EXE to a virtual desktop- 1024x768 shows this issue. The card that was visible without the virtual desktop is now a giant black blob. Should you try to play the game, other graphical glitches will happen- cards disappear and only re-appear when you go to the next turn or right-click on the playing field, choose Duel Options, and then press OK. -- 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 3

[Bug 45325] New: Ubisoft detection tool dont recognize correctly cpu
by wine-bugs＠winehq.org April 12, 2019

April 12, 2019

https://bugs.winehq.org/show_bug.cgi?id=45325 Bug ID: 45325 Summary: Ubisoft detection tool dont recognize correctly cpu Product: Wine Version: 3.10 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mrdeathjr28(a)yahoo.es Distribution: --- Detection tool app used by various ubisoft titles case: assasins creed 1, prince of persia forgotten sands, prince of persia 2008 dont detect real name cpu and only shows intel pentium 4 2.40ghz However in side shows correct cpu cores and non overclocked frecuency Overclocked frecuency dont detected Also occur in batman arkham asylum installer too Thanks -- 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 20082] New: Driver Create and Close displatch routines should be called
by wine-bugs＠winehq.org April 12, 2019

April 12, 2019

http://bugs.winehq.org/show_bug.cgi?id=20082 Summary: Driver Create and Close displatch routines should be called Product: Wine Version: 1.1.29 Platform: PC URL: http://rh-software.com/ OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: ntoskrnl AssignedTo: wine-bugs(a)winehq.org ReportedBy: ray(a)pobox.co.uk Currently when a CreateFile() is done the IRP_MJ_CREATE dispatch routine is not called ! This is a major oversight and caused the v4.00 SIVDRIVER to crash. For 4.01 I worked around this, but failing to call the driver when the CreateFile() is done is a major failing and needs to be corrected. The IRP_MJ_CLOSE routine also needs to get called for the CloseHandle(). -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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 10