August 2023 - Wine-bugs - list.winehq.org

[Bug 39597] New: Amstream demo application fails to play video file
by wine-bugs＠winehq.org 05 May '24

05 May '24

https://bugs.winehq.org/show_bug.cgi?id=39597 Bug ID: 39597 Summary: Amstream demo application fails to play video file Product: Wine Version: 1.7.55 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: amstream Assignee: wine-bugs(a)winehq.org Reporter: bunglehead(a)gmail.com Distribution: --- Created attachment 52762 --> https://bugs.winehq.org/attachment.cgi?id=52762 demo application sources, binary Follow up after first thing from bug 8712 is fixed, but application still doesn't 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.

2 19

[Bug 44260] New: Dungeon Keeper 2 crashs or works very slow
by wine-bugs＠winehq.org 05 May '24

05 May '24

https://bugs.winehq.org/show_bug.cgi?id=44260 Bug ID: 44260 Summary: Dungeon Keeper 2 crashs or works very slow Product: Wine Version: 3.0-rc1 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: rtentser(a)yandex.ru Distribution: --- Created attachment 60067 --> https://bugs.winehq.org/attachment.cgi?id=60067 3.0-rc1_DKII-DX.EXE When i try to start the game with DKII-DX.EXE it starts but very slow. When i use DKII.EXE it crashs. Same with DKII_SOFT.EXE. I also tried the game with 2.0.3. DKII-DX.EXE works the same way. DKII.EXE starts and works a little faster (i think so) but too slow still. DKII-SOFT.EXE starts and works fine. In 1.8.7 DKII-DX.EXE crashs when loading after movies. I use the GOG version of the game. And i use old NVIDIA card (GeForce2 MX/MX 400), so that can be a problem. Or not. I'm not sure. The attachment is the output of 3.0-rc1 with DKII-DX.EXE. I also check if my issue is duplicate of https://bugs.winehq.org/show_bug.cgi?id=22730. No, it's not: i have a low fps not only in the main menu, but in the game 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.

2 12

[Bug 28933] New: Screamer radio, mainmenu doesn't work
by wine-bugs＠winehq.org 05 May '24

05 May '24

http://bugs.winehq.org/show_bug.cgi?id=28933 Bug #: 28933 Summary: Screamer radio, mainmenu doesn't work Product: Wine Version: 1.3.31 Platform: x86 URL: http://www.screamer-radio.com/download/file/screamer04 4.exe OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: ocean04(a)suomi24.fi Classification: Unclassified Mainmenu doesn't work at all, totally unresponsive. -- 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 33

[Bug 41712] New: lto build is broken
by wine-bugs＠winehq.org 04 May '24

04 May '24

https://bugs.winehq.org/show_bug.cgi?id=41712 Bug ID: 41712 Summary: lto build is broken Product: Wine Version: 1.9.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: build-env Assignee: wine-bugs(a)winehq.org Reporter: hi-angel(a)yandex.ru Distribution: --- Compiling WINE with "-flto" in LDFLAGS breaks the build for link-time. The problem boils down to the following minimal example: $ cat main.c void foo(); int main() { foo(); } $ cat foo.c void foo() { } $ winegcc -c -flto foo.c $ winegcc main.c foo.o /usr/lib/wine/libwinecrt0.a(exe_entry.o): In function `__wine_spec_exe_entry': (.text+0x8d): undefined reference to `ExitProcess' /usr/bin/ld: a.out.so: hidden symbol `ExitProcess' isn't defined /usr/bin/ld: final link failed: Bad value collect2: error: ld returned 1 exit status winegcc: gcc failed Simply removing the "-flto" option from the steps fixes the build. -- 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 48402] New: Harry Potter: Quidditch World Cup installer doesn't show the progress
by WineHQ Bugzilla 04 May '24

04 May '24

https://bugs.winehq.org/show_bug.cgi?id=48402 Bug ID: 48402 Summary: Harry Potter: Quidditch World Cup installer doesn't show the progress Product: Wine Version: 5.0-rc3 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: oleg.kuznetsov(a)metamint.ru Distribution: --- Created attachment 66174 --> https://bugs.winehq.org/attachment.cgi?id=66174 log during the installation During installation of Harry Potter: Quidditch World Cup, the installer doesn't show progress neither in percents, nor in form of the progress bar. On real Windows Vista, it is being shown as it should. WINEARCH=win32 WINEPREFIX=~/.wine_hp ./wine winecfg Prefix was set to "Vista". WINEPREFIX=~/.wine_hp/ ./wine start /unix /media/desktop/HPQ_E3/AutoRun.exe &> ~/HPQWC_install.log I closed the installer near the end of the installation, because it was starting up the game. desktop(a)steamos:~/Code/wine$ ./wine --version wine-5.0-rc3-11-g6e4d441 -- 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 49423] New: Added input lag in World of Warcraft and other games
by WineHQ Bugzilla 04 May '24

