wine-bugs June 2023

wine-bugs@winehq.org

1 participants
3070 discussions

[Bug 55118] New: shell32:shlfolder - test_SHOpenFolderAndSelectItems() is missing a registry key in the new WoW mode
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55118 Bug ID: 55118 Summary: shell32:shlfolder - test_SHOpenFolderAndSelectItems() is missing a registry key in the new WoW mode Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: shell32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- shell32:shlfolder - test_SHOpenFolderAndSelectItems() is missing a registry key in the new WoW mode: shlfolder.c:5512: Test failed: Got unexpected hr 0x80040152. shlfolder.c:5513: Test failed: Failed to create window. shlfolder.c:5520: Test failed: Got unexpected hr 0x80040152. shlfolder.c:5521: Test failed: Failed to create window. shlfolder.c:5530: Test failed: Got unexpected hr 0x80040152. shlfolder.c:5531: Test failed: Failed to create window. shlfolder.c:5540: Test failed: Got unexpected hr 0x80040152. shlfolder.c:5541: Test failed: Failed to create window. shlfolder.c:5550: Test failed: Got unexpected hr 0x80040152. shlfolder.c:5551: Test failed: Failed to create window. See https://test.winehq.org/data/patterns.html#shell32:shlfolder Where 0x80040152 == REGDB_E_KEYMISSING This happens in both the 32-bit and 64-bit tests but only in the new Windows-on-Windows mode. See the *-i386 and *-x86_64 results. See also bug 55117 where shell32:shelldispatch has a similar issue. -- 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 55117] New: shell32:shelldispatch - test_ShellWindows() is missing a registry key in the new WoW mode
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55117 Bug ID: 55117 Summary: shell32:shelldispatch - test_ShellWindows() is missing a registry key in the new WoW mode Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: shell32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- shell32:shelldispatch - test_ShellWindows() is missing a registry key in the new WoW mode: shelldispatch.c:1025: Test failed: got 0x80040152 See https://test.winehq.org/data/patterns.html#shell32:shelldispatch Where 0x80040152 == REGDB_E_KEYMISSING This happens in both the 32-bit and 64-bit tests but only in the new Windows-on-Windows mode. See the *-i386 and *-x86_64 results. -- 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 55116] New: services.exe:service - service_main() is missing PATHEXT in the new WoW mode
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55116 Bug ID: 55116 Summary: services.exe:service - service_main() is missing PATHEXT in the new WoW mode Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- services.exe:service - test_service() is missing PATHEXT in the new WoW mode: service.c:420: Test failed: service: did not find PATHEXT environment variable See https://test.winehq.org/data/patterns.html#services.exe:service This happens during both test_service() and test_kill_service_process(), in both the 32-bit and 64-bit tests but only in the new Windows-on-Windows mode. -- 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 55094] New: Memory Access Violation & Run-Time Error 7 in WINE
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55094 Bug ID: 55094 Summary: Memory Access Violation & Run-Time Error 7 in WINE Product: Wine Version: 8.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: vbscript Assignee: wine-bugs(a)winehq.org Reporter: vikasy.enjay(a)gmail.com Distribution: --- Created attachment 74654 --> https://bugs.winehq.org/attachment.cgi?id=74654 Memory Access Violation & Run-Time Error 7 in WINE Memory Access Violation & Run-Time Error 7 in WINE: I am writing this to seek assistance regarding an issue I encountered while installing and running "Busy Accounting Software" using Wine. Despite my previous unsuccessful attempts, I was eventually able to install the software. However, I am currently facing an ongoing problem when attempting to execute the application. It consistently displays a "Runtime 7 Error and Memory Access Violation" error. Any assistance or troubleshooting steps you can provide would be greatly appreciated. Thank you for your attention to this matter. -- 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 7

[Bug 37346] New: New application , installed successfully , starts up fine , no data storing , BUSY WIN ACCOUNTING APP
by wine-bugs＠winehq.org 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=37346 Bug ID: 37346 Summary: New application , installed successfully , starts up fine , no data storing , BUSY WIN ACCOUNTING APP Product: Wine Version: unspecified Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lax.sunny(a)gmail.com Created attachment 49664 --> https://bugs.winehq.org/attachment.cgi?id=49664 Log created by wine on running the app , problem is with database storage and runtime functions Application named busy win very much famous accounting software tried using number of prefixes application installs smoothly when i run the app it starts up normally but crashes on adding a new company or detecting an old DATABASE -- 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 10

