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

[Bug 46756] New: Running (Linux) bash from Wine doesn't output anything
by wine-bugs＠winehq.org March 3, 2019

March 3, 2019

https://bugs.winehq.org/show_bug.cgi?id=46756 Bug ID: 46756 Summary: Running (Linux) bash from Wine doesn't output anything Product: Wine Version: 4.2 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- Best explained by an example. Starting bash generally works: > wine start "Z:\bin\bash" -c "echo hello > x.txt" This creates a text file, as expected. The following command does not work properly: wine start "Z:\bin\bash" -c "echo hello" No text is printed to the terminal, while it should be. Don't know where it is disappearing to. -- 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 2

[Bug 46751] New: Allow starting native binaries
by wine-bugs＠winehq.org March 3, 2019

March 3, 2019

https://bugs.winehq.org/show_bug.cgi?id=46751 Bug ID: 46751 Summary: Allow starting native binaries Product: Wine Version: unspecified Hardware: x86 OS: other Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: kolan_n(a)mail.ru Sometimes apps use CLI apps, and these CLI apps have a version native for the OS and a compatible command line interface. It would be nice to allow Windows apps to call them. An example of such an app is git. Of course paths in arguments and env variables should be rewritten automatically. -- 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 46741] New: Cemu says "This program has encountered a serious problem " after opening Mario Maker
by wine-bugs＠winehq.org March 2, 2019

March 2, 2019

https://bugs.winehq.org/show_bug.cgi?id=46741 Bug ID: 46741 Summary: Cemu says "This program has encountered a serious problem" after opening Mario Maker Product: Wine Version: 4.0-rc5 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: 2021duffykod(a)isd47.org I'm using Cemu version 1.15.2 and I have open GL 4.1 on my Mac. Also I'm opening the file "Block.rpx" from the mario maker rom. -- 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 46749] New: Touhou 6 - The embodiment of Scarlet Devil: Wrong sprite layering of player and boss sprites
by wine-bugs＠winehq.org March 2, 2019

March 2, 2019

https://bugs.winehq.org/show_bug.cgi?id=46749 Bug ID: 46749 Summary: Touhou 6 - The embodiment of Scarlet Devil: Wrong sprite layering of player and boss sprites Product: Wine Version: 4.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: intensonat(a)gmail.com Distribution: --- Created attachment 63752 --> https://bugs.winehq.org/attachment.cgi?id=63752 Player rendered above boss Distro: Fedora 29 x86_64 Wine Staging was used when making screenshot for this report but the bug is reproducible without Wine Staging When the position of the player and the boss overlap, the player is rendered under the boss on Windows (happens with versions listed on the jewel case: http://www16.big.or.jp/~zun/img/th06/th06logo01.jpg) Wine renders the player sprite above the boss. Tested with version 1.02h but reproducible with trial 0.13 available here: http://www16.big.or.jp/~zun/data/soft/kouma_tr013.lzh -- 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 1892] weird installation error (strange setup)
by wine-bugs＠winehq.org March 2, 2019

March 2, 2019

https://bugs.winehq.org/show_bug.cgi?id=1892 Uday_Sri_Harsha <drakemcmannis9876(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |drakemcmannis9876(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 46707] New: Microsoft Word 2019 freeze the whole screen on nouveau driver with CSMT enabled
by wine-bugs＠winehq.org March 1, 2019

March 1, 2019

https://bugs.winehq.org/show_bug.cgi?id=46707 Bug ID: 46707 Summary: Microsoft Word 2019 freeze the whole screen on nouveau driver with CSMT enabled Product: Wine Version: 4.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: peathot(a)hotmail.com Distribution: --- Created attachment 63673 --> https://bugs.winehq.org/attachment.cgi?id=63673 Console output with CSMT enabled When using Microsoft Word 2019 (version 1902, build 11328.20100, installed via Office 365) for a while, the program, followed by the whole screen, will freeze. The mouse pointer is still movable, and I can SSH into the machine and kill WINWORD.EXE. After a moment, the screen will become usable again. By disabling CSMT in registry (HKCU/Software/Wine/Direct3D, csmt=dword:00000000), the problem doesn't occurred. The console output for both when CSMT is enabled and disabled is attached. Also, the kernel messages when CSMT is enabled is attached (there's no kernel messages when CSMT is disabled). This is Wine 4.2 on Xubuntu 18.04. The machine is Mac Mini early 2009 with Nvidia Geforce 9400m [1]. The graphic stack is mesa + nouveau (i.e. Nvidia proprietary driver is not installed). The MS Office is installed using the instructions from [2]. The first registry workaround is also used. Actually, the kernel messages suggests that it's nouveau fault. From my research, it seems like nouveau doesn't like OpenGL calls from multiple thread [3][4]. If it's actually nouveau's fault, I guess we could disable CSMT by default if we detect nouveau driver? [1] Yes, it's a bit old. But this same machine can run this software on Windows 10. So, it's not the problem. [2] https://appdb.winehq.org/objectManager.php?sClass=version&iId=35527&iTestin… [3] https://bugs.freedesktop.org/show_bug.cgi?id=92438#c39 [4] https://bugreports.qt.io/browse/QTBUG-73715 -- 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 46695] New: Linking atl fails on ppc64el with undefined reference to SetWindowLongPtrW
by wine-bugs＠winehq.org March 1, 2019

