December 2020 - Wine-bugs - list.winehq.org

[Bug 48734] New: How to Survive crashes when starting a new game
by WineHQ Bugzilla 16 Apr '23

16 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=48734 Bug ID: 48734 Summary: How to Survive crashes when starting a new game Product: Wine Version: 5.0-rc1 Hardware: x86 URL: https://store.steampowered.com/app/250400/How_to_Survi ve/ OS: Linux Status: NEW Keywords: regression Severity: normal Priority: P2 Component: quartz Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com CC: z.figura12(a)gmail.com Regression SHA1: 94822bae5fed8a3bbda00adb4e79652cd9374309 Distribution: --- Created attachment 66616 --> https://bugs.winehq.org/attachment.cgi?id=66616 terminal output The game was started in windowed mode to work around bug #48732. When I start a new single-player game from the menu, Wine crashes when attempting to play the first video. I think it's 'prologue.avi' which should be playing at this point. Cutscenes didn't work properly before the regression, only a black screen was shown and pressing <Space> or <Esc> made it possible to skip the video. Now Wine crashes. The crash was introduced by commit 94822bae5fed8a3bbda00adb4e79652cd9374309 quartz/vmr9: Create the rendering window when the filter is created. To reproduce the problem select <Local Game> in the main menu, then <Story Mode>, <1 Player>, choose a character and difficulty level. After a short loading animation Wine crashes. Tested in wine-5.3-181-geb63713f60. -- 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 49332] New: CounterPath Bria Solo crashes after login dialog
by WineHQ Bugzilla 14 Apr '23

14 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=49332 Bug ID: 49332 Summary: CounterPath Bria Solo crashes after login dialog Product: Wine Version: 5.10 Hardware: x86 URL: https://www.counterpath.com/bria-solo/ OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: setupapi Assignee: wine-bugs(a)winehq.org Reporter: whydoubt(a)gmail.com Distribution: Fedora After getting past the login dialog, the program crashes almost immediately. It does pop up a dialog that offers to submit logs to the developers. I have not found any logs produced by the software that provide insight into what caused the crash. However, after turning on several debug channels in wine, I found this right before things go sideways: 0024:trace:nls:FormatMessageW (0x1300,00000000,0xe000020e,0x400,0031E634,1,00000000) I tracked down the 0xe000020e error code in this case as coming from SetupDiDestroyDeviceInfoList, even though the call had completed successfully. -- 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 32490] New: Graphical issues in Inquisitor (red squares painted on the screen)
by wine-bugs＠winehq.org 14 Apr '23

14 Apr '23

http://bugs.winehq.org/show_bug.cgi?id=32490 Bug #: 32490 Summary: Graphical issues in Inquisitor (red squares painted on the screen) Product: Wine Version: 1.5.19 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: gyebro69(a)gmail.com Classification: Unclassified Created attachment 42861 --> http://bugs.winehq.org/attachment.cgi?id=42861 terminal output Inquisitor is an RPG released in 2012. I guess it uses DirectX8 (or DX7?) because only +d3d8 produces output, not +d3d9. Red squares are present on the screen while in the menus as well as in the main game. This makes the game unplayable. I tested this bug with a Nvidia gfx card: both the open source Nouveau and the binary drivers show the same problem. Wine 1.2.3, 1.4.1, 1.5.19 etc. have the reported problem. No demo available. Let me know if you need a debug log. -- 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 38

[Bug 28586] New: Team Fortress Arcade and Pixel Force: Left 4 Dead have no sound
by wine-bugs＠winehq.org 14 Apr '23

14 Apr '23

http://bugs.winehq.org/show_bug.cgi?id=28586 Bug #: 28586 Summary: Team Fortress Arcade and Pixel Force: Left 4 Dead have no sound Product: Wine Version: 1.3.29 Platform: All OS/Version: All Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-dmusic AssignedTo: wine-bugs(a)winehq.org ReportedBy: sagman.staredsi(a)gmail.com Classification: Unclassified Created attachment 36730 --> http://bugs.winehq.org/attachment.cgi?id=36730 Full Team Fortress Arcade log Team Fortress Arcade and Pixel Force: Left 4 Dead have no sound due a unimplemented function of directmusic: fixme:dmfile:IDirectMusicSegment8Impl_IPersistStream_Load : WAVE form (loading to be checked) fixme:dswave:IDirectMusicWaveImpl_IPersistStream_Load (0x5f148e8, 0x5f148b8): loading not implemented yet (only descriptor is loaded) This two lines are a message that wine repeat often in the output and inform this. -- 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 20

