wine-bugs

wine-bugs@winehq.org

1 participants
158748 discussions

[Bug 55569] New: mshtml:dom - The 32-bit test_attr_collection_attr() crashes on Windows 10 2004+
by WineHQ Bugzilla 15 Dec '23

15 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=55569 Bug ID: 55569 Summary: mshtml:dom - The 32-bit test_attr_collection_attr() crashes on Windows 10 2004+ Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: mshtml Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com mshtml:dom - The 32-bit test_attr_collection_attr() crashes on Windows 10 2004+: dom.c:3679: this is the last test seen before the exception 1268:dom: unhandled exception c0000005 at 00000001 See https://test.winehq.org/data/patterns.html#mshtml:dom This crash is systematic and started on 2023-08-30. -- 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 54769] New: major regression in dnSpy startup time
by WineHQ Bugzilla 15 Dec '23

15 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=54769 Bug ID: 54769 Summary: major regression in dnSpy startup time Product: Wine Version: 8.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: galtgendo(a)o2.pl Distribution: --- (OK, this will be quite a bit different than what I've planned when I started to write this) Let's start with an oddity: only 32bit versions of dnSpy work, 64bit fail to show anything besides the recently popular stack corruption line (it does not terminate upon it, but fails to do anything else either). The problem (initially observed in 6.1.8, but dnSpyEx 6.3.0 has the same problem): I'm not quite sure when this happened, but IIRC it was at most two releases back, maybe it was the latest one. Before, upon startup there was a minor delay before the window showed up and every now and then (but relatively rarely) the window got filled with visual garbage until it was refreshed. Now, it *seems* corruption has been dealt with (though that needs more time to be verified), but there's a crippling startup delay (over 2-3 min) between when a blank window shows up and when it's filled with content. -- 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 8

[Bug 54361] New: Winebus doesn't enumerate evdev devices in a --without-sdl build unless SDL also disabled by winebus registry key
by WineHQ Bugzilla 15 Dec '23

15 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=54361 Bug ID: 54361 Summary: Winebus doesn't enumerate evdev devices in a --without-sdl build unless SDL also disabled by winebus registry key Product: Wine Version: 8.0-rc5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: j-r(a)online.de Distribution: --- Not sure what info to add. -- 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 53845] New: Regression in GetCalendarInfoEx et al
by WineHQ Bugzilla 15 Dec '23

15 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=53845 Bug ID: 53845 Summary: Regression in GetCalendarInfoEx et al Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: elpochodelagente(a)gmail.com Distribution: --- Created attachment 73375 --> https://bugs.winehq.org/attachment.cgi?id=73375 test case, succeeds in Windows and wine 6.0 The following line succeeds in Windows and used to work in Wine 6, but not in Wine 7.19. Attached is a complete program test GetCalendarInfoEx(0, CAL_GREGORIAN_US, 0, CAL_ITWODIGITYEARMAX | CAL_RETURN_NUMBER, 0, 0, dwData); // returns 0 Looking at dlls/kernelbase/locale.c current git master I can see that now there is an explicit check against CAL_GREGORIAN, and if I change the CAL_GREGORIAN_US parameter in the call to CAL_GREGORIAN then GetCalendarInfoEx succeeds. -- 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 21550] New: Winedbg's disassembler doesn't support SSE2 instructions
by wine-bugs＠winehq.org 15 Dec '23

15 Dec '23

http://bugs.winehq.org/show_bug.cgi?id=21550 Summary: Winedbg's disassembler doesn't support SSE2 instructions Product: Wine Version: 1.1.37 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winedbg AssignedTo: wine-bugs(a)winehq.org ReportedBy: b7.10110111(a)gmail.com Winedbg doesn't support SSE2 instructions while gdb does. -- 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 13

[Bug 56028] New: Yakuza 0 not launching on Mac 10.14 with Wine
by WineHQ Bugzilla 15 Dec '23

15 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=56028 Bug ID: 56028 Summary: Yakuza 0 not launching on Mac 10.14 with Wine Product: Wine Version: 8.0.1 Hardware: x86-64 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dariooliviero09(a)gmail.com Created attachment 75673 --> https://bugs.winehq.org/attachment.cgi?id=75673 Here is the error message I don't know much when it comes to Wine, I installed the latest version the site gave me for MAC. In fact, wine's settings should be the default ones, running a Windows 10 system. For a offline single player game such as Fallout New Vegas, Wine worked pretty well. Thanks to that, I decided to try a newer game: Yakuza 0. After having bought it on GOG.com, I tried running the .exe file to no avail. I admit that I didn't spot the issue as I am a bit clueless when it comes to wine, but I should've attached the error message with this. What do I have to do? Thank you in advance -- 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 9

[Bug 55665] New: Wine versions >=8.9 do not load Fallout 4 properly
by WineHQ Bugzilla 15 Dec '23

15 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=55665 Bug ID: 55665 Summary: Wine versions >=8.9 do not load Fallout 4 properly Product: Wine Version: 8.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: rcs777(a)proton.me Distribution: --- I'm sorry if this is a bit long, but I want to be as detailed as possible. In short, I usually build Wine myself using TkGlitch's build scripts and put the resulting build in Lutris's runtime path. I find that TkG Wine offers slightly better performance for Games than my system-provided wine. However when Wine 8.9 rolled around, my self compiled builds stopped working with Fallout 4; the game simply crashed before the intro played with no backtrace provided. My FO4 has its own logs thanks to mods and they told me it crashed in XAudio2_7.dll. It's worth noting that for FO4 I have XAudio2_7 set to native in winecfg, otherwise the audio that comes through is very muffled. It's pretty much a must have for a playable experience. The first thing I did was try a plain non-modified build of Wine from my package manager and a clean prefix, but had no luck. After some trial and error I found that FO4 works perfectly on plain Wine 8.8, so I bisected between 8.8 and 8.9 and found that the startup failure was caused by commit 354a8bb1f4a65bdec052606f2799db9e2907b5b1, "ntdll: Better match Windows subheap sizes". However... Reverting that patch only works up to 8.10, on plain 8.11 and up I was back to square one with crashing in XAudio before the intro video. So after bisecting from 8.10 with that patch reverted just for good measure (I don't know if it's actually needed past 8.9) and 8.11, I came up with a82238fad52761114ab2488d422fad3f70dbb854, "ntdll: Allocate 64-bit and kernel stacks in high memory". Assuming that reverting that patch would fix the latest development version too, I jumped straight to 8.16 and reverted it. I found that I also had to revert 3ac808e46e4795e14c5b999aa39fd9cd15f95279, "ntdll: Set Wow64 user space limit based on LARGE_ADDRESS_AWARE" and f473e31341a0dbc2eb5222cc1d1cfe468946bf0a, "ntdll: Load modules with a high base address in high memory" too. I'm not sure if those last two patches actually break anything, but they seem to depend on variables introduced in the 64-bit Allocate patch so without reverting these too I got build time failures. In any case, once these patches are reverted on Wine 8.16, I get a clean build and Fallout 4 works perfectly again. Here's where I'm confused... I grabbed a vanilla Wine 8.16 build from https://github.com/Kron4ek/Wine-Builds... and it worked, unpatched, out of the box. As far as I can tell from his build scripts, those Wine builds are compiled on Ubuntu Bionic, which means those libraries and compilers are likely far older than mine on Debian Sid. Maybe it's something that an older compiler is doing different, seeing as how the reverted patches seem to have a lot to do with memory allocation? If that were the case it might not even be a bug in Wine. In any case, here's my specs: OS: Debian GNU/Linux trixie/sid x86_64 Kernel: 6.5.0-1-amd64 DE: Plasma 5.27.8 CPU: AMD Ryzen 7 5800X (16) @ 3.800GHz GPU: AMD ATI Radeon RX 5600 OEM/5600 XT / 5700/5700 XT Memory: 3931MiB / 32011MiB GCC Version: gcc (Debian 13.2.0-4) 13.2.0 All build dependencies while running the configure script were satisfied except for OSS, and I've never actually had satisfied. -- 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 55139] New: loader: regression - error running winecfg
by WineHQ Bugzilla 14 Dec '23

14 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=55139 Bug ID: 55139 Summary: loader: regression - error running winecfg Product: Wine Version: 8.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: loader Assignee: wine-bugs(a)winehq.org Reporter: arusanu.bu(a)gmail.com Distribution: --- The switch to PIE loader seems to affect running wine on my system. Running winecfg generates these errors: '$ winecfg wine: created the configuration directory '/home/iurt_build/.wine' 0024:err:environ:run_wineboot failed to start wineboot c00000e5 wine: could not load kernel32.dll, status c0000135' The regression started with commit cc2cfb9b792bee681b96c5859084fd6d4d0bbed7. Reverting that commit and commit 78ed343842dcd8ffb95c416420953e121959d40d commit c55578f3a54c63084657e7d79c043b22b10df989 commit ac1761d1dae8bf114a05e28ed6886deba6c2c860 , allows wine 8.11 to run fine. System: Mageia 9(cauldron), kernel-6.3.9 - x86_64., gcc-12.3.0, mingw-gcc-12.2.1 Wine specific configuration options used for x86_64/i586: ' ./configure --with-x --with-dbus --with-gstreamer --enable-win64 --with-system-dllpath=/usr/x86_64-w64-mingw32/sys-root/mingw/bin --disable-tests ./configure --with-x --with-dbus --with-gstreamer --with-system-dllpath=/usr/i586-w64-mingw32/sys-root/mingw/bin --disable-tests ' -- 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 49312] New: wineg++ - "invalid program stack in 64-bit code" on exception catching - regression
by WineHQ Bugzilla 14 Dec '23