March 1, 2019

https://bugs.winehq.org/show_bug.cgi?id=46695 Bug ID: 46695 Summary: Linking atl fails on ppc64el with undefined reference to SetWindowLongPtrW Product: Wine Version: 4.2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: tpearson(a)raptorengineering.com Distribution: --- When building on ppc64el, linking atl fails with an undefined reference to SetWindowLongPtrW. I suspect this is due to the existing PowerPC code assuming ppc platforms are 32 bit only; SetWindowLongPtrW is a 64 bit call. -- 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 31644] New: glMapBufferRange is extremely slow while playing Resident Evil 5 ( happens only on nvidia binary driver )
by wine-bugs＠winehq.org March 1, 2019

March 1, 2019

http://bugs.winehq.org/show_bug.cgi?id=31644 Bug #: 31644 Summary: glMapBufferRange is extremely slow while playing Resident Evil 5 ( happens only on nvidia binary driver ) Product: Wine Version: 1.5.12 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: tizbac2(a)gmail.com Classification: Unclassified Calls to glMapBufferRange are extremely slow on nvidia drivers with resident evil 5, if this should be reported to nvidia instead just close it over 90% of frame time is taken by glMapBufferRange -- 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.

1 20

[Bug 38488] New: Wrong taces in functions *_invalidate_location
by wine-bugs＠winehq.org March 1, 2019

March 1, 2019

https://bugs.winehq.org/show_bug.cgi?id=38488 Bug ID: 38488 Summary: Wrong taces in functions *_invalidate_location Product: Wine Version: 1.7.41 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: isakov-sl(a)bk.ru Distribution: --- I got a plenty of messages like fixme:d3d:wined3d_debug_location Unrecognized location flag(s) 0xfffffc00. fixme:d3d:wined3d_debug_location Unrecognized location flag(s) 0xfffffc00. fixme:d3d:wined3d_debug_location Unrecognized location flag(s) 0xfffffc00. fixme:d3d:wined3d_debug_location Unrecognized location flag(s) 0xfffffc00. It rises because the function wined3d_volume_invalidate_location() is used with reversed parameter For example dlls/wined3d/device.c: wined3d_volume_invalidate_location(dst_volume, ~WINED3D_LOCATION_TEXTURE_RGB); The function assumed location and not ~location. ----- void wined3d_volume_invalidate_location(struct wined3d_volume *volume, DWORD location) { TRACE("Volume %p, clearing %s.\n", volume, wined3d_debug_location(location)); volume->locations &= ~location; TRACE("new location flags are %s.\n", wined3d_debug_location(volume->locations)); } ----- Here wined3d_debug_location() will message like above. Same about wined3d_resource_invalidate_location(struct wined3d_resource *resource, DWORD location) -- 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 45149] New: regedit crashes (with no visible crash dialog) in winetricks dotnet35sp1
by wine-bugs＠winehq.org March 1, 2019

March 1, 2019

https://bugs.winehq.org/show_bug.cgi?id=45149 Bug ID: 45149 Summary: regedit crashes (with no visible crash dialog) in winetricks dotnet35sp1 Product: Wine Version: 3.7 Hardware: x86 OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com CC: z.figura12(a)gmail.com Distribution: Gentoo Originally reported at https://github.com/Winetricks/winetricks/issues/810 winetricks hangs when running regedit (though this doesn't happen anywhere else). If you run ps aux, you can see that winedbg --auto is running, but there's no crash dialog (it was not diabled). Talking with Zebediah about it on IRC, he pointed out that staging has a patch that allows the dialog to at least show: https://github.com/wine-staging/wine-staging/blob/master/patches/kernel32-D… I couldn't find any other bug bug referencing it. Of course, there's a second bug, in that running regedit crashes (when setting the windows version).. -- 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