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

[Bug 22992] New: SVN-Monitor needs gdiplus.dll.GdipGetRenderingOrigin
by wine-bugs＠winehq.org Jan. 8, 2022

Jan. 8, 2022

http://bugs.winehq.org/show_bug.cgi?id=22992 Summary: SVN-Monitor needs gdiplus.dll.GdipGetRenderingOrigin Product: Wine Version: 1.2-rc2 Platform: x86 URL: http://www.svnmonitor.com/ OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdiplus AssignedTo: wine-bugs(a)winehq.org ReportedBy: focht(a)gmx.net Hello, SVN Monitor doesn't run well with builtin gdiplus. Although it doesn't crash, a nasty error dialog is displayed each time the exception is thrown (can be dismissed). --- snip --- ... fixme:gdiplus:GdipDrawImagePointsRect Image wrap mode not implemented fixme:gdiplus:GdipGetRegionScansCount not implemented ... fixme:shell:URL_ParseUrl failed to parse L"SVNMonitor.resources" wine: Call from 0x7b836c0f to unimplemented function gdiplus.dll.GdipGetRenderingOrigin, aborting --- snip --- Install recipe (see also appdb entry): --- snip --- $ sh winetricks -q dotnet20 TortoiseSVN is also needed (http://tortoisesvn.net/downloads/) Install the MSI package: $ wine start TortoiseSVN-xxx-win32-svn-xxx.msi Now run the SVN Monitor application installer. $ wine SVNMonitor-xxx-Setup.exe --- snip --- Regards -- 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.

2 6

[Bug 52090] New: New failures in d3d11:d3d11 in Wine
by WineHQ Bugzilla Jan. 8, 2022

Jan. 8, 2022

https://bugs.winehq.org/show_bug.cgi?id=52090 Bug ID: 52090 Summary: New failures in d3d11:d3d11 in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- Running d3d11:d3d11 on the TestBot debiant2 VM used to consistently produce 70 failures. But on 2021-11-04 the failure mix changed and the count increased to a steady 77 failures. The new failures happen in void test_fractional_viewports() and test_negative_viewports(). In typical unified diff style: -d3d11.c:5926: Test failed: Got unexpected CPrimitives count: 3. -d3d11.c:5943: Test failed: Got unexpected CPrimitives count: 3. +d3d11.c:28242: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. +d3d11.c:28242: Test succeeded inside todo block: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. +d3d11.c:28251: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. +d3d11.c:28251: Test succeeded inside todo block: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. +d3d11.c:28188: Test failed: Got texcoord {8.43750119e-001, 1.56249881e-001}, expected {8.43750000e-001, 1.56250000e-001} at (3, 3), offset 1.25000000e-001. +d3d11.c:28242: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. +d3d11.c:28188: Test failed: Got texcoord {8.71093690e-001, 1.28906310e-001}, expected {8.71093750e-001, 1.28906250e-001} at (3, 3), offset 1.56250000e-002. +d3d11.c:28251: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. +d3d11.c:28188: Test failed: Got texcoord {7.51953065e-001, 2.48046935e-001}, expected {7.51953125e-001, 2.48046875e-001} at (3, 3), offset 4.92187500e-001. https://test.winehq.org/data/patterns.html#d3d11:d3d11 A bisect shows that the new failures started with the commit below: commit 26a53f674c234aaba4a85ec36bae48384899b705 Author: Stefan Dösinger <stefan(a)codeweavers.com> Date: Wed Nov 3 20:15:30 2021 +0300 wined3d: Emulate fractional viewports if GL doesn't support them. This allows test_fractional_viewports to pass regardless of GL capabilies. I don't think we can get rid of WINED3D_PIXEL_CENTER_INTEGER (and add +0.5 in the client libs) due to vpos in d3d9 shaders. Signed-off-by: Stefan Dösinger <stefan(a)codeweavers.com> Signed-off-by: Henri Verbeet <hverbeet(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> -- 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 5

[Bug 51703] New: Opening Omnisphere Authorization window with a large amount of text on the clipboard causes an unhandled page fault
by WineHQ Bugzilla Jan. 7, 2022

Jan. 7, 2022