[Bug 55112] New: Chip's Challenge (Steam version) only shows black screen on Nvidia dGPU (works fine on AMD iGPU)
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55112 Bug ID: 55112 Summary: Chip's Challenge (Steam version) only shows black screen on Nvidia dGPU (works fine on AMD iGPU) Product: Wine Version: 8.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: asdfghrbljzmkd(a)outlook.com Distribution: --- Created attachment 74675 --> https://bugs.winehq.org/attachment.cgi?id=74675 Log when running game on Nvidia dGPU The Steam version of Chip's Challenge only shows a black screen when running on my Nvidia dGPU (RTX 3060 Mobile). The game displays fine on my AMD iGPU (Vega). Note: as this version of the game is only available on Steam, it was tested with Proton 8.0. However, due to the age and nature of the game (basic 2D win32), it is very unlikely to be hitting any Proton-specific code paths (there are no mentions of DXVK/etc in the log either.) If needed, I can try more ways to run it in stock Wine Devel, but it's 2AM and I just wanted to at least get the bug report out. -- 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 50079] New: Wine msiexec fails when building inside a windows/mac os x docker container
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=50079 Bug ID: 50079 Summary: Wine msiexec fails when building inside a windows/mac os x docker container Product: Wine Version: 5.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msi Assignee: wine-bugs(a)winehq.org Reporter: spam(a)crasu.de Distribution: --- Created attachment 68535 --> https://bugs.winehq.org/attachment.cgi?id=68535 Run with winedebug=msi and strace Sample dockerfile: FROM ubuntu:20.04 RUN export DEBIAN_FRONTEND="noninteractive" \ && dpkg --add-architecture i386 \ && apt-get update \ && apt-get install -y wget winbind xvfb unzip curl jq \ && apt-get remove -y libmysqlclient21 mysql-common \ && apt autoremove -y RUN wget -nc https://dl.winehq.org/wine-builds/winehq.key && apt-key add winehq.key RUN echo 'deb https://dl.winehq.org/wine-builds/ubuntu/ focal main' > /etc/apt/sources.list.d/wine.list RUN export DEBIAN_FRONTEND="noninteractive" \ && apt-get update \ && apt-get install -o APT::Immediate-Configure=false --install-recommends -y winehq-devel RUN useradd -ms /bin/bash wineuser # Install winemono RUN wget https://dl.winehq.org/wine/wine-mono/5.1.1/wine-mono-5.1.1-x86.msi RUN WINEPREFIX=/home/wineuser/.wine su wineuser -c "wine msiexec /i wine-mono-5.1.1-x86.msi && wineserver -w" Eroor message: 0024:err:msi:ACTION_InstallFiles compressed file wasn't installed (L"bin\\libmono-2.0-x86.dll") 0024:err:msi:execute_script Execution of script 0 halted; action L"InstallFiles" returned 1603 I tried different msis (wine gecko, wine mono, ....) they all fail. After serveral tries the installation sometimes does not through an error. But the package is still not fully installed. Reference: https://github.com/Winetricks/winetricks/issues/1525 -- 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 51502] New: Civilization 3 Sound Stutters, loops, and fails (eventually)
by WineHQ Bugzilla 22 Jun '23

22 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=51502 Bug ID: 51502 Summary: Civilization 3 Sound Stutters, loops, and fails (eventually) Product: Wine Version: 6.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mountmgr.sys Assignee: wine-bugs(a)winehq.org Reporter: bryan(a)varnernet.com Distribution: --- Audio on Civilization III is just not very good. Typical short sounds stutter, playback sounding badly rendered into the target buffer, loop when they shouldn't, etc. The most common problem is for the sound (all of it) to just stop, or just continuously loop a small soundfile that should have been a one-off play at the triggered point in time. Looks like the app is using dsound, along with winmm to mmioOpenA the .wav's. -- 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 52762] New: DesignDoll will not boot/crashes upon booting.
by WineHQ Bugzilla 22 Jun '23