14 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=49312 Bug ID: 49312 Summary: wineg++ - "invalid program stack in 64-bit code" on exception catching - regression Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dd-tom(a)web.de Distribution: --- Created attachment 67324 --> https://bugs.winehq.org/attachment.cgi?id=67324 full crash log Referencing this issue here: https://bugs.launchpad.net/ubuntu/+source/wine/+bug/1881293 When compiling the following C++ program with "wineg++ main.cpp": #include <stdexcept> #include <stdio.h> int main() { printf("start\n"); try { throw std::runtime_error("desc"); } catch (std::exception &ex) { printf("in catch\n"); } printf("end\n"); } Wine crashes with: Unhandled exception: assertion failed, invalid program stack in 64-bit code (0x00007f33f6c24781). The full log is attached. Tested with (not working): - Debian Bullseye and wine 5.0 (packaged) - wine 5.0 compiled from source on Debian Buster Regression since wine 4.0, tested working with: - Debian Buster and wine 4.0 (packaged) - wine 4.0 compiled from source on Debian Buster -- 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 22

[Bug 37517] New: VideoReDo TVSuite H.264 crashes on loading video when using VMR9
by wine-bugs＠winehq.org 14 Dec '23

14 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=37517 Bug ID: 37517 Summary: VideoReDo TVSuite H.264 crashes on loading video when using VMR9 Product: Wine Version: 1.7.30 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: quartz Assignee: wine-bugs(a)winehq.org Reporter: gordon.lack(a)dsl.pipex.com Distribution: --- Created attachment 49929 --> https://bugs.winehq.org/attachment.cgi?id=49929 backtrace saved from crash VideoReDo TVSuite H.264 (http://www.videoredo.com/en/ProductTVS.htm) starts up OK. Under Tools/Options/Playback Devices you can select VMR9 as the Video Driver (FYI: DirectX is also listed there, but it isn't supported any more, and actually used VMR7 as well - the option is going away). This determines the driver used when running the editing page. If you now load a video (mpeg, or h.264) into the program it will 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.