https://bugs.winehq.org/show_bug.cgi?id=51703 Bug ID: 51703 Summary: Opening Omnisphere Authorization window with a large amount of text on the clipboard causes an unhandled page fault Product: Wine-staging Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: andrew(a)amorgan.xyz CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 70576 --> https://bugs.winehq.org/attachment.cgi?id=70576 backtrace I'm attempting to register my Spectatronics Omnisphere installation, which requires pasting an authorization code into the application. However, it appears that during authorization Omnisphere will attempt to read the contents of the clipboard in order to validate the authorization code, but upon doing so with any clipboard size that is significantly large, the application will crash with a page fault. Unfortunately, I cannot work around this issue as there is no option to type in the authorization code rather than pasting it in in full. Running the application with a small amount of text on the clipboard works fine. I also found that simply having 500 letter 'A's on my clipboard ('AAAAA...') will also cause the application to crash, so it appears that the characters involved does not matter - only the size of the clipboard's content does. Through trial and error I have found that a string of 110 A's is fine, but 111 A's on the clipboard will cause the application to crash. -- 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 13

[Bug 45896] New: Dungeon Keeper 2 - Patch'ed v1.8 - doesn't start
by wine-bugs＠winehq.org Jan. 7, 2022

Jan. 7, 2022

https://bugs.winehq.org/show_bug.cgi?id=45896 Bug ID: 45896 Summary: Dungeon Keeper 2 - Patch'ed v1.8 - doesn't start Product: Wine Version: 3.0.3 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: thomas000bauer(a)gmail.com Distribution: --- Hi, i have tried to launch Dungeon Keeper 2 with the "unofficial" Patch to Version v1.8 so the necessity of a noCD Crack is obsolete. When i try to execute the "wine" command it takes about 4-5seconds with/and without attached debug-log export to get me a new command line. But nothing else happens, no Output in the Terminal no nothing. I do as followed to launch Dungeon Keeper 2: [code] export WINEPREFIX="/media/daten350/games-software/wine/dungeon.keeper.2" export WINEDEBUG=+timestamp,+tid,+loaddll,+winediag,+synchronous,+seh,+x11drv,+xrandr cd /media/daten350/games-software/wine/dungeon.keeper.2/drive_c/Program\ Files\ $x86$/Bullfrog/Dungeon\ Keeper\ 2/ wine Dkii.exe &>~/wine-vanilla-3.0.2_loaddl_wgl_log.txt [/code] here the Log is on Git [url]https://gist.github.com/Phenicien/16b7fb1230df0e1becc0845351e80cdb[/url] as well as i have attached it as a .zip file. I already created a Form Thread [url]https://forum.winehq.org/viewtopic.php?f=2&t=31165&sid=b68c344b875b8472…] I'm grateful for every help or solution. 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.

2 9

[Bug 40733] New: page fault on read access to 0x00000004 in 32-bit code ( 0x007091ad).
by wine-bugs＠winehq.org Jan. 7, 2022

Jan. 7, 2022

https://bugs.winehq.org/show_bug.cgi?id=40733 Bug ID: 40733 Summary: page fault on read access to 0x00000004 in 32-bit code (0x007091ad). Product: Wine Version: 1.6.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: martin.suc(a)googlemail.com Distribution: --- Created attachment 54639 --> https://bugs.winehq.org/attachment.cgi?id=54639 backtrace of the inkscape Crash of the inkscape application: Unhandled exception: page fault on read access to 0x00000004 in 32-bit code (0x007091ad). System information: Wine build: wine-1.6.2 Platform: i386 (WOW64) Host system: Linux Host version: 4.4.0-23-generic -- 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 50527] New: Dying Light shows a black screen after starting a new game
by WineHQ Bugzilla Jan. 7, 2022

Jan. 7, 2022

https://bugs.winehq.org/show_bug.cgi?id=50527 Bug ID: 50527 Summary: Dying Light shows a black screen after starting a new game Product: Wine Version: 5.22 Hardware: x86-64 OS: Linux Status: NEW Keywords: regression Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com CC: hverbeet(a)gmail.com Regression SHA1: 8b3cc57df0b791ca6c33f383f9358e1613206b84 Distribution: --- Reverting the commit helps. -- 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 52311] New: Starting executables from removable devices no longer works with Wine 7.0-rc3-7-g3e73437ae8f
by WineHQ Bugzilla Jan. 7, 2022

