wine-bugs June 2023

wine-bugs@winehq.org

1 participants
2653 discussions

[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 55011] New: Cuda-application M/WarpEM got stuck or crashes in wine-staging/7.21, wine/8.9+nvidia-libs
by WineHQ Bugzilla 29 Jun '23

29 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55011 Bug ID: 55011 Summary: Cuda-application M/WarpEM got stuck or crashes in wine-staging/7.21, wine/8.9+nvidia-libs Product: Wine Version: 8.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: nvcuda Assignee: wine-bugs(a)winehq.org Reporter: alois.schloegl(a)gmail.com Distribution: --- M of WarpEM gets stuck very early and eventually crashes. The following steps are needed to reproduce this: 1) install WarpEM according to [1] into wine-staging between v7.17 and v7.21, or wine-8.9 with nvidia-libs. (do not try with wine-staging 7.22 or later, because that has cuda support disabled). This has been testing this with "Shared WoW64" configuration of Wine. Trying to use Wine with the "new WoW64 approach" using -enable-archs=i386,x86_64 did also not work for me, because it failed much earlier when trying to install Cuda/WarpEM. 2) Data (5.5TB!) for testing is available from here [1]. Download and unpack Warpem_test.tar.gz to a directory that is accessible from wine. The screenshots Step1-7 should help to understand how M is supposed to be used. 3) Start M.exe. In my case, I do this ulimit -s 655360 wine $WINEPREFIX/drive_c/Warp/M.exe or vglrun wine $WINEPREFIX/drive_c/Warp/M.exe 4) Within M, do the following steps (see also Step1-7 in [2]): - Step 1: In the GUI window click "LOAD EXISTING FROM FILE" - Step 2: select ...\M_j33\Gag_c2_processing.population - Step 3: Upper right corner Refine button. - Step 4: Click refine - Step 5+6: workers are now testing the memory - Step 7: Eventually (after several minutes), one of the works crash, and there is no further progress. On Windows, this finishes and a new screen appears for the next step. This is not the case here. It gets stuck, and and eventually I stopped wine with <ctrl-C>. A log file is also available [2], but it is too large (1.1 GB) to be included here. If you have suggestions with WINEDEBUG filter should be used, let me know. [1] https://appdb.winehq.org/objectManager.php?sClass=version&iId=40620&iTestin… [2] https://pub.ista.ac.at/~schloegl/warpem-test-data/ -- 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 55159] New: [ms-mpi] mpiexec is unable to connect to the smpd service
by WineHQ Bugzilla 29 Jun '23

29 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55159 Bug ID: 55159 Summary: [ms-mpi] mpiexec is unable to connect to the smpd service Product: Wine Version: 8.0.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: secur32 Assignee: wine-bugs(a)winehq.org Reporter: christian.friedl(a)gmx.at Distribution: Ubuntu Created attachment 74727 --> https://bugs.winehq.org/attachment.cgi?id=74727 Output of `smpd.exe -d` and `mpiexec -d -hosts 1 127.0.0.1 notepad` Running applications with MS-MPI does not work. In order to circumvent https://bugs.winehq.org/show_bug.cgi?id=50341 I started smpd.exe manually with: $ wine 'C:\Program Files\Microsoft MPI\Bin\smpd.exe' -d In a second shell I ran mpiexec: $ wine mpiexec -d -hosts 1 127.0.0.1 notepad The problem is that mpiexec.exe could not connect to smpd.exe because both kerberos and ntlm authentication fail. I have the version 2:4.15.13+dfsg-0ubuntu1.1 of the winbind package installed. The installed MS-MPI version is v10.1.2. Logs including the debug channels `+kerberos,+ntlm,+secur32,+wininet,+seh,+tid` are attached. -- 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 55162] New: Halo 2: Installer shows empty ie-window
by WineHQ Bugzilla 29 Jun '23

29 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55162 Bug ID: 55162 Summary: Halo 2: Installer shows empty ie-window Product: Wine Version: 8.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: odecif(a)gmail.com Distribution: --- Created attachment 74732 --> https://bugs.winehq.org/attachment.cgi?id=74732 console log, 32bit with ie6 installed, after starting "Startup.exe" I do not know why the previous bug was closed in 2015 (https://bugs.winehq.org/show_bug.cgi?id=17543), but the same error still persists today. When executing "Startup.exe" on the CD in a clean 32-bit (and 64-bit as well) prefix a blue windows pops up dislaying absolutely nothing presented (see image). If I install ie6 (winetricks ie6) an error pops up (see image). Attached is a stacktrace of what exists in the console after executing "Startup.exe" from wineconsole with ie6 installed. Br Bob -- 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 6

[Bug 55163] New: compact.exe missing
by WineHQ Bugzilla 28 Jun '23