22 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=52762 Bug ID: 52762 Summary: DesignDoll will not boot/crashes upon booting. Product: Wine Version: 7.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: catchyandcleche(a)gmail.com Distribution: --- Created attachment 72129 --> https://bugs.winehq.org/attachment.cgi?id=72129 This file (designdoll_backtrace01.txt) is the backtrace file/error log file that was created when I tried to run the DesignDoll application. I am using a GUI version of Ubuntu for Desktop (Ubuntu 20.04.4 LTS), also utilizing WINE version 7.0 (Displayed as wine-7.0 in the terminal). When double clicking the .desktop application created on the desktop (DesignDoll.desktop) after installing the DesginDollLauncher.exe program and after making sure that the DesignDoll.desktop shortcut created during the installation process allows launching, the program will boot* but quickly crash. I attached the program error log (see "designdoll_backtrace01.txt). *I can only assume that the application booted (or at least tried to) and quickly crashed. It did not display any indication that the program had booted in the GUI environment. When a window did show up to indicate that the program had run (in a sense), it was to inform me of the fact that the program crashed (or simply could not boot). -- 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 55107] New: DirectX programs cannot run on dedicated GPU in windowed mode for hybrid-graphics laptop
by WineHQ Bugzilla 22 Jun '23

22 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55107 Bug ID: 55107 Summary: DirectX programs cannot run on dedicated GPU in windowed mode for hybrid-graphics laptop Product: Wine Version: 8.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: xuancong84(a)gmail.com Distribution: --- Years ago, I created a Direct3D program with statically-linked C library. This program has minimal library dependency and has been tested working on all versions of Windows with DirectX 9 supported. You can download it at: https://github.com/xuancong84/solid-rubix-cube/raw/master/Release/svcube.exe I typically run this programs in 4 modes of Wine: 1. full-screen mode without dedicated GPU, `wine svcube.exe` 2. full-screen mode with dedicated GPU, `__NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia wine svcube.exe` 3. windowed mode without dedicated GPU, cmdline same as 1 but with 'emulate a virtual desktop' checked 4. windowed mode with dedicated GPU, cmdline same as 2 but with 'emulate a virtual desktop' checked From Wine 5.0 onwards (not tested on older versions), not a single version of Wine (including both wine and winehq, including -stable -staging and -devel) can pass all the 4 modes. In the latest winehq-stable (version 8.0.1~bullseye-1, on MX-Linux21/Debian11), the program can run successfully in 1,2, and 3, but crashes on 4 with the following error: ``` 002c:fixme:winediag:LdrInitializeThunk wine-staging 7.22 is a testing version containing experimental patches. 002c:fixme:winediag:LdrInitializeThunk Please mention your exact version when filing bug reports on winehq.org. 0084:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 0084:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 0084:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 0084:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 MESA-INTEL: warning: Performance support disabled, consider sysctl dev.i915.perf_stream_paranoid=0 MESA-INTEL: warning: Performance support disabled, consider sysctl dev.i915.perf_stream_paranoid=0 MESA-INTEL: warning: Performance support disabled, consider sysctl dev.i915.perf_stream_paranoid=0 0110:fixme:ver:GetCurrentPackageId (006CFAF0 00000000): stub 006c:fixme:imm:ImeSetActiveContext (0000000000010026, 0): stub 006c:fixme:imm:ImmReleaseContext (0000000000010020, 0000000000010026): stub 0110:fixme:imm:ImeSetActiveContext (00010072, 1): stub 0110:fixme:imm:ImmReleaseContext (0002006A, 00010072): stub X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 156 (NV-GLX) Minor opcode of failed request: 43 () Serial number of failed request: 409 Current serial number in output stream: 410 ``` I have NVIDIA CUDA installed (Driver Version: 530.30.02, CUDA Version: 12.1). And PyTorch/Tensorflow can run with/without GPU decoding. I am pretty sure my Nvidia GLX is working properly because Mode 2 can run successfully with the process appearing in `nvidia-smi` and taking GPU usage. -- 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 0

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