August 2018 - Wine-Bugs - list.winehq.org

[Bug 39676] New: The Darkness II shows only black screen when CSMT enabled
by wine-bugs＠winehq.org Aug. 20, 2018

Aug. 20, 2018

https://bugs.winehq.org/show_bug.cgi?id=39676 Bug ID: 39676 Summary: The Darkness II shows only black screen when CSMT enabled Product: Wine-staging Version: 1.8-rc1 Hardware: x86 URL: http://store.steampowered.com/app/67370/ OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 52901 --> https://bugs.winehq.org/attachment.cgi?id=52901 terminal output This is the game from bug #30061. When CSMT is enabled in staging, the game starts but shows only a black screen (I can hear audio from the intro videos but nothing can be seen). This happens when the game is started in fullscreen mode. In windowed mode the game starts properly (CSMT enabled). Switching between fullscreen and windowed mode is available in the game's display option menu. This might be interesting from the console log (not present when CSMT is disabled): err:d3d:wined3d_debug_callback 0x21be40: "GL_INVALID_VALUE in glTexSubImage2D(xoffset+width)". err:d3d_surface:wined3d_surface_upload_data >>>>>>>>>>>>>>>>> GL_INVALID_VALUE (0x501) from glTexSubImage2D @ ../wined3d/surface.c / 1706 The problem can be reproduced with the demo version on Steam. wine-1.8-rc1-81-g6790d82 (Staging) Fedora 23 OpenGL vendor string: nouveau OpenGL renderer string: Gallium 0.4 on NV92 OpenGL core profile version string: 3.3 (Core Profile) Mesa 11.2.0-devel OpenGL core profile shading language version string: 3.30 -- 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 40332] New: Prince of Persioa 2008 crash at intro with wine-staging csmt
by wine-bugs＠winehq.org Aug. 20, 2018

Aug. 20, 2018

https://bugs.winehq.org/show_bug.cgi?id=40332 Bug ID: 40332 Summary: Prince of Persioa 2008 crash at intro with wine-staging csmt Product: Wine Version: 1.9.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fin4478(a)hotmail.com Distribution: --- Similar bug in wine-staging version than in 36063. Graphics hangs in the intro sequence when Elika looks up and shuts the mouth of Prince. Sound keeps going on for a while. To kill the game, press alt+ctrl+f1 and type ps -e to find the application id. There is no trace in the terminal what happened when launching the game from a terminal. With wine 1.8.1 the game works ok. -- 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 41384] New: Office 2010: Activation doesn' t work after wine-staging 1.9.3
by wine-bugs＠winehq.org Aug. 20, 2018

Aug. 20, 2018

https://bugs.winehq.org/show_bug.cgi?id=41384 Bug ID: 41384 Summary: Office 2010: Activation doesn't work after wine-staging 1.9.3 Product: Wine-staging Version: 1.9.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jvtr(a)f.fxnxs.com CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- After comparing logs between wine-staging versions 1.9.3 and 1.9.4 I have realized an unsuccessful call happening to SetupDiGetDeviceRegistryProperty with property value 1 (SPDRP_HARDWAREID). HardwareId is not present, because the patch <b>setupapi-Display_Device/0001-setupapi-Create-registry-keys-for-display-devices-an.patch</b> creates keys for the display device (create_display_keys) without HardwareID value. Before the patch there was no device info and thus no calls from application to get that property. Workaround is simple - create registry value HardwareID of type REG_MULTI_SZ with value "PCI\VEN_0000&DEV_0000" (to be honest I don't know what constitutes the right values) in HKEY_LOCAL_MACHINE\System\CurrentControlSet\Enum\PCI\VEN_0000&DEV_0000\13&12345&0. It can even be empty for the activation to work. example registry file: REGEDIT4 [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Enum\PCI\VEN_0000&DEV_0000\13&12345&0] "HardwareId"=hex(7):50,43,49,5c,56,45,4e,5f,30,30,30,30,26,44,45,56,5f,30,30,\ 30,30,00,00,00,00 Tested with Microsoft Word 2010 version 14.0.7015.1000. -- 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 44024] New: Battle.net leaves processes open after exiting.
by wine-bugs＠winehq.org Aug. 20, 2018

Aug. 20, 2018

