wine-bugs November 2020

wine-bugs@winehq.org

1 participants
6745 discussions

[Bug 50066] New: dinput-remap-joystick causes crash with >32 button joystick
by WineHQ Bugzilla 07 Nov '20

07 Nov '20

https://bugs.winehq.org/show_bug.cgi?id=50066 Bug ID: 50066 Summary: dinput-remap-joystick causes crash with >32 button joystick Product: Wine-staging Version: 5.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lemmi59612(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 68522 --> https://bugs.winehq.org/attachment.cgi?id=68522 Log of `wine control joy.cpl` when crashing due to button 33 being pressed When the `dinput-remap-joystick` staging patch is applied to Wine, various crashes occur with a joystick that has more than 32 buttons. * Wine's `joy.cpl` crashes when pressing or releasing such a button (Wine-Staging) * Star Citizen crashes during launch (Wine-Staging + DXVK) `joy.cpl` works fine in vanilla Wine. Star Citizen requires other staging patches to launch, and works fine if `dinput-remap-joystick` is excluded. I'm using the Saitek X-55 Rhino HOTAS, where the throttle and stick can be plugged in independently. The throttle has 34 buttons and causes these crashes, the stick only reports 17 buttons (14 physically) and does not cause any crashes. Buttons 32-34 on the throttle are the three-state "MODE" switch (M1-M3 respectively). The crashes in `joy.cpl` happen regardless of whether the `(event)` or `(js)` interface of the throttle is selected. -- 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 50035] New: Bugs in ntdll-Junction_Points staging patchset
by WineHQ Bugzilla 07 Nov '20

07 Nov '20

https://bugs.winehq.org/show_bug.cgi?id=50035 Bug ID: 50035 Summary: Bugs in ntdll-Junction_Points staging patchset Product: Wine-staging Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: martin(a)martin.st CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 68475 --> https://bugs.winehq.org/attachment.cgi?id=68475 First patch Attaching two patches that can be squashed into the existing patches in ntdll-Junction_Points. The bugs are that FindNextFileW doesn't properly set the dwReserved0 field (containing the ReparseTag value) if iterating over files in a directory other than the current one, and that CreateSymbolicLinkA is unimplemented. -- 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 49829] New: file.c:237:37: error: 'EXTATTR_NAMESPACE_USER' undeclared building with GCC 9 and FreeBSD
by WineHQ Bugzilla 07 Nov '20

07 Nov '20

https://bugs.winehq.org/show_bug.cgi?id=49829 Bug ID: 49829 Summary: file.c:237:37: error: 'EXTATTR_NAMESPACE_USER' undeclared building with GCC 9 and FreeBSD Product: Wine-staging Version: 5.17 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gerald(a)pfeifer.com CC: damjan.jov(a)gmail.com, leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: Other Created attachment 68166 --> https://bugs.winehq.org/attachment.cgi?id=68166 Excerpt from the failure log This regression came between version 5.16 and 5.17 and only with Wine Staging. I am seeing this on FreeBSD/i386 11.x with GCC 9. -- 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 5

[Bug 50051] New: Error when launching gfclient.exe from a wineprefix
by WineHQ Bugzilla 07 Nov '20

07 Nov '20

https://bugs.winehq.org/show_bug.cgi?id=50051 Bug ID: 50051 Summary: Error when launching gfclient.exe from a wineprefix Product: Wine Version: 5.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: winehq_bugzilla(a)yahoo.com Distribution: --- Created attachment 68506 --> https://bugs.winehq.org/attachment.cgi?id=68506 Console output 5.20 Hi, This is the follow-up for bug 50023. Because despite the error happening in bug 50023, the gameforge client is installed on computer. Launching it this way gives an error, console output attached : wine gfclient.exe >>5.20.txt 2>&1 In particular that part is different from bug 50023 : [1024/080349.058:INFO:CONSOLE(1)] "%cCalling loggedOut method now", source: spark://www.gameforge.com/js/app.a6b5.js (1) [1024/080349.100:WARNING:cert_verify_proc_win.cc(104)] Unknown error -2146762482 mapped to net::ERR_FAILED wine: Unhandled exception 0x80000003 in thread 1dc at address 128B8D12 (thread 01dc), starting debugger... -- 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 49567] New: Warframe launcher ntdll dead locking since 5.10 staging, problem persists in 5.11 staging
by WineHQ Bugzilla 07 Nov '20