Jan. 7, 2022

https://bugs.winehq.org/show_bug.cgi?id=52311 Bug ID: 52311 Summary: Starting executables from removable devices no longer works with Wine 7.0-rc3-7-g3e73437ae8f Product: Wine Version: 7.0-rc3 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: wineserver Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, just found by chance while checking some old bug reports. Mount media/ISO image as usual and change to the directory where the executable resides (= becomes working directory). Starting executable with 'wine ./setup.exe' results in: --- snip --- wine: failed to open "./setup.exe": c0000135 --- snip --- --- snip --- $ WINEDEBUG=+module,+server wine ./setup.exe >> ~/Downloads/log.txt 2>&1 ... 0024:trace:module:get_load_order looking for L"C:\\setup.exe" 0024: get_key_value( hkey=0004, name=L"C:\\setup.exe" ) 0024: get_key_value() = OBJECT_NAME_NOT_FOUND { type=-1, total=0, data={} } 0024: get_key_value( hkey=0004, name=L"*setup.exe" ) 0024: get_key_value() = OBJECT_NAME_NOT_FOUND { type=-1, total=0, data={} } 0024: get_key_value( hkey=0004, name=L"setup.exe" ) 0024: get_key_value() = OBJECT_NAME_NOT_FOUND { type=-1, total=0, data={} } 0024:trace:module:get_load_order got main exe default n,b for L"C:\\setup.exe" wine: failed to open "./setup.exe": c0000135 0024: terminate_process( handle=ffffffff, exit_code=-1073741515 ) 0024: terminate_process() = 0 { self=1 } --- snip --- It worked with Wine 7.0-rc3 but with today's git it no longer does. I suspect https://source.winehq.org/git/wine.git/commitdiff/3e73437ae8f04a12200bf5377… ("ntdll: Preserve the startup Unix directory unless it's on a removable device.") being the culprit. --- snip --- $ findmnt /run/media/focht/acad TARGET SOURCE FSTYPE OPTIONS /run/media/focht/acad /dev/sr1 iso9660 ro,nosuid,nodev,relatime,nojoliet,check=s,map=n,blocksize=2048,uid=1000,gid=1000,dmode=500,fmode=400 $ pwd /run/media/focht/acad $ ll total 105 -r-xr-xr-x. 1 focht focht 306 Feb 12 2007 acadcd.mid -r-xr-xr-x. 1 focht focht 43 Feb 22 2002 autorun.inf dr-xr-xr-x. 80 focht focht 10240 Feb 12 2007 rr_moved -r-xr-xr-x. 1 focht focht 87656 Feb 12 2007 setup.exe dr-xr-xr-x. 11 focht focht 4096 Feb 12 2007 x64 dr-xr-xr-x. 11 focht focht 4096 Feb 12 2007 x86 --- snip --- --- snip --- $ ll ~/.wine/dosdevices/ lrwxrwxrwx. 1 focht focht 10 Dec 31 14:05 c: -> ../drive_c lrwxrwxrwx. 1 focht focht 10 Dec 31 14:07 com1 -> /dev/ttyS0 ... lrwxrwxrwx. 1 focht focht 10 Dec 31 14:07 com9 -> /dev/ttyS8 lrwxrwxrwx. 1 focht focht 8 Dec 31 14:05 d:: -> /dev/sr0 lrwxrwxrwx. 1 focht focht 21 Dec 31 14:05 e: -> /run/media/focht/acad lrwxrwxrwx. 1 focht focht 8 Dec 31 14:05 e:: -> /dev/sr1 lrwxrwxrwx. 1 focht focht 8 Dec 31 14:07 lpt1 -> /dev/lp0 lrwxrwxrwx. 1 focht focht 8 Dec 31 14:07 lpt2 -> /dev/lp1 lrwxrwxrwx. 1 focht focht 8 Dec 31 14:07 lpt3 -> /dev/lp2 lrwxrwxrwx. 1 focht focht 8 Dec 31 14:07 lpt4 -> /dev/lp3 lrwxrwxrwx. 1 focht focht 1 Dec 31 14:05 z: -> / --- snip --- This works: --- snip --- $ wine "e:\\setup.exe" ... --- snip --- $ wine --version wine-7.0-rc3-34-gb6dc8399087 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 5