2 17

[Bug 21790] New: 3D Rad demo "BeltBall" can't use its bundled mfc80u.dll?
by wine-bugs＠winehq.org 14 Dec '23

14 Dec '23

http://bugs.winehq.org/show_bug.cgi?id=21790 Summary: 3D Rad demo "BeltBall" can't use its bundled mfc80u.dll? Product: Wine Version: 1.1.38 Platform: x86 URL: http://www.3drad.com/games/BeltBall%20v102.exe OS/Version: Linux Status: UNCONFIRMED Keywords: download Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com The smallest demo from http://www.3drad.com/free-pc-games.php is the 8MB http://www.3drad.com/games/BeltBall%20v102.exe, sha1sum d8827274480b0391ad200478b2ebe26a2658166d BeltBall v102.exe It installs fine, but when you start it, it complains fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.VC80.CRT" (8.0.50727.762) and puts up a dialog saying "The dynamic link library 'MFC80U.DLL' could not be found" even though it's installed in ./3D Rad Games/BeltBall v102/Microsoft.VC80.MFC/mfc80u.dll Perhaps the installer forgot to set an app path or a manifest or something? winetricks vc2005 works around the problem. The game installs and runs fine on Vista; I guess we need to try it on an old XP box that doesn't have vc2005 runtimes already and see if it works there to confirm this bug. (I checked on Vista, and there's no entry for the app in HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths, for what it's worth. And there doesn't seem to be a manifest file next to the .exe.) -- 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 18

[Bug 55927] New: RestoreDC appears to fail with printers
by WineHQ Bugzilla 13 Dec '23