07 Nov '20

https://bugs.winehq.org/show_bug.cgi?id=49567 Bug ID: 49567 Summary: Warframe launcher ntdll dead locking since 5.10 staging, problem persists in 5.11 staging Product: Wine-staging Version: 5.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: katharine.chui(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 67707 --> https://bugs.winehq.org/attachment.cgi?id=67707 log at default log level, wine staging 5.11 Since wine 5.10 staging, warframe launher can no longer get through it's checking for new content stage and would get stuck there seemingly indefinitely with log message similar with ``` 0330:err:ntdll:RtlpWaitForCriticalSection section 0x7f0c224d64c0 "../../../dlls/ntdll/unix/virtual.c: csVirtual" wait timed out in thread 0330, blocked by 02e4, retrying (60 sec) ``` The said problem was not encountered on wine 5.9 staging, and is also observed on wine 5.11 staging below attaches log at default log level -- 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 50023] New: Back screen at game forge client loading (runes of magic)
by WineHQ Bugzilla 07 Nov '20

07 Nov '20

https://bugs.winehq.org/show_bug.cgi?id=50023 Bug ID: 50023 Summary: Back screen at game forge client loading (runes of magic) Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: winehq_bugzilla(a)yahoo.com Distribution: Debian Created attachment 68454 --> https://bugs.winehq.org/attachment.cgi?id=68454 Cousole output Hi, When launching the game, the first waiting screen checking for updates is ok, but after there is a black screen when displaying the gameforge client. Console output attached, from build including latest commit. -- 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 48836] New: Movies in 'BlazBlue Calamity Trigger' play without audio
by WineHQ Bugzilla 07 Nov '20

07 Nov '20

https://bugs.winehq.org/show_bug.cgi?id=48836 Bug ID: 48836 Summary: Movies in 'BlazBlue Calamity Trigger' play without audio Product: Wine Version: 5.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: quartz Assignee: wine-bugs(a)winehq.org Reporter: lvb.crd(a)protonmail.com Distribution: --- Created attachment 66755 --> https://bugs.winehq.org/attachment.cgi?id=66755 +amstream,+devenum,+evr,+quartz,+qcap,+qedit,+strmbase,+wineqtdecoder,+gstreamer,+timestamp,+seh,+tid output Movies in 'BlazBlue Calamity Trigger' play without audio maybe this output lines from log important warn:strmbase:filter_inner_QueryInterface {2dd74950-a890-11d1-abe8-00a0c905f375} not implemented, returning E_NOINTERFACE. warn:strmbase:filter_inner_QueryInterface {36b73880-c2c8-11cf-8b46-00805f6cef60} not implemented, returning E_NOINTERFACE. warn:strmbase:filter_inner_QueryInterface {37d84f60-42cb-11ce-8135-00aa004bb851} not implemented, returning E_NOINTERFACE. For this output I used https://github.com/wine-staging/wine-staging/commit/f9d1798edb5aea67db49ba4… because BlazBlue need 'xactengine-initial' patchset https://bugs.winehq.org/show_bug.cgi?id=48684 -- 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 10

[Bug 43396] New: Microsoft Outlook 2010 crashes after loading profile
by wine-bugs＠winehq.org 07 Nov '20

07 Nov '20