https://bugs.winehq.org/show_bug.cgi?id=44024 Bug ID: 44024 Summary: Battle.net leaves processes open after exiting. Product: Wine-staging Version: 2.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: peter.g.anderson(a)live.co.uk CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- When exiting the Blizzard App / Battle.net client, the application window closes, but looking in system monitor shows that there is a Battle.net.exe and an Agent.exe still running, as well as the associated wine processes such as wineserver etc. These persist until Battle.net.exe and Agent.exe are killed manually, in that order. If the application was launched in a virtual desktop, the desktop will remain open and visible, but unusable. This bug would perhaps affect plain wine as well as staging, but there are other issues that prevent plain wine from running Battle.net. Unable to find any workaround for this, except for manually killing the processes in task manager. -- 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 19

[Bug 42377] New: WSASend() returns invalid number of bytes when both lpOverlapped and lpNumberOfBytesSent
by wine-bugs＠winehq.org Aug. 20, 2018

Aug. 20, 2018

https://bugs.winehq.org/show_bug.cgi?id=42377 Bug ID: 42377 Summary: WSASend() returns invalid number of bytes when both lpOverlapped and lpNumberOfBytesSent Product: Wine Version: 2.0-rc5 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: zbr(a)ioremap.net Distribution: --- Created attachment 57161 --> https://bugs.winehq.org/attachment.cgi?id=57161 WINEDEBUG=+all ./grtest_server Golang uses overlapped sockets, but sets both lpOverlapped and lpNumberOfBytesSent. Sometimes lpNumberOfBytesSent is returned to be higher than number of bytes in the buffer to be sent, this breaks overlapped state machine in golang, which eventually ends up with error and connection reset. Bug is 100% reproducible, but it requires quite a setup. First, golang uses memory mapped page hack to get time structures. These are not updated by wine (see the bug here: https://bugs.winehq.org/show_bug.cgi?id=29168) To fix it I made a patch for golang which falls back to QPC timings if startup code detects timer is stalled, see patches and discussion: https://go-review.googlesource.com/#/c/35710/ https://github.com/golang/go/issues/18537 After golang has been patched, I use this test case to compile a grpc server and python client: https://github.com/bioothod/grpc_test # edit Makefile to specify golang path and root directory $ make windows $ wine ./grpc_server $ python client.py ... Running multiple clients 100% ends up with connection close errors, which I debugged to incorrect (larger than the buffer size) lpNumberOfBytesSent Here is a discussion: https://github.com/golang/go/issues/18887 Turning overlapped feature off (by setting lpOverlapped to NULL) resolves the bug, but as far as I understand it ends up with blocked WSASend() call, who will wait for buffer to be completely sent, which is kind of undesired behaviour. Attached WINEDEBUG=+all ./grtest_server log if it helps. -- 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 22

[Bug 41512] New: Adobe Creative Cloud application crashing
by wine-bugs＠winehq.org Aug. 20, 2018

Aug. 20, 2018

https://bugs.winehq.org/show_bug.cgi?id=41512 Bug ID: 41512 Summary: Adobe Creative Cloud application crashing Product: Wine-staging Version: unspecified Hardware: x86 URL: http://ccmdls.adobe.com/AdobeProducts/KCCC/1/win32/Cre ativeCloudSet-Up.exe OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mrypsilons(a)gmail.com CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 55876 --> https://bugs.winehq.org/attachment.cgi?id=55876 backtrace from the crash dialog The application immediately crashes on startup. Did a regression test, the crash is happening if this patch is applied: https://github.com/wine-compholio/wine-staging/blob/master/patches/kernel32… I can provide terminal output, but I don't know what WINEDEBUG flags to use. Steps to reproduce: - Set version to Windows 7 - Run the installer (see URL field) - Installer automatically starts installed "Creative Cloud.exe", which immediately crashes -- 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 42679] New: no alpha while blitting in batches
by wine-bugs＠winehq.org Aug. 20, 2018

Aug. 20, 2018

https://bugs.winehq.org/show_bug.cgi?id=42679 Bug ID: 42679 Summary: no alpha while blitting in batches Product: Wine-staging Version: 2.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: keloero(a)oreolek.ru CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 57641 --> https://bugs.winehq.org/attachment.cgi?id=57641 fireurq2.1 - run test.qst [I'm not the app developer, but I noticed the bug.] The bug occurs only in staging version, Wine 2.0 stable and lower are unaffected. There is no alpha channel while blitting in batches, the bitmaps have black background. How to reproduce: see the fireurq.7z attachment; run fireURQ2.exe, choose test.qst as the game or just run like this: wine fireURQ2.exe test.qst Look at the button, the letters have rough black edges on them. It shouldn't look like that and it doesn't in Wine 2.0 -- 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 42123] New: Missing icons in jsMSIx
by wine-bugs＠winehq.org Aug. 20, 2018