13 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=55927 Bug ID: 55927 Summary: RestoreDC appears to fail with printers Product: Wine Version: 8.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: kadlecf(a)fzu.cz Distribution: --- My wine is packed within the OpenSuse Tumbleweed distribution. Since recently, I experience problems with printing from a custom application which worked in earlier wine versions. Its graphical output (mostly data represented as lines and text) is normally shown on the screen where I encounter no problems. However, currently, when the data is sent to a printer - either one with paper or the CUPS pdf printer -, it is clipped to a rectangle defined by the SaveDC function. This would be OK except that the function RestoreDC BOOL RestoreDC ( [in] HDC hdc, [in] int nSavedDC ) ; does not work properly with the device context hdc connected to a printer device. In brief, the sequence SaveDC (functions involving clipping of the output region) RestoreDC does not restore the clipping region to the original one for the printer (however, it does for the screen device context). -- 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 14

[Bug 55986] New: Gunner3 has flickering in fullscreen
by WineHQ Bugzilla 13 Dec '23

13 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=55986 Bug ID: 55986 Summary: Gunner3 has flickering in fullscreen Product: Wine Version: 8.21 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: --- Since wine-6.1 there is flickering when running Gunner3 in fullscreen mode. Also, from time to time old frame data is shown for a few moments making the game It works with winecfg virtual desktop mode, and making screenshots in fullscreen is hard. It looks similar to the glitches in bug 45168 (but it is unrelated). Don't try to click on a level without having the fix from bug 41977 though, it might crash. The menu is enough to reproduce the 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 4

[Bug 8051] The Sims 2 demo needs support for software vertex processing
by WineHQ Bugzilla 13 Dec '23

13 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=8051 --- Comment #190 from Alexandr Oleynikov <sashok.olen(a)gmail.com> --- (In reply to Zeb Figura from comment #189) > (In reply to Alexandr Oleynikov from comment #188) > > What kind of an update do you want exactly? > > It doesn't look like Wine 9.0-rc1 had any changes related to software vertex > > processing, so the bug stands as it is. And it's probably unlikely that this > > will change, especially with DXVK now being the preferred backend for games > > (which like I mentioned before fully implements this feature). > > I don't know whom DXVK is "preferred" by, but it's not the position of the > Wine project, and it's certainly our intent to implement software vertex > processing mode. It's just not exactly trivial, and there are some > unresolved design questions. Of course, I was not stating it's an official position of the Wine project, it's just merely what vast majority Linux gamers prefer for its far better compatibility and performance for both D3D9 and D3D11 games (if hardware is compatible), and what is used in Proton too. -- 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

[Bug 56019] New: LOCAL_GetBlock not enough space in local heap
by WineHQ Bugzilla 12 Dec '23

12 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=56019 Bug ID: 56019 Summary: LOCAL_GetBlock not enough space in local heap Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: elias_0000_0000(a)yahoo.com Distribution: --- wine-8.0 (Debian 8.0~repack-4) See this game: https://archive.org/details/connections-1995 Same bug with that: https://bugs.winehq.org/show_bug.cgi?id=1490 both with win32 win64 prefix. 0180:err:local:LOCAL_GetBlock not enough space in local heap 076f for 1948 bytes (etc.) -- 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

[Bug 56018] New: Respondus LockDown Browser fatally hangs on loading screen
by WineHQ Bugzilla 12 Dec '23

12 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=56018 Bug ID: 56018 Summary: Respondus LockDown Browser fatally hangs on loading screen Product: Wine Version: 9.0-rc1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: micah.haber(a)gmail.com Distribution: --- Created attachment 75659 --> https://bugs.winehq.org/attachment.cgi?id=75659 No backtrace available, list of deferred .dlls Respondus LockDown Browser v. 2.1.1.05. -- 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

[Bug 8051] The Sims 2 demo needs support for software vertex processing
by WineHQ Bugzilla 12 Dec '23

12 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=8051 --- Comment #189 from Zeb Figura <z.figura12(a)gmail.com> --- (In reply to Alexandr Oleynikov from comment #188) > What kind of an update do you want exactly? > It doesn't look like Wine 9.0-rc1 had any changes related to software vertex > processing, so the bug stands as it is. And it's probably unlikely that this > will change, especially with DXVK now being the preferred backend for games > (which like I mentioned before fully implements this feature). I don't know whom DXVK is "preferred" by, but it's not the position of the Wine project, and it's certainly our intent to implement software vertex processing mode. It's just not exactly trivial, and there are some unresolved design questions. -- 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

[Bug 54396] New: Rutoken driver cannot install.
by WineHQ Bugzilla 12 Dec '23

