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

[Bug 51827] d3dx10_34:d3dx10 crashes on all versions of Windows

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=51827 --- Comment #1 from Nikolay Sivov <bunglehead(a)gmail.com> --- Created attachment 70950 --> https://bugs.winehq.org/attachment.cgi?id=70950 patch Could you check if this helps? Reducing range like this patch does, seems to affect testbot results. I don't see all affected test machines available for testbot, is there a way to run on all of them, before submitting? -- 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.

Nov. 3, 2021

[Bug 51966] New: Autostart fluidsynth

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=51966 Bug ID: 51966 Summary: Autostart fluidsynth Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: es20490446e(a)gmail.com Distribution: --- Many distros keep fluidsynth off by default because it consumes quite some memory (126MiB), and usually it conflicts with other user sessions (only one session can run fluidsynth at the same time). If fluidsynth isn't running Wine could autostart it, so midi music works. Once Wine is closed, if it was started by Wine, Wine could close it. A good default configuration for launching it is: fluidsynth -si -a alsa -m alsa_seq -C no -g 0.5 -L 1 -r 48000 -R yes -z 1024 -o synth.default-soundfont="[soundfont]" Where soundfont could be, if present and in this order: - GeneralUser.sf2 (better more realistic audio) - FluidR3_GM.sf2 (more frequent) Under one of these folders, depending on the distro: /usr/share/soundfonts (fluidsynth default, modern) /usr/share/sounds/sf2 (debian default, vintage) -- 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.

Nov. 3, 2021