Aug. 20, 2018

https://bugs.winehq.org/show_bug.cgi?id=42123 Bug ID: 42123 Summary: Missing icons in jsMSIx Product: Wine Version: 2.0-rc3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jhansonxi(a)gmail.com Distribution: Ubuntu Created attachment 56657 --> https://bugs.winehq.org/attachment.cgi?id=56657 White icons Xubuntu 14.04 (and 16.04) x86_64, AMD Phenom 9550, GeForce GTX 750Ti with Nvidia 340.98 driver. Windows version: Windows XP Wine Staging (wine PPA) and git There's a regression in jsMSIx. Most button icons are completely white (compare to screenshot in AppDB). I first noticed it with 1.9.23 (PPA). Worked with 1.8-rc1 when I last filed a test report. It works with 1.7.55 and 1.8.0 from the repos so I began regression testing. I first compiled from git at current head a few days ago and retested. Unexpectedly the icons displayed properly. I retested 2.0-rc3 from the PPA on Xubuntu 16.04 and they were white again. Seems like there is a problem with the PPA packages. May be related to bug #42121. Requires VB6 runtime (winetricks -q vb6run). -- 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 40363] New: Wine Stabilization - Gentoo Slow to Adopt With Valid Reason
by wine-bugs＠winehq.org Aug. 20, 2018

Aug. 20, 2018

https://bugs.winehq.org/show_bug.cgi?id=40363 Bug ID: 40363 Summary: Wine Stabilization - Gentoo Slow to Adopt With Valid Reason Product: Wine-staging Version: 1.8.1 Hardware: x86-64 URL: https://bugs.gentoo.org/show_bug.cgi?id=578202 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ecyoung(a)grandecom.net CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: Gentoo I opened the bug that I'm asking you to comment on. I opened this bug because Gentoo's Stable version is still at 1.6.2. I use an old RPG, Istaria which is blocky in 1.9.5, and Eve Online, which is unplayable in my case using 1.6.2. In order to properly regression test where my issues are coming from, I thought I would start at finding out why Gentoo's stable version lagged behind WineHQ's stable version. Our package maintainer is doing the best he can, as our distribution is source based, and he is perfectly within his right not to use a custom patchset (See Comment 3). Comment 7 in my bug states: Let's keep this open with the info from NP-Hardass so that anybody else who seeks for 1.8.1 knows. I'm closing #578272 as I see no point of having it open. NP-Hardass stated he wants to bump and stabilize 1.8.x, so it's on upstream now. Thanks for your interest Carter, maybe try to convince upstream to get it going ;) ---------------------------------------- Bug 578272 was implemented as a tracker, but the commenter is correct in assuming that the issue lies upstream. I present Snippets from Comment 3: I'd prefer that our stable wine 1.8 use the official gstreamer 1.0 patchset, but upstream never released that under the 1.8 branch. Once again though, I'd rather not be hosting a custom patchset for stable. There is currently a request to the upstream wine stable maintainer to include this in 1.8.2. 1.8.1 was never bumped because Wine Staging never released a patchset for 1.8.1 and I'd rather not have a stable candidate in package.use.stable.mask and not have staging support. I'd also rather not have to host a custom staging patch just for 1.8.1. I've cc'd the Staging devs in case they'd like to weigh in on making an official release for 1.8.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.

1 7

[Bug 41344] New: err:seh: setup_exception_record stack overflow crash in SAO visual novel
by wine-bugs＠winehq.org Aug. 20, 2018

Aug. 20, 2018

https://bugs.winehq.org/show_bug.cgi?id=41344 Bug ID: 41344 Summary: err:seh:setup_exception_record stack overflow crash in SAO visual novel Product: Wine Version: 1.9.18 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: wyrex(a)openmailbox.org Distribution: --- Created attachment 55691 --> https://bugs.winehq.org/attachment.cgi?id=55691 Log without +seh Game plays opening video but crashes after second screen of text ingame. Happens every time. Trial version which I used is available here (NSFW!) http://sample9.dmm.co.jp/digital/cg_game/d_066395/d_066395t.lzh. winecfg is set to Win 7 and "devenum ffdshow quartz vcrun6 native_oleaut32" are installed from winetricks. -- 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 18