October 2019 - Wine-bugs - list.winehq.org

[Bug 47789] New: Gameforge Client: Initialization fails due to SparkWebHelper.exe crashing
by WineHQ Bugzilla 10 Oct '19

10 Oct '19

https://bugs.winehq.org/show_bug.cgi?id=47789 Bug ID: 47789 Summary: Gameforge Client: Initialization fails due to SparkWebHelper.exe crashing Product: Wine Version: 4.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: sickam(a)mail.ru Distribution: --- Created attachment 65278 --> https://bugs.winehq.org/attachment.cgi?id=65278 Wine's terminal output Hello everyone, as in the summary stated the Gameforge Client fails to initialize due to SparkWebHelper.exe crashing. I can click a "retry" symbol in the launcher afterwards, but it keeps failing again and again. You can find a terminal output and a backtrace in the attachments. My system: OS: Gentoo uname -a: Linux gen2 5.2.16-gentoo #1 SMP Sat Sep 21 14:14:44 CEST 2019 x86_64 AMD Ryzen 7 1800X Eight-Core Processor AuthenticAMD GNU/Linux GPU: AMD Vega 56 Window server: xorg-server-1.20.5 Window manager: i3-4.17.1 Mesa: mesa-19.2.0_rc4 LLVM: llvm-9.0.0 Download to the Gameforge Client: https://gameforge.com/en-US/download -- 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 47503] New: Problems with CreateProcess(CREATE_SUSPENDED) and later ResumeThread
by wine-bugs＠winehq.org 09 Oct '19

09 Oct '19

https://bugs.winehq.org/show_bug.cgi?id=47503 Bug ID: 47503 Summary: Problems with CreateProcess(CREATE_SUSPENDED) and later ResumeThread Product: Wine Version: 4.0.1 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: ghotik2002(a)yahoo.com Distribution: --- I'm trying to port DxWnd ( https://sourceforge.net/p/dxwnd ) on Wine and it runs pretty out of the box for injection based on SetWindowsHook calls, but in many cases it is necessary to use code injection based on thread suspension / resume. An injection mode uses CreateProcess(CREATE_SUSPENDED) and some later ResumeThread call, but the result is an alive process (I can list it with Linux ps command) that is probably still suspended and can't take control of the desktop. If anyone may want to replicate the test, he/she may contact me on SourceForge DxWnd dedicated forum or write me at ghotik2002(a)yahoo.com. -- 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

[Bug 47913] New: Canon driver crashes on install
by WineHQ Bugzilla 09 Oct '19

09 Oct '19

https://bugs.winehq.org/show_bug.cgi?id=47913 Bug ID: 47913 Summary: Canon driver crashes on install Product: Wine Version: 4.0.2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winelib Assignee: wine-bugs(a)winehq.org Reporter: rebrown01(a)gmail.com Distribution: --- Created attachment 65408 --> https://bugs.winehq.org/attachment.cgi?id=65408 Backtrace file for canon driver installation Canon driver MP Navigator 3.0.6 EX crashes on install file mpnx_3_0-win-3_06-ea23_2.exe ubuntu 18.04.3 Wine 4.0.2 4.15.0-64-generic -- 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 47914] New: winecfg: many ALSA devices are missing from the device list
by WineHQ Bugzilla 09 Oct '19

09 Oct '19

https://bugs.winehq.org/show_bug.cgi?id=47914 Bug ID: 47914 Summary: winecfg: many ALSA devices are missing from the device list 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: forestcode(a)ixio.org Distribution: --- winecfg lists only a small subset of the ALSA devices on my system, and the one I need for surround playback is not among them. This is an ALSA-only system. PulseAudio is not installed. Ubuntu 19.04, x86_64, wine-4.17 (Staging) from the winehq repo. Running aplay -L shows dozens of output devices, including these: default:CARD=Audigy2 SB Audigy 5/Rx [SB1550], ADC Capture/Standard PCM Playback Default Audio Device sysdefault:CARD=Audigy2 SB Audigy 5/Rx [SB1550], ADC Capture/Standard PCM Playback Default Audio Device front:CARD=Audigy2,DEV=0 SB Audigy 5/Rx [SB1550], ADC Capture/Standard PCM Playback Front speakers rear:CARD=Audigy2,DEV=0 SB Audigy 5/Rx [SB1550], ADC Capture/Standard PCM Playback Rear speakers center_lfe:CARD=Audigy2,DEV=0 SB Audigy 5/Rx [SB1550], ADC Capture/Standard PCM Playback Center and Subwoofer speakers side:CARD=Audigy2,DEV=0 SB Audigy 5/Rx [SB1550], ADC Capture/Standard PCM Playback Side speakers surround21:CARD=Audigy2,DEV=0 SB Audigy 5/Rx [SB1550], ADC Capture/Standard PCM Playback 2.1 Surround output to Front and Subwoofer speakers surround40:CARD=Audigy2,DEV=0 SB Audigy 5/Rx [SB1550], ADC Capture/Standard PCM Playback 4.0 Surround output to Front and Rear speakers surround41:CARD=Audigy2,DEV=0 SB Audigy 5/Rx [SB1550], ADC Capture/Standard PCM Playback 4.1 Surround output to Front, Rear and Subwoofer speakers surround50:CARD=Audigy2,DEV=0 SB Audigy 5/Rx [SB1550], ADC Capture/Standard PCM Playback 5.0 Surround output to Front, Center and Rear speakers surround51:CARD=Audigy2,DEV=0 SB Audigy 5/Rx [SB1550], ADC Capture/Standard PCM Playback 5.1 Surround output to Front, Center, Rear and Subwoofer speakers surround71:CARD=Audigy2,DEV=0 SB Audigy 5/Rx [SB1550], ADC Capture/Standard PCM Playback 7.1 Surround output to Front, Center, Side, Rear and Woofer speakers The closest match for any of those that appears in winecfg is: Out: SB Audigy 5/Rx [SB1550], ADC Capture/Standard PCM Playback As you can see, that is not useful, since there are a dozen different devices with that same description. winecfg gives me no indication of which actual device it is referring to, and no way to select the one I need. Could it be that wine is skipping any device that has the same description as one that it already enumerated? -- 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 45702] New: World of Final Fantasy crashes with page fault on read access to 0x0 at address (0x1409b111f)
by wine-bugs＠winehq.org 08 Oct '19

