wine-bugs May 2023

wine-bugs@winehq.org

1 participants
3167 discussions

[Bug 28678] New: DirectDraw primary buffer is obscured by transparent window
by wine-bugs＠winehq.org 01 Jul '23

01 Jul '23

http://bugs.winehq.org/show_bug.cgi?id=28678 Bug #: 28678 Summary: DirectDraw primary buffer is obscured by transparent window Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-ddraw AssignedTo: wine-bugs(a)winehq.org ReportedBy: octavian.voicu(a)gmail.com Classification: Unclassified Created attachment 36852 --> http://bugs.winehq.org/attachment.cgi?id=36852 Screenshot showing the obscured dialog. When trying to exit from the game The Longest Journey (either via menu option or pressing Alt+F4), a dialog box is shown with Yes/No options. The application uses DirectDraw for rendering. The dialog box and mouse cursor are rendered on an offscreen surface (dialog has an image as the background and buttons use a custom implementation afaics), which is then blitted to the primary buffer (happens like this when you force single buffer mode; with double buffering it could be slightly different, but the overall effect is the same). The dialog is a parent of the main application window, uses the standard dialog window class (atom #32270 or 8000 in hex) and has the WS_POPUP and WS_EX_TRANSPARENT window styles. Window receives a WM_ERASEBKGND message, which is handled by the default dialog proc by painting the background in the standard window background color (gray in this case). When primary buffer is blitted to the d3d surface (ddraw_surface_update_frontbuffer which uses OpenGL), the rendering of the dialog is masked by the window boundaries and the gray rectangle remains. Dialog is interactable and you can click the buttons (if you can do that without seeing where the mouse is). The question is: how can we make the primary buffer draw over WS_EX_TRANSPARENT child windows, as it works on native? Removing the WS_EX_TRANSPARENT style from the dialog window (on runtime, using WinSpy++ 1.7) makes native's behavior identical to current wine behavior (only a gray rectangle is visible). -- 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 30

[Bug 54638] New: amazon music does not let wineserver quit (on shutdown)
by WineHQ Bugzilla 01 Jul '23

01 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=54638 Bug ID: 54638 Summary: amazon music does not let wineserver quit (on shutdown) Product: Wine Version: 8.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: wineserver Assignee: wine-bugs(a)winehq.org Reporter: wine(a)stegm.de Distribution: --- amazon music does not let wineserver quit (on shutdown). That results in waiting for systemd to kill wineserver after 2 minutes. Or wineserver -k must be run as user before shutdown. -- 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 43054] New: FlightUnlimited II crashes during map load, Unhandled page fault on read access to 0x00000039 at address 0x41f87f ( thread 0009)
by wine-bugs＠winehq.org 01 Jul '23

01 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=43054 Bug ID: 43054 Summary: FlightUnlimited II crashes during map load, Unhandled page fault on read access to 0x00000039 at address 0x41f87f (thread 0009) Product: Wine Version: 2.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: haakobja(a)gmail.com Distribution: --- Created attachment 58220 --> https://bugs.winehq.org/attachment.cgi?id=58220 Log from FlightUnlimitedII I recently installed Flight Unlimited II through Wine. After successfully loading the menus (the game needs quartz.dll override, if not it crashes during intro), I tried to play. Only to experience an error stating "Unhandled page fault on read access to 0x00000039 at address 0x41f87f (thread 0009), starting debugger... Unhandled exception: page fault on read access to 0x00000039 in 32-bit code (0x0041f87f)" being thrown in my face. -- 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 36211] New: Sybase PowerDesigner 16.5 'pdshell16.exe' (.NET 4.x WPF app) reports scripting error, needs VBScript_AddTypeLib implementation
by wine-bugs＠winehq.org 30 Jun '23