12 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=54396 Bug ID: 54396 Summary: Rutoken driver cannot install. Product: Wine Version: 8.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: setupapi Assignee: wine-bugs(a)winehq.org Reporter: igor.bz(a)list.ru Distribution: --- Created attachment 73963 --> https://bugs.winehq.org/attachment.cgi?id=73963 Wine log. Distro: Ubuntu 20.04 x64 Kernel: Linux 6.0.9 Download link: https://download.rutoken.ru/Rutoken/Drivers/Current/rtDrivers.exe Steps to reproduce: - Running the installation file (rtDrivers.exe). - An error is reported during the installation process: Error. Error code: 120 (0x00000078): Function not implemented - Installation failure. - The program cannot be installed. Translation: - Установить => Install - Ошибка. Код ошибки: 120 (0x00000078): Функция не реализована => Error. Error code: 120 (0x00000078): Function not implemented - Ошибка. Код ошибки: 3758096907 (0xe000020b) => Error. Error code: 3758096907 (0xe000020b) - 0x80070643 Сбой установки => 0x80070643 Installation failure. -- 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 9

[Bug 16957] New: CreateProcess handles are inherited even when bInheritHandles=FALSE
by wine-bugs＠winehq.org 12 Dec '23

12 Dec '23

http://bugs.winehq.org/show_bug.cgi?id=16957 Summary: CreateProcess handles are inherited even when bInheritHandles=FALSE Product: Wine Version: 1.1.2 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: kernel32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: ben(a)salilab.org Created an attachment (id=18729) --> (http://bugs.winehq.org/attachment.cgi?id=18729) test.c The attached file uses CreateProcess to create a subprocess (gzip in this case) with redirected standard output. In order for this to work properly, the output handle created in this code must be inherited by the subprocess - thus the bInheritHandles argument to CreateProcess must be TRUE. And indeed if this program is compiled to test-true.exe, a simple text file 'test.in' and the gzip binary are placed in the same directory, and then test-true.exe is run, it successfully produces the output test.gz. If the TRUE argument is switched to FALSE and the file is compiled again to test-false.exe, when the program is run in the same way on a 'real' Windows sytem (32 bit Vista Business in this case) the following is output: gzip: stdout: Bad file descriptor This is also fine and expected, since the output file handle was not passed to gzip. *However* if the same test-false.exe program is run with Wine (the Fedora 10 wine-core-1.1.12-1.fc10.i386 package in this case) it runs in just the same way as test-true.exe, generating the test.gz output. This suggests to me that the bInheritHandles argument is ignored by Wine. As stated, this is a minor bug but it would be nice if Wine behaved the same way as Windows here. (In our case we discovered this problem after we tested our program successfully under Wine, but then had it fail on a real Windows system.) I am not familiar with the code, but hopefully it should be straightforward enough to provide the subprocess with invalid handles if bInheritHandles=FALSE? -- 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 15

[Bug 56008] New: Running multiple apps simultaneously causes crashes.
by WineHQ Bugzilla 12 Dec '23

12 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=56008 Bug ID: 56008 Summary: Running multiple apps simultaneously causes crashes. Product: Wine Version: 9.0-rc1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: yaoqi01(a)foxmail.com Distribution: --- My environment is as follows: Hardware: Thinkpad E490 Operating System: Ubuntu 22.04.1 LTS WINE Version: wine-9.0-rc1 Custom DLLs: msls31, msvcp140, riched20 (sourced from Windows 11) Phenomenon: When I use the software "WeChat" and "CloudMusic" consecutively, opening one and minimizing it to run in the background, then opening the other software directly causes the first one to crash. The error codes from the console are: 0970:fixme:winsock:setsockopt Ignoring SO_RANDOMIZE_PORT 0730:fixme:thread:NtSetInformationThread ThreadPowerThrottling stub! 0730:fixme:file:ReplaceFileW Ignoring flags 2 0730:fixme:thread:NtSetInformationThread ThreadPowerThrottling stub! X Error of failed request: BadWindow (invalid Window parameter) Major opcode of failed request: 10 (X_UnmapWindow) Resource id in failed request: 0x4800003 Serial number of failed request: 456 Current serial number in output stream: 456 -- 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 8051] The Sims 2 demo needs support for software vertex processing
by WineHQ Bugzilla 12 Dec '23

12 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=8051 --- Comment #188 from Alexandr Oleynikov <sashok.olen(a)gmail.com> --- What kind of an update do you want exactly? It doesn't look like Wine 9.0-rc1 had any changes related to software vertex processing, so the bug stands as it is. And it's probably unlikely that this will change, especially with DXVK now being the preferred backend for games (which like I mentioned before fully implements this feature). -- 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

[Bug 8051] The Sims 2 demo needs support for software vertex processing
by WineHQ Bugzilla 12 Dec '23

