wine-bugs January 2022

wine-bugs@winehq.org

1 participants
4295 discussions

[Bug 22992] New: SVN-Monitor needs gdiplus.dll.GdipGetRenderingOrigin
by wine-bugs＠winehq.org 08 Jan '22

08 Jan '22

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 08 Jan '22

08 Jan '22

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 52366] New: Vortex Mod Manager - Chromium-based Window UI Doesn't Maximize Correctly
by WineHQ Bugzilla 08 Jan '22

08 Jan '22

https://bugs.winehq.org/show_bug.cgi?id=52366 Bug ID: 52366 Summary: Vortex Mod Manager - Chromium-based Window UI Doesn't Maximize Correctly Product: Wine Version: 7.0-rc5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: nekoNexus(a)protonmail.ch Distribution: --- Created attachment 71557 --> https://bugs.winehq.org/attachment.cgi?id=71557 Wine 7.0-rc5 Log(s) and Screenshots SHA256 of installer executable: ee6a45b1a4f88e1c5905b3dc9b25578a520279ff8d8be14b1f56b041388fcd6a Download location: https://web.archive.org/web/20220107223737/https://github.com/Nexus-Mods/Vo… ----- After installing and running Vortex, attempting to maximize the window causes the window to maximize incorrectly (vertically) and also some pixels off of the right side of the screen; additionally, though not clear if it's due to this issue, mouse targeting registration of UI elements misbehaves in a way where not hovering directly over elements is still perceived as hovering directly over it - though this doesn't quite mean that clicking actually performs the action(?), just that it seems to incorrectly report as being able to do so. That said, these are both issues I've noticed in other electron-based applications before <a href=https://appdb.winehq.org/objectManager.php?sClass=application&iId=8620>such as the Twitch desktop client</a> and <a href=https://github.com/z-edit/zedit>zEdit</a> (a W.I.P. modding tool for Bethesda games). -- 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 52363] New: Rhythm Doctor does not load
by WineHQ Bugzilla 08 Jan '22

08 Jan '22

https://bugs.winehq.org/show_bug.cgi?id=52363 Bug ID: 52363 Summary: Rhythm Doctor does not load Product: Wine Version: unspecified Hardware: Other OS: Mac OS X Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: minjae.lee137(a)gmail.com Created attachment 71551 --> https://bugs.winehq.org/attachment.cgi?id=71551 The text shown after bug Wine doesn't load the game fully -- 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 1

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

08 Jan '22

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 08 Jan '22

08 Jan '22

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 52364] New: Mouse sticks (doesn't release without an extra click) after resizing or moving the battle.net client window
by WineHQ Bugzilla 08 Jan '22

08 Jan '22

https://bugs.winehq.org/show_bug.cgi?id=52364 Bug ID: 52364 Summary: Mouse sticks (doesn't release without an extra click) after resizing or moving the battle.net client window Product: Wine Version: 7.0-rc4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lexlexlex(a)gmail.com Distribution: --- Steps to reproduce: 1. Install the Battle.net client from Blizzard. 2. Run the Battle.net client, such that its window becomes visible on-screen. If this is not working, please troubleshoot it until it works, since it is working here on Manjaro XFCE with wine 7.0-rc4. 3. Move or resize the Battle.net client window by holding the left mouse button and dragging the mouse anywhere. 4. Release the mouse button that was used to move or resize the Battle.net client window. 5. Move the mouse cursor elsewhere on the screen. 6. Fully click (mouse-down and mouse-up) the left mouse button again. 7. Move the mouse cursor elsewhere on the screen. Observed behavior: During step 5 of the steps to reproduce, the Battle.net client window moved or was resized according to changes in the position of the mouse cursor. Only during step 7 did that no longer happen. Expected behavior: During step 5 of the steps to reproduce, the Battle.net client window is expected to no longer move or be resized according to changes in the position of the mouse cursor. -- 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 27269] New: Bitcoin display ugly
by wine-bugs＠winehq.org 08 Jan '22

08 Jan '22

http://bugs.winehq.org/show_bug.cgi?id=27269 Summary: Bitcoin display ugly Product: Wine Version: 1.3.20 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: fracting(a)gmail.com Created an attachment (id=34876) --> (http://bugs.winehq.org/attachment.cgi?id=34876) Screenshot : bitcoin 1. download bitcoin http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.3.21/bitcoi… $ sha1sum bitcoin-0.3.21-win32-setup.exe 3f94d6a8b08c455a7886561089270247eaada7b4 bitcoin-0.3.21-win32-setup.exe 2. install with wine 3. start bitcoin $ wine bitcoin.exe fixme:msvcrt:_setmbcp trail bytes data not available for DBCS codepage 0 - assuming all bytes fixme:toolhelp:CreateToolhelp32Snapshot Unimplemented: heap list snapshot fixme:toolhelp:Heap32ListFirst : stub fixme:system:SetProcessDPIAware stub! fixme:ntdll:NtLockFile I/O completion on lock not implemented yet fixme:toolhelp:CreateToolhelp32Snapshot Unimplemented: heap list snapshot fixme:toolhelp:Heap32ListFirst : stub some part of bitcoin became transparent, see screenshot for details -- 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 11

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

07 Jan '22

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 07 Jan '22

07 Jan '22

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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs January 2022