30 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=36211 Bug ID: 36211 Summary: Sybase PowerDesigner 16.5 'pdshell16.exe' (.NET 4.x WPF app) reports scripting error, needs VBScript_AddTypeLib implementation Product: Wine Version: 1.7.17 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: vbscript Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Hello folks, as the summary says ... Prerequisite: 'winetricks -q dotnet40 vb6run' You might need to navigate the main menu items multiple times until the sub-menu popup shows up (another bug). Main menu, select 'File' -> 'New Model' -> 'XML Model' -> 'XML Model Diagram' A message box is shown, telling "scripting error occurred" Unfortunately this isn't reproducible every time. There seem to be multiple Wine bugs in this app, influencing each other :| --- snip --- fixme:vbscript:VBScript_AddTypeLib (0x6cddff8)->() fixme:vbscript:VBScript_AddTypeLib (0x6cddff8)->() fixme:vbscript:VBScript_AddTypeLib (0x6cddff8)->() fixme:vbscript:VBScript_AddTypeLib (0x6cddff8)->() --- snip --- Source: http://source.winehq.org/git/wine.git/blob/9eed654e054520888429fb7ea1c9d8cc… --- snip --- 447 static HRESULT WINAPI VBScript_AddTypeLib(IActiveScript *iface, REFGUID rguidTypeLib, 448 DWORD dwMajor, DWORD dwMinor, DWORD dwFlags) 449 { 450 VBScript *This = impl_from_IActiveScript(iface); 451 FIXME("(%p)->()\n", This); 452 return E_NOTIMPL; 453 } --- snip --- $ sha1sum PowerDesigner165_DMR.exe c74e4cfd99500d9e3e32713b302ea35bc3f911fb PowerDesigner165_DMR.exe $ du -sh PowerDesigner165_DMR.exe 810M PowerDesigner165_DMR.exe $ wine --version wine-1.7.17-148-g2e5cb7a 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 6

[Bug 54888] New: Transparent window are displayed as black background window on wine
by WineHQ Bugzilla 30 Jun '23

30 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=54888 Bug ID: 54888 Summary: Transparent window are displayed as black background window on wine Product: Wine Version: 8.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bcjon07(a)gmail.com Distribution: --- Some transparent windows are displayed as black background window. Here is a simple WPF window program that can reproduce this issue. On Windows, all parts are transparent except for the graphics and text in the middle, but it has a black background on Wine. It achieves transparency only by adding the following code to the window constructor (the main point is that WindowChrome is used instead of AllowTransparent): WindowStyle = WindowStyle.None; ResizeMode = ResizeMode.NoResize; Background = Brushes.Transparent; WindowChrome.SetWindowChrome(this, new WindowChrome { GlassFrameThickness = new Thickness(-1) }); Download link of the demo program: https://drive.google.com/file/d/1MCrnb1N6cLUzVoX_vO4tFO4qlS_qhAwi/view?usp=… Other clues: Transparent windows implemented using AllowTransparent are valid on Wine, while those implemented using WindowChrome are invalid. On Windows, transparent forms implemented using WindowChrome are frequently used due to better performance(usually). According to my pre investigation, AllowTransparent seems to be implemented using GDI, but WindowChrome mainly uses the DWM API System architecture: x86_64 Ubuntu 20.04 wine 8.6 wine-mono 7.4.0 -- 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 54197] New: cuda-z and warpem fail in wine-staging 7.22 and later
by WineHQ Bugzilla 29 Jun '23

29 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=54197 Bug ID: 54197 Summary: cuda-z and warpem fail in wine-staging 7.22 and later Product: Wine Version: 7.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alois.schloegl(a)gmail.com Distribution: --- Created attachment 73728 --> https://bugs.winehq.org/attachment.cgi?id=73728 screenshot of running cuda-z one wine-staging 7.22 cuda-z fails to run in wine-staging 7.22 and later. It reports the error "CUDA not found. Please update the nvidia-driver.". cuda-z runs fine under wine-staging 7.21 (and earlier) on the same machine with the same nvidia driver. The application "WarpEM" can be also not used anymore because it does not find any GPU. I suspect that disabling the nvcuda-support patches in wine-staging [1] is the reason for this breakage. I believe bug #54102 is related, but the bug report says that this occured already in v7.21. But this issue is not reproducible to me in 7.21 only in 7.22. [1] https://gitlab.winehq.org/wine/wine-staging/-/commit/6c3797b3e8dba19698328c… [2] https://bugs.winehq.org/show_bug.cgi?id=54102 -- 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 54480] New: GPU Caps Viewer does not report any CUDA devices
by WineHQ Bugzilla 29 Jun '23

