September 2019 - Wine-Bugs - list.winehq.org

[Bug 47730] New: Synthesia does not handle piano reconnect
by wine-bugs＠winehq.org Sept. 12, 2019

Sept. 12, 2019

https://bugs.winehq.org/show_bug.cgi?id=47730 Bug ID: 47730 Summary: Synthesia does not handle piano reconnect Product: Wine Version: 4.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: spleefer90(a)gmail.com Distribution: --- Using Synthesia 10.5.1. Setting Synthesia up for USB MIDI Piano works great, but when I disconnect the piano (either by turning it off or physically unplugging the cable) and then reconnecting it again, I need to restart Synthesia or disable/enable the piano in Synthesia to make it work again. This does not happen on Windows 10 1903, there it finds the piano again on reconnect. Physically disconnecting the cable: 0077:fixme:midi:handle_midi_event Unexpected event received, type = 43 from 0:1 At reconnect there's no new logs. Pressing "Ignore this device" and "Use this device" in Synthesia to get it picked up again: 0078:fixme:avrt:AvRevertMmThreadCharacteristics (12345678): stub 007e:fixme:avrt:AvSetMmThreadCharacteristicsW (L"Audio",03EAFF14): stub 007e:fixme:avrt:AvRevertMmThreadCharacteristics (12345678): stub 0084:fixme:avrt:AvSetMmThreadCharacteristicsW (L"Audio",03FBFF14): stub Tried with wine and wine-staging on 4.15. -- 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 47756] Bugzilla Email Issues - Not Sending
by WineHQ Bugzilla Sept. 12, 2019

Sept. 12, 2019

https://bugs.winehq.org/show_bug.cgi?id=47756 --- Comment #9 from Alexandre Julliard <julliard(a)winehq.org> --- Hopefully it's working now -- 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 47756] Bugzilla Email Issues - Not Sending
by WineHQ Bugzilla Sept. 12, 2019

Sept. 12, 2019

https://bugs.winehq.org/show_bug.cgi?id=47756 --- Comment #8 from Alexandre Julliard <julliard(a)winehq.org> --- testing... -- 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 47753] Magic The Gathering: Arena (MTGA) issue crashing on start
by WineHQ Bugzilla Sept. 11, 2019

Sept. 11, 2019

https://bugs.winehq.org/show_bug.cgi?id=47753 Benjamin <benjamin.bozou(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |benjamin.bozou(a)gmail.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.

1 0

[Bug 47749] New: Reconnect of gamepad
by wine-bugs＠winehq.org Sept. 9, 2019

Sept. 9, 2019

https://bugs.winehq.org/show_bug.cgi?id=47749 Bug ID: 47749 Summary: Reconnect of gamepad Product: Wine-staging Version: 4.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alexzk(a)mail.ru CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- If gamepad is reconnected windows game (Elite dangerous in my case) fails to use it back. Elite itself has a bug so you can see if gamepad was connected during startup due this bug. So it seems game detects gamepad but cannot receive events from. Complete restart of wine (closing ALL windows programs in prefix) resolves issue. If wine was not restarted (for example, launcher still runs) then gamepad is "broken". Downgrading to 4.12.1 fixed that - gamepad is working after reconnect. P.S. ONCE it worked ok for me in 4.15 too, but it was 1 time of 100 reconnects or so. -- 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 47729] New: Amazon Workspaces Client: crashes after login when launching Windows WorkSpace desktop
by wine-bugs＠winehq.org Sept. 9, 2019

Sept. 9, 2019