08 Oct '19

https://bugs.winehq.org/show_bug.cgi?id=45702 Bug ID: 45702 Summary: World of Final Fantasy crashes with page fault on read access to 0x0 at address (0x1409b111f) Product: Wine Version: 3.14 Hardware: x86-64 URL: https://store.steampowered.com/app/552700/WORLD_OF_FIN AL_FANTASY/ OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lockert.fredrick(a)gmail.com Distribution: Debian Created attachment 62129 --> https://bugs.winehq.org/attachment.cgi?id=62129 Backtrace When starting World of Final Fantasy, it crashes with: wine: Unhandled page fault on read access to 0x00000000 at address 0x1409b111f -- 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 3

[Bug 47750] New: Linker complaining about multiple logf_finite definitions
by wine-bugs＠winehq.org 07 Oct '19

07 Oct '19

https://bugs.winehq.org/show_bug.cgi?id=47750 Bug ID: 47750 Summary: Linker complaining about multiple logf_finite definitions Product: Wine Version: 4.15 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: janarvottin(a)gmail.com Distribution: --- Created attachment 65231 --> https://bugs.winehq.org/attachment.cgi?id=65231 compilation log When compiling 4.15 with patches from staging repository linker fails to assemble libmvec_nonshared.a. Same problem aried with 4.14. Partial log attached. -- 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 2

[Bug 47104] New: Cannot click anywhere on VST plugins
by wine-bugs＠winehq.org 07 Oct '19

07 Oct '19

https://bugs.winehq.org/show_bug.cgi?id=47104 Bug ID: 47104 Summary: Cannot click anywhere on VST plugins Product: Wine-staging Version: 4.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: paulalbertdev(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Hi ! Just wanted you to know that 10mins ago everything was working fine but then I upgraded the staging version of wine and, since that, when I'm using windows VSTs plugins through vst-bridge and wine, clicks on the interface are not taken into account... So I cannot use no win VST anymore. Gonna downgrade to dev version but got other problems (less disturbing) with it. Good luck for fixing the bug ! Cheers -- 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 14

[Bug 40378] New: Monitor AOC I-menu not running
by wine-bugs＠winehq.org 07 Oct '19

07 Oct '19

https://bugs.winehq.org/show_bug.cgi?id=40378 Bug ID: 40378 Summary: Monitor AOC I-menu not running Product: Packaging Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-packages Assignee: wine-bugs(a)winehq.org Reporter: fatihfawaz(a)gmail.com CC: michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 54084 --> https://bugs.winehq.org/attachment.cgi?id=54084 Program error i can't running application from AOC, I-menu becouse i have a bug, a bug i attach the file. thank you... -- 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 5

[Bug 47904] New: Jobs should also report a count of failed test units
by WineHQ Bugzilla 06 Oct '19

06 Oct '19

https://bugs.winehq.org/show_bug.cgi?id=47904 Bug ID: 47904 Summary: Jobs should also report a count of failed test units Product: Wine-Testbot Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- Currently jobs report the number of individual ok() failures. That's ok when testing an individual test unit. But for WineTest jobs one can get numbers like 390 or even 2733. That's impossible to compare to the results of test.winehq.org which report the number of failed test units. In particular test.winehq.org rejects reports that have more than 50 or 70 failed test units and its impossible to tell by looking at the results on the TestBot whether the report was rejected or not. So it would be nice to report the number of failed test units in addition to the number of individual ok() failures. This would also be nice when a patch modifies a Wine module so that all its test units are re-run. -- 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 47902] New: CheckForWinetestUpdate systematically claims to have created jobs
by WineHQ Bugzilla 06 Oct '19

06 Oct '19

https://bugs.winehq.org/show_bug.cgi?id=47902 Bug ID: 47902 Summary: CheckForWinetestUpdate systematically claims to have created jobs Product: Wine-Testbot Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- CheckForWinetestUpdate.pl ends with the following lines: LogMsg "Submitted jobs\n"; exit $Rc; So whenever cron runs it this line appears in the TestBot log, even if the WineTest binaries have not been updated and no job was created. So while this allows making sure the script is still running as expected, the message is misleading. It would be better if it exited either with a message saying there was no update or which jobs got created. -- 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