28 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55163 Bug ID: 55163 Summary: compact.exe missing Product: Wine Version: 8.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: sakul8826(a)gmail.com Distribution: --- Hello, I wanted to use "compact.exe," which is a part of the default Windows 10 installation. I selected "Windows 10" in winecfg, and it appears that compact.exe is missing. I need this program to compress my content (cars, apps, etc.) in Assetto Corsa's Content Manager to reduce their size. I have very limited storage available, and this program (compact.exe) would be extremely helpful. I believe it should be relatively simple to implement this since we could use a Linux compression and decompression tool. Are there any plans to implement this? Thank you in advance. Best regards, Tim Gromeyer -- 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 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 55157] New: Net6 x64 app: unable to allocate more than ~1GB of contiguous memory, OutOfMemory exception
by WineHQ Bugzilla 28 Jun '23

28 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55157 Bug ID: 55157 Summary: Net6 x64 app: unable to allocate more than ~1GB of contiguous memory, OutOfMemory exception Product: Wine Version: 8.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: korshunov(a)macroscop.com Distribution: --- A "big" net6 app may throw an OutOfMemory exception at some point in time. It was found that the exception occurs when the size of byte array is increased and exception is repeatable 100% - it always fails when byte array resized from 26mb to 53mb. Since big app is hard to debug, a simple test app was written, all it tries to do is to resize array x2 in a loop. Test app fails with dotnet OutOfMemory exception 100% of the time, but in the test app the "limit" at which it fails is different, about ~1gb or "Failed at resizing from 534773760 to 1069547520". Here's the code of the test app: var array = new byte[1023]; while (true) try { Array.Resize(ref array, array.Length * 2); } catch (Exception ex) { Console.WriteLine($"Failed at resizing from {array.Length} to {array.Length * 2}\r\n" + ex); return; } Test app is built for "AnyCPU, x64 preferred". Net6 runtime (6.0.16) is installed via winetricks. For the tests, x86 version of net6 runtime has been uninstalled, so the test app is guaranteed to run in x64. Test app is available via the link below. What I've already tried: - wine 8.11 staging - fails with OutOfMemory exception, "Failed at resizing from 534773760 to 1069547520". WINEDEBUG output available through the link below. - wine 8.0 with patch from https://bugs.winehq.org/show_bug.cgi?id=52396 - fails with same error. WINEDEBUG output available through the link below. - running app with wine64, used clean prefix - same error. - wine 7.13 - fails with same error. - wine 8.11, but test app built for netFramework46 - no OutOfMemory, fails when overflowing integer, "Failed at resizing from 2139095040 to -16777216" which is expected, but it shows that it gets to 2gb mark for the array. I consider this as "working fine". WINEDEBUG output available through the link below. - WineGE with multiple versions from 6.14 to 8.8, consisting of Proton and WineGE patches - net6 app working fine with every wineGE version tested, just as netFramework Test app - created prefix with wine 8.11, run test app, then run test app with WineGE in the same exact prefix - wine fails with OutOfMemory while wineGE executes app normally. - made different net6 app, which just allocates a single array of ~1.5 GB (new byte[1_500_000_000]) - app fails with OutOfMemory every time. It fails at about 1GB (950mb works, while 1050mb does not) Tests were done on three different virtual machines (ubuntu22, centos7, debian9) with different amount of RAM (4-8 GB, swap is 2.5GB). Wine 8.11 is installed on Ubuntu 22 with 4GB RAM. What caught my attention in the logs was the message "find_free_block created new sub-heap xxx of 0x400000 bytes" (4GB, all of the RAM), which mentioned in "net6" logs 1 time, and not mentioned in "netFramework46" logs. What else can I try to fix this or to provide more information? Links to a WINEDEBUG output (wine8.11-net6, wine8.11-netFramework46, "wine 8.0 with patch"-net6), logs taken with command WINEDEBUG=+timestamp,+seh,+heap,+virtual,+pid wine Tests_autoresize/Tests_net6.exe >>wine811_tshvp_net6_resize.log 2>&1 https://drive.google.com/drive/folders/1fgr0J6dKBvBOHWrfYC0UCrflxiAYOjZ2?us… -- 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 55044] New: dnSpy 6.2.0 crashes on start with a stackoverflow
by WineHQ Bugzilla 28 Jun '23

28 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55044 Bug ID: 55044 Summary: dnSpy 6.2.0 crashes on start with a stackoverflow Product: Wine Version: 8.9 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- This is introduced in https://github.com/dnSpyEx/dnSpy/releases/download/v6.2.0-rc1/dnSpy-net-win… Version 6.1.9 works: https://github.com/dnSpyEx/dnSpy/releases/download/v6.1.9/dnSpy-net-win64.z… -- 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

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