https://bugs.winehq.org/show_bug.cgi?id=47729 Bug ID: 47729 Summary: Amazon Workspaces Client: crashes after login when launching Windows WorkSpace desktop Product: Wine Version: 4.15 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: casutherland(a)gmail.com Distribution: --- Created attachment 65206 --> https://bugs.winehq.org/attachment.cgi?id=65206 backtrace Running Ubuntu 18.04 LTS and installed the Amazon WorkSpaces client Version 2.5.8.1216 around 16-Jul-2019, using the distro default wine-stable package, and a (much) older version of wine-stable. Everything was working fine, the WorkSpaces client successfully launched Windows WorkSpaces & Linux WorkSpaces. Then, I ran the software update tool, for Ubuntu 18.04.3 LTS around 01-Aug-2019. Shortly after the update, the WorkSpaces client began failing with the error message below whenever a Windows WorkSpace was launched. Authentication is successful, however the client crashes immediately after the Windows WorkSpace display is opened. "The program workspaces.exe has encountered a serious problem and needs to close. We are sorry for the inconvenience." "This can be caused by a problem in the program or a deficiency in Wine. You might want to check the Application Database for tips about running this application." Note that the WorkSpaces client running with wine successfully launches a Linux WorkSpaces desktop, however the client crashes when launching a Windows WorkSpaces desktop. Upgraded the WorkSpaces client to Version 2.5.10.1246, and it is till failing, with the same error message. Updated Wine to 4.15 development and tried both versions of the WorkSpaces client, 2.5.8.1216 and 2.5.10.1246, still failing with the same error message. A full stacktrace is attached, and the following excerpt is displayed on the terminal from which the workspaces.exe is launched using wine. 017c:fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0034CDFC 1 C) semi-stub 00ec:fixme:winsock:WSAIoctl WS_SIO_UDP_CONNRESET stub 0117:err:winediag:WSASocketW Failed to create a socket of type SOCK_RAW, this requires special permissions. 014b:fixme:winspool:FindFirstPrinterChangeNotification Stub: 0x1 7 0 0xfe7fef4 wine: Unhandled page fault on read access to 0x00000000 at address 0x7da63bac (thread 014b), starting debugger... 014e:fixme:dbghelp:elf_search_auxv can't find symbol in module -- 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 47745] New: crash dialog should instruct to attach console log to bug report
by wine-bugs＠winehq.org Sept. 8, 2019

Sept. 8, 2019

https://bugs.winehq.org/show_bug.cgi?id=47745 Bug ID: 47745 Summary: crash dialog should instruct to attach console log to bug report Product: Wine Version: 4.15 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: winedbg Assignee: wine-bugs(a)winehq.org Reporter: apq49584(a)tuofs.com Distribution: --- The crash dialog displays the backtrace in a convinent window and instructs the user to attach that to a bug report. But as I have learned, the console log (with debug symbols installed) is even more useful/required information to attach. It would make sense for the Error Details Windows to prominently mention that and display short instructions on how to obtain it, or even display it right away, if possible. related: https://bugs.winehq.org/show_bug.cgi?id=28543 -- 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 46821] New: Alan Wake has light rendering issue
by wine-bugs＠winehq.org Sept. 7, 2019

Sept. 7, 2019

https://bugs.winehq.org/show_bug.cgi?id=46821 Bug ID: 46821 Summary: Alan Wake has light rendering issue Product: Wine Version: 4.3 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- Created attachment 63844 --> https://bugs.winehq.org/attachment.cgi?id=63844 screenshot Staying in a safe zone shows this. Contrast depends on angle. Reproducible after commit dd0ea0a61463db83c647a9367ca61e2b69a98eb3. Solves with cleaning shaders cache and disabling CSMT. After that: err:d3d:wined3d_debug_callback 0x1c589c0: "GL_INVALID_OPERATION error generated. <program> has not been linked, or is not a program object.". err:d3d:wined3d_debug_callback 0x1c589c0: "GL_INVALID_OPERATION error generated. <program> object is not successfully linked, or is not a program object.". NVIDIA Driver 418.43, wine-4.3-229-g6d82b2f1ad -- 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 11

[Bug 42987] New: Dawn of Magic does not start with DirectX failed call error
by wine-bugs＠winehq.org Sept. 7, 2019

Sept. 7, 2019

https://bugs.winehq.org/show_bug.cgi?id=42987 Bug ID: 42987 Summary: Dawn of Magic does not start with DirectX failed call error Product: Wine Version: 2.7 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: 00cpxxx(a)gmail.com Distribution: Debian Created attachment 58124 --> https://bugs.winehq.org/attachment.cgi?id=58124 std log with +msgbox Dawn of Magic installs but does not run with the message below right after changing screen resolution. The game does not seem to have a demo, I can provide other logs as requested. trace:msgbox:MSGBOX_OnInit L".\\BMRender\\rmode.cpp(3583): DirectX call failed: code=0x80004001 (-2147467263)" Tested on both Intel with Mesa 13.0.5 and NVIDIA proprietary driver, with CSMT on/off results are the same. -- 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 47714] New: Empire Earth: Gold rotate some menu components
by wine-bugs＠winehq.org Sept. 7, 2019

Sept. 7, 2019

https://bugs.winehq.org/show_bug.cgi?id=47714 Bug ID: 47714 Summary: Empire Earth: Gold rotate some menu components Product: Wine Version: 4.14 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: slawek(a)lach.art.pl Distribution: --- Empire Earth's main menu is completely broken. Background is rotated 180 degrees, but menu element not. After go to options menu, some elements are rotated 180 degrees with rotate point set to center of the screen. https://pastebin.com/e7GkpqzE I using wine 4.14 on OpenSUSE Tumbleweed. My computer have Intel and AMD graphic card. -- 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