04 May '24

https://bugs.winehq.org/show_bug.cgi?id=49423 Bug ID: 49423 Summary: Added input lag in World of Warcraft and other games Product: Wine Version: 4.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bloodyiron(a)lanified.com Distribution: --- In World of Warcraft you use WASDQE to move your character in the world in a very highly responsive manner. When using WINE 4.16, there is no perceptible input lag. However, switching to WINE 4.17 or higher (verified in 5.7 also), there is immediately perceptible input lag. Namely, in a combination of dropped/missed inputs and delayed response to inputs the game receives. This seems to be reproducible 100% of the time based on my experience and generally everyone else I've asked, or read comments on the topic. This input lag is so bad it means World of Warcraft should not be played on any version higher than WINE 4.16 until this input lag bug is fixed, as it makes gameplay elements (complex boss fights) nearly impossible. -- 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 31245] New: xrandr12 warcraft 3 regression
by wine-bugs＠winehq.org 04 May '24

04 May '24

http://bugs.winehq.org/show_bug.cgi?id=31245 Bug #: 31245 Summary: xrandr12 warcraft 3 regression Product: Wine Version: 1.5.9 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv AssignedTo: wine-bugs(a)winehq.org ReportedBy: asdfrewq(a)mail.ru Classification: Unclassified When i trying to change screen resolution in Warcraft 3 options, it show me confirmation window "All ok, do you realy want to save this resolution", but realy nothing happens, resolution does not change. This is printed to stdout: fixme:win:EnumDisplayDevicesW ((null),0,0x33f354,0x00000000), stub! err:xrandr:xrandr12_set_current_mode Resolution change not successful -- perhaps display has changed? In wine 1.5.8 all was ok. -- 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 36

[Bug 48565] New: When entering fullscreen at lower resolution than the desktop, scrollable virtual desktop is accessible
by WineHQ Bugzilla 04 May '24

04 May '24

https://bugs.winehq.org/show_bug.cgi?id=48565 Bug ID: 48565 Summary: When entering fullscreen at lower resolution than the desktop, scrollable virtual desktop is accessible Product: Wine Version: 5.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dmayr.dev(a)gmail.com Distribution: --- I tried playing a DirectX-based game, e.g. GTAIV, using the emulated virtual desktop at 800x600 (my desktop's native resolution is 1440x900). But ever since I changed back to playing the game fullscreen at 800x600 *without the virtual desktop*, the following happens: - The game starts at the desired lower resolution - Part of my desktop environment's panel is visible within the game's viewport, at that same lower resolution - If I move the mouse far enough, I realize that there's an active 1440x900 virtual desktop, showing me a lo-res 800x600 window - I can scroll around the edges of this virtual desktop, thus Wine losing the captured mouse cursor - When playing, this moves the centered game view past the center of the screen, losing focus; this prevents the mouse cursor's movements to be confined within the fullscreen window, which is supposed to be the an immovable viewport. I haven't found a way to revert back from having tried the virtual desktop option, as the change has been somehow been made permanent. -- 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 50553] New: SetEnvironmentVariableW function sets last error on deleting non-existent variable
by WineHQ Bugzilla 04 May '24

04 May '24