29 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=54480 Bug ID: 54480 Summary: GPU Caps Viewer does not report any CUDA devices Product: Wine-staging Version: 8.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: danielyhwong(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- wine version 8.1 does not report any cuda devices in Caps viewer 1.58.01 $ deviceQuery deviceQuery Starting... CUDA Device Query (Runtime API) version (CUDART static linking) Detected 2 CUDA Capable device(s) CUDA https://i.imgur.com/zbTiqfC.png OpenCL https://i.imgur.com/jvu8nde.png -- 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 37664] New: CUDA encoder does not work on MediaCoder x64 0.8.33 build 5680
by wine-bugs＠winehq.org 28 Jun '23

28 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=37664 Bug ID: 37664 Summary: CUDA encoder does not work on MediaCoder x64 0.8.33 build 5680 Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: rickardj42(a)gmail.com Distribution: --- Created attachment 50128 --> https://bugs.winehq.org/attachment.cgi?id=50128 Screenshot of the error message In MediaCoder x64 0.8.33 build 5680 attempting to select GPU encoder causes error "No supported acceleration hardware detected", dispite the presence of an NVidia GeForce 750ti in my system. Attempting to force GPU encoding using CUDA encoder results in Error (14) on all items(general encoder error). -- 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 7

[Bug 54739] New: oleaut32:typelib - The 64-bit test_register_typelib_64() crashes in Wine
by WineHQ Bugzilla 28 Jun '23

28 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=54739 Bug ID: 54739 Summary: oleaut32:typelib - The 64-bit test_register_typelib_64() crashes in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: oleaut32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- oleaut32:typelib - The 64-bit test_register_typelib_64() crashes in Wine: typelib.c:7057: Test failed: got 00000002 typelib.c:8195: Test failed: got wrong return code: 2, side: 0200 typelib.c:8231: Test failed: got: 80040155, side: 0200 typelib.c:8235: Test failed: got: 80040154, side: 0200 Unhandled exception: page fault on read access to 0x0000000000000000 in 64-bit code (0x00000000428dc1). [...] Backtrace: =>0 0x00000000428dc1 in oleaut32_test (+0x28dc1) (0x0000000050e538) 1 0x000000004460c8 in oleaut32_test (+0x460c8) (0x000000621080c0) 2 0x0000000050dbeb in oleaut32_test (+0x10dbeb) (0x00000000ab4415) 3 0x0000000050d447 in oleaut32_test (+0x10d447) (0000000000000000) 4 0x0000007b629409 BaseThreadInitThunk+0x9(unknown=<internal error>, entry=<internal error>, arg=<internal error>) [Z:\home\winetest\tools\testbot\var\wine\dlls\kernel32\thread.c:61] in kernel32 (0000000000000000) 5 0x00000170061213 __wine_pop_frame(entry=000000000050D3E0, arg=00000000003F0000) [Z:\home\winetest\tools\testbot\var\wine\include\wine\exception.h:277] in ntdll (0000000000000000) 6 0x00000170061213 RtlUserThreadStart+0x83(entry=[<register RSP not accessible in this frame>, arg=[<register RSP not accessible in this frame>) [Z:\home\winetest\tools\testbot\var\wine\dlls\ntdll\thread.c:295] in ntdll (0000000000000000) 0x00000000428dc1 oleaut32_test+0x28dc1: mov (%rcx), %rax See https://test.winehq.org/data/patterns.html#oleaut32:typelib Where: 2 == ERROR_FILE_NOT_FOUND 0x80040154 == REGDB_E_CLASSNOTREG 0x80040155 == REGDB_E_IIDNOTREG -- 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 50938] New: Stop alt key from getting stuck on alt-tab
by WineHQ Bugzilla 28 Jun '23

28 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=50938 Bug ID: 50938 Summary: Stop alt key from getting stuck on alt-tab Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: sojuz151(a)gmail.com Distribution: --- When you use alt-tab shortcut to switch to another window and then switch back in, application will at no point receive alt key up signal. User needs to press alt again to make this key unstuck. This behevior is observed in Plasma and in lxde, both of them use alt-tab for windows switching. Behaviour on windows: alt key is not stuck in down position after alt-tabing out of any application How to test: this can be observed in any keyboard testing program. I used switch hitter for testing. Is it really a bug? Maybe not. Still very annoying in full-screen 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 5

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 May 2023