[Bug 51957] Program started via HKLM\Software\Microsoft\Windows\CurrentVersion\App Paths should also be started if extension ".exe" is missing

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=51957 Louis Lenders <xerox.xerox2000x(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #70937|0 |1 is obsolete| | --- Comment #3 from Louis Lenders <xerox.xerox2000x(a)gmail.com> --- Created attachment 70949 --> https://bugs.winehq.org/attachment.cgi?id=70949 possible patch Attached a simple patch that fixes the bug, but I don`t know if this is the right way to fix it -- 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.

Nov. 3, 2021

[Bug 51957] Program started via HKLM\Software\Microsoft\Windows\CurrentVersion\App Paths should also be started if extension ".exe" is missing

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=51957 --- Comment #2 from Louis Lenders <xerox.xerox2000x(a)gmail.com> --- Created attachment 70948 --> https://bugs.winehq.org/attachment.cgi?id=70948 test executable I did a bit more testing, and it turns out that Autohotkey does successfully start when you start it via "cmd /c Autohotkey", but it doesn't when trying to start via the PSconsole. So I put extra traces in the in shelexec.c to find the difference and it looks like essential difference is: Via cmd one gets in ShellExecuteExW for sei->lpVerb: L"open" whereas via PSconsole one gets: sei->lpVerb NULL I have attached test-executable that replicates the problem, and source below. To avoid having to install Autohotkey, it tries to start something outside the path, like ngen.exe On windows this successfully is started (via ShellExecuteExW), whereas in wine this fails. I`ll see if i try add test to wine Source of test executable: #include <windows.h> #include <stdio.h> int __cdecl wmain( int argc, WCHAR *argv[] ) { HKEY hk; WCHAR app_pathW[] = L"Software\\Microsoft\\Windows\\CurrentVersion\\App Paths\\ngen.exe"; WCHAR exe_pathW[] = L"c:\\windows\\MicroSoft.NET\\Framework\\v4.0.30319\\ngen.exe"; BOOL success = FALSE; SHELLEXECUTEINFOW sei; memset( &sei, 0, sizeof( sei ) ); sei.cbSize = sizeof( sei ); // sei.lpVerb = NULL; sei.lpFile = L"ngen"; sei.fMask = 1344; sei.nShow = 1; RegCreateKeyW( HKEY_LOCAL_MACHINE, app_pathW, &hk ); RegSetValueExW(hk, NULL, 0, REG_SZ, (LPBYTE) exe_pathW, sizeof(WCHAR) * ( lstrlenW(exe_pathW)+1)); RegCloseKey( hk ); printf("Trying to start ngen via App Paths...\n"); success = ShellExecuteExW( &sei ); if ( success ) printf("successfully started ngen.exe\n"); else printf("No success!!!!!!!!!!!!!\n"); RegDeleteKeyW( HKEY_LOCAL_MACHINE, app_pathW); return 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.

Nov. 3, 2021

[Bug 10922] JDK 6 offline installer fails to create jdk1.6.0_03\jre\bin\msvcr71.dll, puts up error dialog

by WineHQ Bugzilla

Nov. 3, 2021

[Bug 51628] Samsung SDK 1.2.2 for Java ME: Black window

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=51628 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |https://web.archive.org/web | |/20210819094918/https://sof | |tpedia-secure-download.com/ | |dl/cdc4ff091f2abe041e966cd4 | |8078eedc/611e283c/100160914 | |/software/programming/Samsu | |ng_sdk_1.2.2.exe Keywords| |download Resolution|--- |FIXED CC| |focht(a)gmx.net Component|-unknown |gdi32 Status|REOPENED |RESOLVED --- Comment #14 from Anastasius Focht <focht(a)gmx.net> --- Hello folks, next time please provide *exact* instructions on all artifacts, including download link to used JDK and the command line to be run. If those are in other bugs, either copy them (preferred) and/or link bug reports. Stable download links via Internet Archive: Samsung SDK 1.2.2 for Java ME https://web.archive.org/web/20210819094918/https://softpedia-secure-downloa… $ sha1sum Samsung_sdk_1.2.2.exe 88789b058f468ab28f5bea6de046e5c9649980eb Samsung_sdk_1.2.2.exe $ du -sh Samsung_sdk_1.2.2.exe 61M Samsung_sdk_1.2.2.exe Original vendor page: http://web.archive.org/web/20150322214547/http://developer.samsung.com/java… JDK 1.6 https://web.archive.org/web/20111129235500/http://download.oracle.com/otn-p… $ sha1sum jdk-6u26-windows-i586.exe 4745fa7b3f82053363ba2e29a2c111f1c2a737dc jdk-6u26-windows-i586.exe $ du -sh jdk-6u26-windows-i586.exe 77M jdk-6u26-windows-i586.exe Just a guess because OP didn't provide instructions what to run. --- snip --- $ pwd /home/focht/.wine/drive_c/Samsung_SDK_122/bin $ wine ./ktoolbar.exe # or any other $ wine cmd.exe /c DefaultDevice.bat ... C:\Samsung_SDK_122\bin>C:\PROG~5P2\Java\JDK1~OW0.0_2\bin\java.exe -Dkvem.home="C:\Samsung_SDK_122" -cp C:\SAMS~45M\wtklib\substance.jar;C:\SAMS~45M\wtklib\kenv.zip;C:\SAMS~45M\wtklib\ktools.zip com.sun.kvem.preferences .DefaultDeviceWindow ... --- snip --- I could reproduce the black window with Wine 6.15 but not with Wine 6.16 release. Wine 6.14 works fine as well. It was most likely a regression from work on the GDI syscall interface (gdi32). $ wine --version wine-6.16 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.

Nov. 3, 2021

[Bug 45277] Multiple applications need Vulkan child window rendering (DxO PhotoLab, Affinity Photo, Google Earth Pro, Autodesk Fusion 360)

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=45277 --- Comment #80 from Andy Holst <andy.holst85(a)gmail.com> --- For full reference of how I compile Wine v6.20 with Wine staging v6.20 patches take a look at https://github.com/andyholst/robotic_experimentation/blob/setup_ironcad_wit… -- 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.

Nov. 3, 2021

[Bug 45277] Multiple applications need Vulkan child window rendering (DxO PhotoLab, Affinity Photo, Google Earth Pro, Autodesk Fusion 360)

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=45277 --- Comment #79 from Andy Holst <andy.holst85(a)gmail.com> --- (In reply to Andy Holst from comment #78) > So I'm compiling Wine source and applying patches with Wine staging. I'm > going to test out IronCAD 2019 by rendering graphics with Vulkan. Is there > anything I need to know about what patch to apply? > > Is it still patch https://bugs.winehq.org/attachment.cgi?id=70100 aka 'Patch > with sync in vkAcquireNextImage2KHR' that needs to be applied as is by > providing > > './patches/patchinstall.sh DESTDIR="`pwd`" --all -W Pipelight -W > winex11-Vulkan_support' that just support v6.19? > > Or will the following commands by literally applying the wine-staging v6.20 > patches as is in a open container context? > > For amd64 architecture: > > ARG VERSION="6.20" > ARG WINE_VERSION="${VERSION}~buster" > ARG WINE_DEB_VERSION="${WINE_VERSION}-1" > > RUN DEBIAN_FRONTEND=noninteractive apt build-dep -y > wine="${WINE_DEB_VERSION}" > > RUN git clone -b "wine-${VERSION}" git://source.winehq.org/git/wine.git > /usr/src/wine-source > > RUN git clone -b "v${VERSION}" > https://github.com/wine-staging/wine-staging.git /usr/src/wine-staging > > RUN mkdir -p /usr/src/wine64 > > WORKDIR /usr/src/wine-staging/patches > > RUN exec /bin/bash -c './patchinstall.sh DESTDIR=/usr/src/wine-source --all > --force-autoconf' > > WORKDIR /usr/src/wine64 > > RUN exec /bin/bash -c 'PKG_CONFIG_PATH=/usr/lib/pkgconfig > ../wine-source/configure --enable-win64 \ > --prefix=/opt/wine-staging' > > RUN exec /bin/bash -c 'make -j7' > > For i386 architecture: > > ARG VERSION="6.20" > ARG WINE_VERSION="${VERSION}~buster" > ARG WINE_DEB_VERSION="${WINE_VERSION}-1" > > RUN DEBIAN_FRONTEND=noninteractive apt build-dep -y > wine="${WINE_DEB_VERSION}" > > RUN mkdir -p /usr/src/wine32 /usr/src/wine32-tools > COPY --from=amd64 /usr/src/wine-source /usr/src/wine-source > COPY --from=amd64 /usr/src/wine64 /usr/src/wine64 > > WORKDIR /usr/src/wine32-tools > > RUN exec /bin/bash -c 'PKG_CONFIG_PATH=/usr/lib/pkgconfig > ../wine-source/configure' > > RUN exec /bin/bash -c 'make -j7' > > WORKDIR /usr/src/wine32 > > RUN exec /bin/bash -c 'PKG_CONFIG_PATH=/usr/lib/pkgconfig > ../wine-source/configure --with-wine64=../wine64 \ > --with-wine-tools=../wine32-tools --prefix=/opt/wine-staging' > > RUN exec /bin/bash -c 'make -j7' > > RUN exec /bin/bash -c 'checkinstall -D --pkgname=wine-local > --pkgversion="${VERSION}" --nodoc --install=yes' > > From final amd64 architecture do following: > > > RUN cd /usr/bin && wget > 'https://raw.githubusercontent.com/Winetricks/winetricks/master/src/ > winetricks' > > RUN chmod +x /usr/bin/winetricks > > WORKDIR /home/ubuntu > > COPY --from=amd64 /usr/src/wine-source /home/ubuntu/wine-source > COPY --from=amd64 /usr/src/wine64 /home/ubuntu/wine64 > COPY --from=i386 /opt/wine-staging /opt/wine-staging > COPY --from=i386 /lib /lib > > WORKDIR /home/ubuntu/wine64 > > RUN exec /bin/bash -c 'checkinstall -D --pkgname=wine-local > --pkgversion="${VERSION}" --nodoc --install=yes' Clarification: To apply the specific mentioned patch above is it just the following commands ? /usr/src/wine-staging/patches$ /patches/patchinstall.sh DESTDIR="`pwd`" --all -W Pipelight -W winex11-Vulkan_support /$ cd /usr/src && wget -O wine-vk-child-window.patch -nc "https://bugs.winehq.org/attachment.cgi?id=70100" /usr/src/wine-source$ patch -p1 < ../wine-vk-child-window.patch Then the previous mentioned compiling and installing as usual? -- 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.

Nov. 3, 2021

[Bug 45277] Multiple applications need Vulkan child window rendering (DxO PhotoLab, Affinity Photo, Google Earth Pro, Autodesk Fusion 360)

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=45277 Andy Holst <andy.holst85(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |andy.holst85(a)gmail.com --- Comment #78 from Andy Holst <andy.holst85(a)gmail.com> --- So I'm compiling Wine source and applying patches with Wine staging. I'm going to test out IronCAD 2019 by rendering graphics with Vulkan. Is there anything I need to know about what patch to apply? Is it still patch https://bugs.winehq.org/attachment.cgi?id=70100 aka 'Patch with sync in vkAcquireNextImage2KHR' that needs to be applied as is by providing './patches/patchinstall.sh DESTDIR="`pwd`" --all -W Pipelight -W winex11-Vulkan_support' that just support v6.19? Or will the following commands by literally applying the wine-staging v6.20 patches as is in a open container context? For amd64 architecture: ARG VERSION="6.20" ARG WINE_VERSION="${VERSION}~buster" ARG WINE_DEB_VERSION="${WINE_VERSION}-1" RUN DEBIAN_FRONTEND=noninteractive apt build-dep -y wine="${WINE_DEB_VERSION}" RUN git clone -b "wine-${VERSION}" git://source.winehq.org/git/wine.git /usr/src/wine-source RUN git clone -b "v${VERSION}" https://github.com/wine-staging/wine-staging.git /usr/src/wine-staging RUN mkdir -p /usr/src/wine64 WORKDIR /usr/src/wine-staging/patches RUN exec /bin/bash -c './patchinstall.sh DESTDIR=/usr/src/wine-source --all --force-autoconf' WORKDIR /usr/src/wine64 RUN exec /bin/bash -c 'PKG_CONFIG_PATH=/usr/lib/pkgconfig ../wine-source/configure --enable-win64 \ --prefix=/opt/wine-staging' RUN exec /bin/bash -c 'make -j7' For i386 architecture: ARG VERSION="6.20" ARG WINE_VERSION="${VERSION}~buster" ARG WINE_DEB_VERSION="${WINE_VERSION}-1" RUN DEBIAN_FRONTEND=noninteractive apt build-dep -y wine="${WINE_DEB_VERSION}" RUN mkdir -p /usr/src/wine32 /usr/src/wine32-tools COPY --from=amd64 /usr/src/wine-source /usr/src/wine-source COPY --from=amd64 /usr/src/wine64 /usr/src/wine64 WORKDIR /usr/src/wine32-tools RUN exec /bin/bash -c 'PKG_CONFIG_PATH=/usr/lib/pkgconfig ../wine-source/configure' RUN exec /bin/bash -c 'make -j7' WORKDIR /usr/src/wine32 RUN exec /bin/bash -c 'PKG_CONFIG_PATH=/usr/lib/pkgconfig ../wine-source/configure --with-wine64=../wine64 \ --with-wine-tools=../wine32-tools --prefix=/opt/wine-staging' RUN exec /bin/bash -c 'make -j7' RUN exec /bin/bash -c 'checkinstall -D --pkgname=wine-local --pkgversion="${VERSION}" --nodoc --install=yes' >From final amd64 architecture do following: RUN cd /usr/bin && wget 'https://raw.githubusercontent.com/Winetricks/winetricks/master/src/winetric…' RUN chmod +x /usr/bin/winetricks WORKDIR /home/ubuntu COPY --from=amd64 /usr/src/wine-source /home/ubuntu/wine-source COPY --from=amd64 /usr/src/wine64 /home/ubuntu/wine64 COPY --from=i386 /opt/wine-staging /opt/wine-staging COPY --from=i386 /lib /lib WORKDIR /home/ubuntu/wine64 RUN exec /bin/bash -c 'checkinstall -D --pkgname=wine-local --pkgversion="${VERSION}" --nodoc --install=yes' -- 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.

Nov. 3, 2021

[Bug 51628] Samsung SDK 1.2.2 for Java ME: Black window

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=51628 --- Comment #13 from Josesk Volpe <joseskvolpe(a)gmail.com> --- I tried it again in Wine 6.20 i had recently upgraded, in a prolonged time. I had no issue with windows opening or turning in black i had in Wine 6.16. So yeah, i can confirme that was fixed. :3 -- 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.

Nov. 3, 2021