12 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=8051 --- Comment #187 from Chebanenko Igor <chebanenkoigor93(a)gmail.com> --- Wine 9.0-rc1 was released. Any updates? -- 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

[Bug 49195] New: Multiple 4k demoscene OpenGL demos crash on startup (failure to lookup atom 0xC019 'static' from global atom tables)
by WineHQ Bugzilla 12 Dec '23

12 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=49195 Bug ID: 49195 Summary: Multiple 4k demoscene OpenGL demos crash on startup (failure to lookup atom 0xC019 'static' from global atom tables) Product: Wine Version: 5.8 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, extracted from bug 48898 My comment: https://bugs.winehq.org/show_bug.cgi?id=48898#c12 --- quote --- To me it looks like bug 18490 ("Multiple games fail to set pixel format on D3D device context created on desktop window (Empire: Total War, Napoleon: Total War, Utopia City)") but for GL device context on the desktop window. According to online information it's not allowed to do any rendering using this context but enough to call functions like glGetString() etc. Maybe some of the Wine graphics folks could weigh in with an opinion if this limitation is already known / tracked in a bug? --- quote --- Henri's answer: https://bugs.winehq.org/show_bug.cgi?id=48898#c13 --- quote --- I'm not aware of an existing bug report for this issue, no. It does strike me as similar to bug 36506 though, and it would not particularly surprise me if wglGetProcAddress() is supposed to return results consistent with GL_EXTENSIONS/GL_VERSION here, even without a current GL context. I seem to recall having established in the context of bug 18490 that creating a GL context (or more specifically, setting a pixel format) on the desktop window is indeed supposed to fail. In any case, this seems like of of those bugs that would benefit from tests to establish what's supposed to happen. --- quote --- Turns out this was a side-effect of an earlier problem. It was not supposed to be GetDC(NULL) (Desktop window). --- snip --- $ WINEDEBUG=+seh,+relay,+server,+class,+win,+msg wine ./End\ of\ time\ 720p.exe >>log.txt 2>&1 ... 0024:Call user32.ChangeDisplaySettingsA(00421288,00000004) ret=004200da ... 0024: get_desktop_window( force=0 ) 0024: get_desktop_window() = 0 { top_window=00010020, msg_window=00010026 } ... 0024:Ret user32.ChangeDisplaySettingsA() retval=00000000 ret=004200da 0024:Call KERNEL32.CreateThread(00000000,00000000,004201ca,004304e8,00000000,00000000) ret=004200ee ... 0024:Ret KERNEL32.CreateThread() retval=00000080 ret=004200ee 00bc: *fd* 17 <- 38 00bc: init_thread( unix_pid=3683, unix_tid=3729, debug_level=1, teb=7ffd4000, entry=004201ca, reply_fd=15, wait_fd=17, cpu=x86 ) 0024:Call user32.CreateWindowExA(00000000,0000c019,00000000,91000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000) ret=004200f4 0024:trace:win:WIN_CreateWindowEx (null) #c019 ex=00000000 style=91000000 0,0 0x0 parent=(nil) menu=(nil) inst=(nil) params=(nil) 00bc: init_thread() = 0 { pid=0020, tid=00bc, server_start=1d62d3b280579be (-2.9701360), info_size=0, version=603, all_cpus=00000003, suspend=0 } 0024:trace:win:dump_window_styles style: WS_POPUP WS_VISIBLE WS_MAXIMIZE 0024:trace:win:dump_window_styles exstyle: ... 00bc:Starting thread proc 0x4201ca (arg=0x4304e8) ... 0024: create_window( parent=00010020, owner=00000000, atom=c019, instance=00000000, dpi=96, awareness=2, class=L"" ) 0024: create_window() = INVALID_HANDLE { handle=00000000, parent=00000000, owner=00000000, extra=0, class_ptr=00000000, dpi=0, awareness=0 } 0024:warn:win:create_window_handle error 6 creating window 0024:trace:class:GetClassInfoExW (nil) #c019 0x1518f9e0 0024:trace:class:CLASS_FindClass #c019 0x7e910000 -> not found 0024:Ret user32.CreateWindowExA() retval=00000000 ret=004200f4 --- snip --- The failing window creation resulted in NULL handle which got passed to user32.GetDC(): --- snip --- 0024:Call user32.GetDC(00000000) ret=004200fb 0024:trace:win:GetDCEx hwnd 0x10020, hrgnClip (nil), flags 00000003 ... 0024: get_visible_region( window=00010020, flags=00000013 ) 0024: get_visible_region() = 0 { top_win=00010020, top_rect={-1920,0;-1919,1}, win_rect={0,0;3200,1080}, paint_flags=00000001, total_size=16, region={{-1920,0;1280,1080}} } 0024:Call winex11.drv.GetDC(00030039,00010020,00010020,1518fde0,1518fdf0,00000013) ret=7e97bd3e 0024:Ret winex11.drv.GetDC() retval=00000001 ret=7e97bd3e 0024:trace:win:GetDCEx (0x10020,(nil),0x13): returning 0x30039 (updated) 0024:Ret user32.GetDC() retval=00030039 ret=004200fb --- snip --- Well, the rest of the OpenGL story is known and the current behaviour makes sense. Back to the actual problem... The creation of the window which ought the be used for OpenGL context/rendering fails because atom 0xc019 can't be found/resolved. I should have looked more carefully at the trace log and the demo disassembly. --- snip --- ... 004200B6 | xor esi,esi | 004200B8 | push esi | 004200B9 | push esi | 004200BA | push esi | 004200BB | push esi | 004200BC | push esi | 004200BD | push esi | 004200BE | push esi | 004200BF | push esi | 004200C0 | push esi | 004200C1 | push 91000000 | 004200C6 | push esi | 004200C7 | push C019 | global atom! 004200CC | push esi | 004200CD | push 4 | 004200CF | push end of time 720p.421288 | 004200D4 | call dword ptr ds:[<&user32.ChangeDisplaySettingsA>] | 004200DA | push esi | 004200DB | push esi | 004200DC | push end of time 720p.4304E8 | 004200E1 | push end of time 720p.4201CA | 004200E6 | push esi | 004200E7 | push esi | 004200E8 | call dword ptr ds:[<&KERNEL32.CreateThread>] | 004200EE | call dword ptr ds:[<&user32.CreateWindowExA>] | fails 004200F4 | push eax | 004200F5 | call dword ptr ds:[<&user32.GetDC>] | 004200FB | mov edi,eax | 004200FD | mov dword ptr ds:[3AB08EC],eax | 00420102 | push esi | 00420103 | push edi | 00420104 | push esi | 00420105 | push end of time 720p.42125C | 0042010A | push edi | 0042010B | call dword ptr ds:[<&gdi32.ChoosePixelFormat>] | 00420111 | push eax | 00420112 | push edi | 00420113 | call dword ptr ds:[<&gdi32.SetPixelFormat>] | 00420119 | call dword ptr ds:[<&opengl32.wglCreateContext>] | 0042011F | push eax | 00420120 | push edi | 00420121 | call dword ptr ds:[<&opengl32.wglMakeCurrent>] | 00420127 | call dword ptr ds:[<&user32.ShowCursor>] | 0042012D | call end of time 720p.4202CC | --- snip --- The demoscene guys are crazy and fight for each saved byte ;-) Courtesy of: http://www.pouet.net/topic.php?which=9894 --- quote --- I was able to get 4 bytes off of a test 1k intro (Peach GLSL Shader of Japan) by replacing the "edit" string with 0xC018, making it 1006 bytes instead of 1010. Nice. ...and then I got it down to 1004 bytes, because now "test eax, eax" compressed better than "test ax, ax", which used to compress better sometime before this newest change. ;) This 1k intro business is crazy, you'd really need some kind of brute-force code masher that tries all possible combinations of code that perform the same thing. --- quote --- --- quote --- That´s mine since 2009 using DirectX9...someone told me using "static" instead of "edit" would be better back then in some other thread...was iq if i remember correctly. The ATOM for "static" is 0xC019 btw, but be warned: it added 7 bytes here in my first test, opposed to chopping off 4 bytes in case of "edit". --- quote --- --- quote --- Oh, shit...i did the test the wrong way around...meaning the ATOM actually chopped off 7 bytes in case of "static" vs. "0xC019" :/ :D Yay, thanks for the nice trick, man! :) --- quote --- Also relevant, shows dump of global and typical local atom tables: https://github.com/lungetech/ICAS/blob/master/logs/volatility/win32/output/… Wine source: https://source.winehq.org/git/wine.git/blob/9e26bc811656ad8eb901bffa5528b9c… --- snip --- 407 /*********************************************************************** 408 * CLASS_FindClass 409 * 410 * Return a pointer to the class. 411 */ 412 static CLASS *CLASS_FindClass( LPCWSTR name, HINSTANCE hinstance ) 413 { 414 static const WCHAR comctl32W[] = {'c','o','m','c','t','l','3','2','.','d','l','l',0}; 415 struct list *ptr; 416 ATOM atom = get_int_atom_value( name ); 417 418 GetDesktopWindow(); /* create the desktop window to trigger builtin class registration */ 419 420 if (!name) return NULL; 421 422 name = CLASS_GetVersionedName( name, NULL, NULL, TRUE ); 423 424 for (;;) 425 { 426 USER_Lock(); 427 428 LIST_FOR_EACH( ptr, &class_list ) 429 { 430 CLASS *class = LIST_ENTRY( ptr, CLASS, entry ); 431 if (atom) 432 { 433 if (class->atomName != atom) continue; 434 } 435 else 436 { 437 if (strcmpiW( class->name, name )) continue; 438 } 439 if (!class->local || class->hInstance == hinstance) 440 { 441 TRACE("%s %p -> %p\n", debugstr_w(name), hinstance, class); 442 return class; 443 } 444 } 445 USER_Unlock(); 446 447 if (atom) break; 448 if (!is_comctl32_class( name )) break; 449 if (GetModuleHandleW( comctl32W )) break; 450 if (!LoadLibraryW( comctl32W )) break; 451 TRACE( "%s retrying after loading comctl32\n", debugstr_w(name) ); 452 } 453 454 TRACE("%s %p -> not found\n", debugstr_w(name), hinstance); 455 return NULL; 456 } --- snip --- https://source.winehq.org/git/wine.git/blob/9e26bc811656ad8eb901bffa5528b9c… $ sha1sum atz-end_of_time.zip 3a4ce3fd92e2fdd1a4533ee67d4809d3f2184f6b atz-end_of_time.zip $ du -sh atz-end_of_time.zip 3.3M atz-end_of_time.zip $ wine --version wine-5.8-173-g9e26bc8116 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.