https://bugs.winehq.org/show_bug.cgi?id=43396 Bug ID: 43396 Summary: Microsoft Outlook 2010 crashes after loading profile Product: Wine Version: 2.0.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: marceloalmeida(a)inb.gov.br Distribution: --- Created attachment 58739 --> https://bugs.winehq.org/attachment.cgi?id=58739 normal start, with crash Microsoft Outlook 2010 crashes after loading the profile, but if I start whit the WINEDEBUG="+relay" option, it works, slowly but works. Commands used to configure the environment: - download, install and configure WineHQ $> sudo dnf config-manager --add-repo https://dl.winehq.org/wine-builds/fedora/25/winehq.repo $> sudo dnf install winehq-stable samba-common-tools samba-winbind-clients $> WINEPREFIX=~/wine/office2010 WINEARCH=win32 wineboot $> wget https://raw.githubusercontent.com/Winetricks/winetricks/master/src/winetric… $> chmod +x winetricks $> WINEPREFIX=~/wine/office2010 ./winetricks dotnet20 msxml - installl Office $> WINEPREFIX=~/wine/office2010 wine control open add/remove apps and do the Office2010 install, (optional) add the email profile (optional) $> WINEPREFIX=~/wine/office2010 winecfg change the "riched20" to native, to correct the input boxes - enabling WINEDEBUG="+relay" make the app to run with slow performance, but it works #> WINEPREFIX=~/wine/office2010 WINEDEBUG="+relay" wine ~/wine/office2010/drive_c/Office2010/Office14/OUTLOOK.EXE #> WINEPREFIX=~/wine/office2010 WINEDEBUG="+relay" wine ~/wine/office2010/drive_c/Office2010/Office14/OUTLOOK.EXE >~/wine/outlooklogdebug.txt 2>&1 - with this commands it crash after load the profile #> WINEPREFIX=~/wine/office2010 WINEDEBUG="+relay" wine ~/wine/office2010/drive_c/Office2010/Office14/OUTLOOK.EXE > /dev/null 2>&1 #> WINEPREFIX=~/wine/office2010 wine ~/wine/office2010/drive_c/Office2010/Office14/OUTLOOK.EXE >~/wine/outlooklog.txt 2>&1 -- 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 36893] New: Spin IDE (for Spin Semiconductor FV-1 DSP chip) crashes when you try to assemble your code.
by wine-bugs＠winehq.org 07 Nov '20

07 Nov '20

http://bugs.winehq.org/show_bug.cgi?id=36893 Bug ID: 36893 Summary: Spin IDE (for Spin Semiconductor FV-1 DSP chip) crashes when you try to assemble your code. Product: Wine Version: 1.7.17 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: faultline1989(a)yahoo.com Created attachment 49001 --> http://bugs.winehq.org/attachment.cgi?id=49001 The backtrace generated when this issue was encountered. I'm using Linux Mint version 15. Wine version is 1.7.17. The Windows installer for this program may be found here: http://www.spinsemi.com/Products/software/spn1001-dev/SpinSetup_1_1_31.exe Here is the main page describing the system: http://www.spinsemi.com/products.html After installing the program, download any of the ".spn" files at this page: http://www.spinsemi.com/programs.php Launch the SpinASM IDE and then open the .spn file so you are looking at the code. Click on the "a" icon at the top right of the tool bar to begin assembly of the code. It crashes at this point. -- 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 47397] New: Altium Designer 13.3.4 cannot render DirectX 3D on second monitor in Wine 4.10
by wine-bugs＠winehq.org 07 Nov '20

07 Nov '20

https://bugs.winehq.org/show_bug.cgi?id=47397 Bug ID: 47397 Summary: Altium Designer 13.3.4 cannot render DirectX 3D on second monitor in Wine 4.10 Product: Wine Version: 4.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: brian.mccarter.ctr(a)navy.mil Distribution: --- I have been running Altium Designer 13 on Wine successfully for some time, using these packages installed with winetricks: gdiplus, corefonts, riched20, mdac28, msxml16. That list was compiled from suggestions on the AppDB and may include unnecessary packages, but it's been working fine for me through Wine 4.7. The wineprefix is otherwise unmodified, and contains only the Altium installation. I use PlayOnLinux to manage the wineprefix and launch the application. The WINEARCH is win32. I recently upgraded to Wine 4.10 (vanilla, not staging), and found that Altium is no longer able to render DirectX 3D on my second monitor. Rendering on my primary monitor still works fine, and Wine does not crash or otherwise throw an error when I move the Altium window to my second monitor. The only error is reported by Altium, and reads: "Graphics adapter for this display does not meet DirectX requirements (DirectX 9.0c, Shader Model 3.0). Unable to switch to 3D." Doing some digging, I found that the last version of Wine that renders correctly on the second monitor is Wine 4.7. Versions 4.8, 4.9, and 4.10 all cause Altium to display the error. My system uses an NVIDIA Quadro M4000 and the proprietary driver, version 430.14. The OS is Gentoo Linux, kernel 5.1.5, mesa 18.3.6. I have also tried a recent Radeon card with mesa drivers and found the same problem, though I haven't tested that configuration as extensively. Nothing notable appears the debugger window when I launch the application through PlayOnLinux. I have tried to install several other programs with simple 3D displays in an attempt to duplicate the error with other software, but I haven't been successful. Please let me know how I can help resolve this 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.

2 2

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 November 2020