[Bug 42372] New: Watchtower Library 2016, program crashes when trying to play a video from within the program
by wine-bugs＠winehq.org 14 Apr '23

14 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=42372 Bug ID: 42372 Summary: Watchtower Library 2016, program crashes when trying to play a video from within the program Product: Wine Version: 2.0 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: drctheboss(a)charter.net Distribution: --- Created attachment 57155 --> https://bugs.winehq.org/attachment.cgi?id=57155 when the program crashed this was generated All aspects of the program seem to work fine, except when attempting to play a video. Then the program will crash and wine will generate a backtrace report -- 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 40

[Bug 18773] New: The Westerner: needs MPEG Layer-3 audio codec
by wine-bugs＠winehq.org 14 Apr '23

14 Apr '23

http://bugs.winehq.org/show_bug.cgi?id=18773 Summary: The Westerner: needs MPEG Layer-3 audio codec Product: Wine Version: 1.1.22 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: winmm&mci AssignedTo: wine-bugs(a)winehq.org ReportedBy: hoehle(a)users.sourceforge.net The Westerner until now had garbage AppDB rating but no bug entry. Deselecting any audio driver in winecfg let's wine play the intro and crash after: err:ole:CoGetClassObject class {38be3000-dbf4-11d0-860e-00a024cfef6d} not registered err:ole:CoGetClassObject no class object {38be3000-dbf4-11d0-860e-00a024cfef6d} could be created for context 0x1 This UUID is the "FriendlyName"="MPEG Layer-3 Decoder" from DirectX9 windows\system32\l3codecx.ax As Wine has its own winemp3.acm, shouldn't it declare this UUID (e.g. via tools/wine.inf)? Is this a simple omission? Does winemp3 implement something entirely different, another win API? When audio is not disabled in winecfg, wine crashes after repeatedly (~13x) opening and closing all winmm codecs, including winemp3.acm (it does not manage to reach the intro). wine regsvr32 l3codecx.ax WINEDLLOVERRIDES=quartz=n wine PICTuRE.exe is what's needed to let the music play, to see the intro, to start gameplay and to bump the AppDB rating from garbage to bronze. (Likely gold except for serious mouse lag, which is another issue.) The loop mentioned above is then avoided, as a driver is found. The native quartz.dll is needed or it won't find some pin (later than the intro). I copied the l3codecx.ax from a separate winetricks DirectX9 install before noticing that The Westerner's CD-ROM also contains it in DirectX9\DirectX.cab. Oddly, the application's cover lists only DirectX 8.1 as requirement. Using The Westerner German Patch v1.3. I guess v1.0 (CD-ROM without patch) would behave the same (guessing from reports in AppDB). -- 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 25

[Bug 25495] New: Homeworld 2: Shadows and High-Quality Hyperspace Effect are disabled
by wine-bugs＠winehq.org 12 Apr '23

12 Apr '23

http://bugs.winehq.org/show_bug.cgi?id=25495 Summary: Homeworld 2: Shadows and High-Quality Hyperspace Effect are disabled Product: Wine Version: 1.3.7 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: megatog615(a)gmail.com Even with the Shadows and High-Quality Hyperspace Effect enabled through the options menu in Homeworld 2, either effect is not seen in the actual gameplay. >From some research via Google, it appears both effects use the stencil capabilities of the graphics driver. I'm assuming the game is failing to detect the correct capabilities of the graphics card. -- 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 26

[Bug 33192] New: Characters in Granado Espada not visible
by wine-bugs＠winehq.org 12 Apr '23

12 Apr '23