https://bugs.winehq.org/show_bug.cgi?id=50553 Bug ID: 50553 Summary: SetEnvironmentVariableW function sets last error on deleting non-existent variable Product: Wine Version: 6.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: topin89(a)mail.ru Distribution: --- This code ``` //gcc test.c -o test.exe && ./test.exe #include <windows.h> #include <stdio.h> int main(int argc, char *argv[]){ BOOL result; result = SetEnvironmentVariableW(L"PERL5LIB", NULL); printf("result: %u, last error: %d\n", result, GetLastError()); SetLastError(0); result = SetEnvironmentVariableW(L"PERL5LIB", "SomeValue"); printf("result: %u, last error: %d\n", result, GetLastError()); SetLastError(0); result = SetEnvironmentVariableW(L"PERL5LIB", NULL); printf("result: %u, last error: %d\n", result, GetLastError()); SetLastError(0); result = SetEnvironmentVariableW(L"PERL5LIB", NULL); printf("result: %u, last error: %d\n", result, GetLastError()); SetLastError(0); return 0; } ``` compiled with Mingw-w64 gcc and running from command line and MSYS console gives this in Windows 10: ``` result: 1, last error: 0 result: 1, last error: 0 result: 1, last error: 0 result: 1, last error: 0 ``` and this in Kubuntu 20.04.1 with winehq-staging 6.0: ``` <snip fixmes> result: 0, last error: 203 result: 1, last error: 0 result: 1, last error: 0 result: 0, last error: 203 ``` Error 203 is ERROR_ENVVAR_NOT_FOUND, btw. So, in Win 10 deleting already deleted environmental variable doesn't lead to error, in Wine it is. This alone prevents git.exe (and probably many more apps) to work correctly. In file git-for-windows-repo/compat/mingw.c there is this function, ``` int mingw_putenv(const char *namevalue) { int size; wchar_t *wide, *equal; BOOL result; if (!namevalue || !*namevalue) return 0; size = strlen(namevalue) * 2 + 1; wide = calloc(size, sizeof(wchar_t)); if (!wide) die("Out of memory, (tried to allocate %u wchar_t's)", size); xutftowcs(wide, namevalue, size); equal = wcschr(wide, L'='); if (!equal) result = SetEnvironmentVariableW(wide, NULL); else { *equal = L'\0'; result = SetEnvironmentVariableW(wide, equal + 1); } free(wide); if (!result) errno = err_win_to_posix(GetLastError()); return result ? 0 : -1; } ``` This line : ``` result = SetEnvironmentVariableW(wide, NULL); ``` sets error on removing non-existent `PERL5LIB` and that leads to result == 0 which in turn leads to premature exit in `err_win_to_posix(GetLastError())`. In this particular case, for some reason last error sets to 0 instead of 203. Another bug probably, I'll report it later. -- 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 13198] New: Microsoft Pinball Arcade black/blank window in 24bpp mode
by wine-bugs＠winehq.org 04 May '24

04 May '24

http://bugs.winehq.org/show_bug.cgi?id=13198 Summary: Microsoft Pinball Arcade black/blank window in 24bpp mode Product: Wine Version: 1.0-rc1 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: vanessaezekowitz(a)gmail.com Created an attachment (id=13030) --> (http://bugs.winehq.org/attachment.cgi?id=13030) Screenshot of real 8bpp mode Microsoft Pinball Arcade (commercial/full version) doesn't work properly in WINE if you're using a regular, standard-issue 24bpp X session. Intro/menu screens work, but the 3D content (direct3d? ddraw?) just produces a black screen. Steps to reproduce: 0. Obtain a copy of the game (maybe the demo version will do?). cd into your 'drive c' directory and start the game: `wine Program\ Files/Microsoft\ Games/Pinball\ Arcade/Launcher.exe` 1. A movie displays showing a closeup of one of the game's tables. 2. Click on the movie to interrupt it. The title screen appears and looks fine. 3. Click again, table select menu appears and waits for input. 4. Click on any menu item at the bottom of the window - a dialog related to it appears as it should. 5. Double-click on one of the tables - the table selection screen gets blacked out, the window resizes, and the table's loading screen appears all in the same instant - without repainting the window - the loading screen only painted on the parts of the window that were already black. So we have a window half filled with the loading screen and half transparent, showing this browser and the controlling terminal through it. 6. The loading screen disappears and the window turns solid black. A windows pointer appears. On the console, the "Cannot change screen BPP" line appears. 7. Clicking around eventually causes the pointer to disappear, probably because I managed to trigger the insert-coin hot spot followed by the "1 player" hotspot, thus starting the actual game. Hitting Esc is supposed to bring up a graphical exit/no-exit dialog, but nothing appears. Blindly hitting "y" puts me back at the table-select screen as it should. So the actual game is accepting input, it just isn't showing me anything. 7a. If I try another table, I get the exact same result, including another "Cannot change screen BPP" line on the console. 8. Double-click the table-select menu's internal Exit button and Wine drops back to my shell after a couple of seconds. Actual Results: Described above - I get a black window instead of a game table. Expected Results: Wine should have displayed the table properly and let me play the game. Notes: In order to run this game properly, the user *must* have a true 8bpp mode with StaticColor visual defined in their xorg.conf, and the user *must* manually run a second, separate X screen (e.g. one accessible with Ctrl-Alt-F8) in that more with that visual. Desipte having a known, tested, working 8bpp mode in xorg.conf, Xorg does not have any kind of ability to switch away from the currently-running depth to some other mode (e.g. it cannot and never will be able to drop from 24bpp to 8bpp), and is not expected to ever have such a feature. Furthermore, some users' hardware does not have the ability to run in true 8bpp mode at all, so this game simply *will not work* on those systems. ply does not work on some hardware, despite having correct software settings. The attached screenshot shows what the game looks like in reap 8bpp "StaticColor" mode, using twm as a window manager (it looks the same without a window manager). Versions affected: All WINE versions from roughly 0.9.31 through the current 1.0 rc1 release. -- 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 29