[Bug 52292] New: Cygwin compilation fails in ld: undefined reference to `__main' @ include/wine/test.h
by WineHQ Bugzilla Jan. 7, 2022

Jan. 7, 2022

https://bugs.winehq.org/show_bug.cgi?id=52292 Bug ID: 52292 Summary: Cygwin compilation fails in ld: undefined reference to `__main' @ include/wine/test.h Product: Wine Version: 7.0-rc3 Hardware: x86-64 OS: other Status: UNCONFIRMED Severity: blocker Priority: P2 Component: activeds Assignee: wine-bugs(a)winehq.org Reporter: saulius2(a)gmail.com (This is continuation from the bug 52287) make fails during following `winegcc` step: --- snip --- tools/winegcc/winegcc.exe -o dlls/activeds/tests/activeds_test.exe --wine-objdir . -Wl,--disable-stdcall-fixup \ -fasynchronous-unwind-tables -mno-cygwin dlls/activeds/tests/activeds.o \ dlls/activeds/tests/testlist.o dlls/ole32/libole32.a dlls/oleaut32/liboleaut32.a \ dlls/activeds/libactiveds.a dlls/winecrt0/libwinecrt0.a dlls/msvcrt/libmsvcrt.a \ dlls/kernel32/libkernel32.a dlls/ntdll/libntdll.a /usr/lib/gcc/i686-pc-cygwin/10/../../../../i686-pc-cygwin/bin/ld: dlls/activeds/tests/testlist.o: in function `main': /home/saukrs/src/wine/include/wine/test.h:669: undefined reference to `__main' collect2: error: ld returned 1 exit status winegcc: /usr/bin/gcc.exe failed make: *** [Makefile:2000: dlls/activeds/tests/activeds_test.exe] Error 2 --- snip --- -- 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 9

[Bug 52157] New: ntdll:wow64 fails on 64-bit Wine
by WineHQ Bugzilla Jan. 7, 2022

Jan. 7, 2022

https://bugs.winehq.org/show_bug.cgi?id=52157 Bug ID: 52157 Summary: ntdll:wow64 fails on 64-bit Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- ntdll:wow64 fails on 64-bit Wine: wow64.c:329: Test failed: debugging failed wow64.c:332: Test failed: BeingDebugged is 0 wow64.c:337: Test failed: BeingDebugged is 0 https://test.winehq.org/data/patterns.html#ntdll:wow64 The timeout only happens on WoW64 wineprefixes but impacts both real machines (cw-gtx560, cw-rx460) and VMs (notably the TestBot's debiant2 VM). A bisect shows that this started with the commit below: commit a041075cd2c26874757e0b6e1449c23c1326241c Author: Alexandre Julliard <julliard(a)winehq.org> Date: Thu Dec 2 09:59:49 2021 +0100 makefiles: Support per-platform values for EXTRADLLFLAGS. Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> However the current thought is that the commit only revealed a preexisting bug by changing the ntdll base address. -- 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 52144] New: Ketarin stops refreshing program window on Wine 6.22
by WineHQ Bugzilla Jan. 7, 2022

Jan. 7, 2022

https://bugs.winehq.org/show_bug.cgi?id=52144 Bug ID: 52144 Summary: Ketarin stops refreshing program window on Wine 6.22 Product: Wine Version: 6.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jim_henderson(a)sil.org Distribution: --- Running Ketarin 1.8.11.0 on Wine 6.22 on Lubuntu 20.04.3 LTS (64-bit) Shows error messages as in attached file. When I run the program it looks for updates to many software installers and successfully downloads any updated ones, but then gets to a state where the program fails to refresh the screen after a move or resize or xrefresh. The Control menu (program icon at top-left corner) still works, however, and I can use it to move the window to a different desktop or iconify or maximise the window. Window borders appear and change size properly, but no window contents are drawn. The initial error messages when I run the program are attached to bug #52143. The latest part of the error messages when this happens are shown in the attachment to bug #52142. Hoping someone can help 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 4