http://bugs.winehq.org/show_bug.cgi?id=33192 Bug #: 33192 Summary: Characters in Granado Espada not visible Product: Wine Version: 1.5.25 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: rndbit(a)nm.ru Classification: Unclassified Created attachment 43911 --> http://bugs.winehq.org/attachment.cgi?id=43911 Visual explanation So game works flawlessly except for models somehow not being attached to animations. I uploaded screenshot that illustrates issue. 1. As you can see models of all static actors are pisitioned in center of loaded level. 2. Spots where NPCs should stand are empty, however 'invisible' npcs are clickable at spot above their name, just where npc body should be. 3. Player characters also can not be seen. Items carried by characters (and NPCs) are rendered properly. Gear moves according to animation. Terminal log: String Dictionary Loading Start String Dictionary Loading Success fixme:win:EnumDisplayDevicesW ((null),0,0x32ef04,0x00000000), stub! fixme:winediag:AUDDRV_GetAudioEndpoint Winepulse is not officially supported by the wine project fixme:winediag:AUDDRV_GetAudioEndpoint For sound related feedback and support, please visit http://ubuntuforums.org/showthread.php?t=1960599 fixme:d3d9:Direct3DShaderValidatorCreate9 stub fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:imm:ImmGetOpenStatus (0xcf077a8): semi-stub fixme:imm:ImmReleaseContext (0xa0062, 0xcf077a8): stub fixme:ras:RasEnumConnectionsW (0x1333e8,0x326af0,0x76c623e4),stub! fixme:ras:RasEnumConnectionsW RAS support is not implemented! Configure program to use LAN connection/winsock instead! fixme:service:EnumServicesStatusW resume handle not supported fixme:ras:RasEnumEntriesW ((nil),(null),0xcffb108,0x327320,0xcffadf4),stub! fixme:wmvcore:WMCreateSyncReader ((nil), 0, 0xd17ef28): stub fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:wined3d_buffer_preload Too many declaration changes or converting dynamic buffer, stopping converting fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:wined3d_buffer_preload Too many declaration changes or converting dynamic buffer, stopping converting fixme:win:GetWindowPlacement not supported on other process window 0x20028 <...> fixme:win:GetWindowPlacement not supported on other process window 0x20028 <...> fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:wmvcore:WMCreateSyncReader ((nil), 0, 0x193d8048): stub fixme:d3d:resource_check_usage Unhandled usage flags 0x8. <...> fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:win:GetWindowPlacement not supported on other process window 0x20028 fixme:d3d:resource_check_usage Unhandled usage flags 0x8. <...> fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:win:GetWindowPlacement not supported on other process window 0x20028 fixme:d3d:resource_check_usage Unhandled usage flags 0x8. <...> fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:win:GetWindowPlacement not supported on other process window 0x20028 fixme:d3d:resource_check_usage Unhandled usage flags 0x8. <...> fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:win:GetWindowPlacement not supported on other process window 0x20028 <...> fixme:win:GetWindowPlacement not supported on other process window 0x20028 I replaced multiple same messages with <...> for improved readability. Forum thread: http://forum.winehq.org/viewtopic.php?f=2&t=18485 -- 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 9

[Bug 46970] New: call of duty world war II crash on start
by wine-bugs＠winehq.org 08 Apr '23

08 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=46970 Bug ID: 46970 Summary: call of duty world war II crash on start Product: Wine Version: 4.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mathieu.schmitt68(a)orange.fr Distribution: --- Created attachment 64125 --> https://bugs.winehq.org/attachment.cgi?id=64125 backtrace-callofdutyw2 i use Ubuntu 18.10 and wine 4.5, DXVK 1.0.2 i start the game from steam and the game crash. i don't see any splash screen or main menu. (backtrace.txt) i start the game from the command line. i can't generate a back-trace file from the command line i see : 0009:fixme:heap:RtlSetHeapInformation 0x4b0000 0 0x22e740 4 stub wine: Unhandled exception 0xc0000409 in thread 29 at address 0x140057490 (thread 0029), starting debugger... 002c:fixme:dbghelp:elf_search_auxv can't find symbol in module (40x) Regards Mathieu -- 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 6

[Bug 45068] New: Patches page sorting by Reviewer, Sign, Testbot and Job ID broken
by wine-bugs＠winehq.org 08 Apr '23

08 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=45068 Bug ID: 45068 Summary: Patches page sorting by Reviewer, Sign, Testbot and Job ID broken Product: WineHQ.org Version: unspecified Hardware: x86-64 URL: https://source.winehq.org/patches/ OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: www-unknown Assignee: wine-bugs(a)winehq.org Reporter: gijsvrm(a)gmail.com URL: https://source.winehq.org/patches/ Script location: https://source.winehq.org/git/tools.git/blob/HEAD:/patches/update Clicking on 'Reviewer', 'Sign', 'Testbot' or 'Job ID' doesn't result in the desired sorting. This used to work before. I would run a regression test, but I'm not sure how to work with the patches/update script. IMO the desired sorting would be: - 'Reviewer': First by name, then by patch ID - 'Sign': First by the number of signs, then by patch ID - 'Testbot': First by status, then by patch ID - 'Job ID': First by job number (if there is one), then by patch ID If I recall correctly, this is how it was before. This was probably broken when the patches list was adapted to cope with the merging of wine-devel and wine-patches. I can attach screenshots if necessary. -- 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