1 7

[Bug 55548] New: kernel32:power - test_GetSystemPowerStatus() fails on macOS
by WineHQ Bugzilla 11 Dec '23

11 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=55548 Bug ID: 55548 Summary: kernel32:power - test_GetSystemPowerStatus() fails on macOS Product: Wine Version: unspecified Hardware: x86-64 OS: Mac OS X Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com kernel32:power - test_GetSystemPowerStatus() fails on macOS: power.c:34: Test failed: expected TRUE See https://test.winehq.org/data/patterns.html#kernel32:power The failure is systematic and only happens macOS (see Remi's rbernon-macos-* cloud test machines). It looks like the macOS implementation of fill_battery_state() fails, presumably because of permission issues. -- 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 55965] New: Divide by zero error with Trackmania 2020 when loading tracks [D3DMetal]
by WineHQ Bugzilla 11 Dec '23

11 Dec '23

https://bugs.winehq.org/show_bug.cgi?id=55965 Bug ID: 55965 Summary: Divide by zero error with Trackmania 2020 when loading tracks [D3DMetal] Product: Wine Version: unspecified Hardware: arm OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: omgloldave(a)gmail.com Created attachment 75555 --> https://bugs.winehq.org/attachment.cgi?id=75555 backtrace log of game crashing when loading into a game. Hi all, bit at a loss on where exactly to report this. I'm trying here first and if it's not a problem with wine itself, please tell me where to poke exactly. So Trackmania 2020 has a rather weird error when it comes to using Apples new GPTK layer. The game works amazingly... in the editor. You can load tracks and drive them (with pretty remarkable quality). However, when you load a track or join a server, the game crashes with a divide by zero error. Additionally, in the editor, some graphical elements are weird (i.e, some trees are not rendering, weird blown out textures etc) and you can't render the track (aka "calculate shadows"). Luckily TM2020 is free to play to recreate this. Just open the game and try to load any track. You can also recreate the editor weirdness by using the scenery blocks. I have used Whisky, Crossover (where this error log comes from), PortingKit and vanilla wine and each yields the same results with various versions (all released within the last 4-5 months). There's a bug report on Whisky on this issue that's flagged specifically as an issue with wine (also I posted a comment with no response: https://github.com/Whisky-App/Whisky/issues/235). I currently use Parallels to play (which works fine, of course using a different method of emulation), but with the new GPTK update the performance increase is apparently massive, so it would be nice to see this fixed. I'm not going to make this harder by guessing, as I am not super technical with Wine. However looking at the backtrace and just glancing at the error-log I think the problem is down to Wine's interaction with GPTK/D3DMetal, or with GPTK/D3D/Apple itself. Weirdly, I don't *think* this is a WINE bug necessarily, TM2020 is my favourite game, so more than anything I kinda want to know *where* exactly to report this error in detail if not here. Plus I want someone far more well versed than me to explain how to report this bug. Is this an Apple issue or a WINE issue or a skill issue? Thanks for your help and all your hard work! -- 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 12

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