November 2018 - Wine-bugs - list.winehq.org

[Bug 45622] New: Overwatch crashes when trying to save highlights
by wine-bugs＠winehq.org 29 Nov '18

29 Nov '18

https://bugs.winehq.org/show_bug.cgi?id=45622 Bug ID: 45622 Summary: Overwatch crashes when trying to save highlights Product: Wine Version: 3.13 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: sashok.olen(a)gmail.com Distribution: --- Created attachment 62052 --> https://bugs.winehq.org/attachment.cgi?id=62052 terminal output Whenever I try to save a highlight through in-game feature, the game crashes, even with hardware encoding option disabled. It doesn't crash with a wine debugger dialog but I attached a part of the terminal output of when it crashes. The game also creates its own dump when it crashes but I am not sure it's useful to wine developers. However, if it is, just ask for it and I will upload it. -- 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 26

[Bug 43488] New: cant run software
by wine-bugs＠winehq.org 29 Nov '18

29 Nov '18

https://bugs.winehq.org/show_bug.cgi?id=43488 Bug ID: 43488 Summary: cant run software Product: Wine Version: 2.10 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: neneda(a)www.bccto.me Distribution: --- Created attachment 58870 --> https://bugs.winehq.org/attachment.cgi?id=58870 i cant fix it when i run the software bluestacks ,the problem comes out -- 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 42870] New: CurrentBuild registry value is missing
by wine-bugs＠winehq.org 29 Nov '18

29 Nov '18

https://bugs.winehq.org/show_bug.cgi?id=42870 Bug ID: 42870 Summary: CurrentBuild registry value is missing Product: Wine Version: 2.6 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: registry Assignee: wine-bugs(a)winehq.org Reporter: pgkos.bugzilla(a)yahoo.com Distribution: ArchLinux In HKLM\Software\Microsoft\Windows NT\CurrentVersion\, all Windows versions since at least Windows XP have a "CurrentBuild" registry string value (aside from "CurrentBuildNumber"). In Wine's registry, there exists only "CurrentBuildNumber". For maximum compatibility, the "CurrentBuild" value should exist and be created/updated by winecfg when switching Windows versions. It should have the same value as the "CurrentBuildNumber", for example on Windows 7 SP1: CurrentBuildNumber = "7601" CurrentBuild = "7601" <-- this value is missing -- 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 43125] New: Device reports coming in too fast
by wine-bugs＠winehq.org 29 Nov '18

29 Nov '18

https://bugs.winehq.org/show_bug.cgi?id=43125 Bug ID: 43125 Summary: Device reports coming in too fast Product: Wine Version: 2.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: pershyn_nikolay(a)mail.ru Distribution: --- Launching wine or winecfg in any prefix(including clean prefix) reports errors about device reports coming too fast. $ WINEPREFIX=~/.local/share/wineprefixes/Temp32/ WINEARCH=win32 winecfg err:hid_report:process_hid_report Device reports coming in too fast, last report not read yet! After it(any application or winecfg) is closed following line appears in console output: wine: Unhandled page fault on read access to 0x7e479e70 at address 0x7ec9e1e1 (thread 0034) I don't really know what information would be useful to provide here. Well, it says hid, which I assume means human interface device. My input devices are ROCCAT Tyon and Microsoft Natural Ergonomic Keyboard 4000. # uname -a Linux subspace 4.9.16-gentoo #1 SMP Fri Apr 21 19:37:09 MDT 2017 x86_64 Intel(R) Xeon(R) CPU E5-2630 v3 @ 2.40GHz GenuineIntel GNU/Linux # grep INPUT /etc/portage/make.conf INPUT_DEVICES="${INPUT_DEVICES} evdev roccat_tyon" # ls -l /dev/input/by-id/ total 0 lrwxrwxrwx 1 root root 9 May 23 21:37 usb-Microsoft_Natural®_Ergonomic_Keyboard_4000-event-kbd -> ../event9 lrwxrwxrwx 1 root root 10 May 23 21:37 usb-Microsoft_Natural®_Ergonomic_Keyboard_4000-if01-event-kbd -> ../event10 lrwxrwxrwx 1 root root 10 May 23 21:37 usb-ROCCAT_ROCCAT_Tyon_White_ROC-11-851-event-mouse -> ../event11 lrwxrwxrwx 1 root root 10 May 23 21:37 usb-ROCCAT_ROCCAT_Tyon_White_ROC-11-851-if01-event-kbd -> ../event12 lrwxrwxrwx 1 root root 10 May 23 21:37 usb-ROCCAT_ROCCAT_Tyon_White_ROC-11-851-if02-event-joystick -> ../event13 lrwxrwxrwx 1 root root 9 May 23 21:37 usb-ROCCAT_ROCCAT_Tyon_White_ROC-11-851-mouse -> ../mouse0 -- 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 24

[Bug 36884] New: Drakensang: The Dark Eye demo crashes on startup (needs d3dx9_36.dll.D3DXCreateTeapot implementation)
by wine-bugs＠winehq.org 29 Nov '18

29 Nov '18

https://bugs.winehq.org/show_bug.cgi?id=36884 Bug ID: 36884 Summary: Drakensang: The Dark Eye demo crashes on startup (needs d3dx9_36.dll.D3DXCreateTeapot implementation) Product: Wine Version: 1.7.22 Hardware: x86 URL: http://www.gamershell.com/download_36990.shtml OS: Linux Status: NEW Keywords: download Severity: minor Priority: P2 Component: directx-d3dx9 Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Follow up to bug 35742. Now that D3DXCreateTorus is implemented, the game crashes on start with a dialog box saying: *** NEBULA ASSERTION ***\nprogrammer says: nD3D9Server::DeviceOpen(): D3DXCreateTeapot() failed! and in the terminal (the only d3dx fixme): fixme:d3dx:D3DXCreateTeapot (0x193100, 0x3242ec4, (nil)): stub austin(a)aw25 ~ $ sha1sum Drakensang_DEMO_setup_ENGLISH.exe 2e47a2fbc7307e736394bf1d2b1a2f09c497c7a1 Drakensang_DEMO_setup_ENGLISH.exe austin(a)aw25 ~ $ du -h Drakensang_DEMO_setup_ENGLISH.exe 501M Drakensang_DEMO_setup_ENGLISH.exe austin(a)aw25 ~ $ wine --version wine-1.7.22 -- 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 12

[Bug 37834] New: RtlSetCurrentDirectory_U prepends "UNC\" for network paths; the resulting path is invalid
by wine-bugs＠winehq.org 29 Nov '18

29 Nov '18

https://bugs.winehq.org/show_bug.cgi?id=37834 Bug ID: 37834 Summary: RtlSetCurrentDirectory_U prepends "UNC\" for network paths; the resulting path is invalid Product: Wine Version: 1.7.33 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: atakama0512(a)yahoo.com Distribution: --- Created attachment 50382 --> https://bugs.winehq.org/attachment.cgi?id=50382 cmd.exe output showing how UNC\ gets prepended when running cd \\server\share Calling RtlSetCurrentDirectory_U with a network share argument like "\\server\share" sets the current directory to "UNC\server\share". Subsequent calls to GetCurrentDirectory will return the modified path. The resulting path is invalid and unusable: attempting to read the directory or writing a file to it results in ERROR_PATH_NOT_FOUND. The bug can be reproduced using the internal command prompt, as seen in the attachment. >From what I've gathered from the source code, RtlSetCurrentDirectory_U calls RtlDosPathNameToNtPathName_U, which prepends UncPfxW to the supplied path. The last edits to dlls/ntdll/path.c were made in 2003-2004. I stumbled across this behavior while investigating why Total Commander cannot copy files to network shares. The sequence of calls in Total Commander is: SetCurrentDirectory to the network path, then GetCurrentDirectory (which returns the modified path in the form "UNC\server\share") and then it builds the destination parameter by concatenating this path with the destination file name. This gets passed to CopyFileEx, which fails with ERROR_PATH_NOT_FOUND because of the "UNC\" prefix. -- 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 44369] New: cmd's %0 path variables (e.g. %~dp0) wrong inside subroutine call
by wine-bugs＠winehq.org 29 Nov '18

29 Nov '18

https://bugs.winehq.org/show_bug.cgi?id=44369 Bug ID: 44369 Summary: cmd's %0 path variables (e.g. %~dp0) wrong inside subroutine call Product: Wine Version: 3.0-rc6 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: cmd Assignee: wine-bugs(a)winehq.org Reporter: ryan.prichard(a)gmail.com Distribution: --- Test program (C:\bin\workaround.cmd): @echo off call :fix exit /b :fix echo [%0] [%~d0] [%~p0] [%~n0] [%~x0] exit /b Expected behavior (tested on XP): C:\>set PATH=C:\bin;%PATH% C:\>workaround.cmd [:fix] [C:] [\bin\] [workaround] [.cmd] C:\>"workaround.cmd" [:fix] [C:] [\bin\] [workaround] [.cmd] C:\>"w"or"k"aroun"d.c"md [:fix] [C:] [\bin\] [workaround] [.cmd] Behavior on wine-3.0-rc6: c:\>set PATH=C:\bin;%PATH% c:\>workaround.cmd [:fix] [c:] [\] [:fix] [] c:\>"workaround.cmd" [:fix] [c:] [\] [:fix] [] c:\>"w"or"k"aroun"d.c"md [:fix] [c:] [\] [:fix] [] Background: The Android NDK generates wrapper batch files that invoke clang.exe. If the wrapper is invoked from the PATH using double-quotes, then %~dp0 is wrong (when using Windows CMD). A workaround I've found is to evaluate %~dp0 in a subroutine in the batch file. This workaround works with Windows CMD, but breaks with Wine CMD. (It expands to the working directory instead.) See https://github.com/android-ndk/ndk/issues/616#issuecomment-358117090. FWIW: Wine CMD doesn't have the same %~dp0 bugginess as Windows CMD that motivated the GitHub issue I linked to. Wine handles all of the example command lines on that GitHub comment consistently (aside from case differences in the drive letter or the filename extension). If Wine tries to match Windows bug-for-bug, then maybe this too should change. -- 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 45530] New: No$Gba crash when open.
by wine-bugs＠winehq.org 29 Nov '18

29 Nov '18

https://bugs.winehq.org/show_bug.cgi?id=45530 Bug ID: 45530 Summary: No$Gba crash when open. Product: Wine Version: 3.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: wzhy90(a)gmail.com Distribution: --- Created attachment 61927 --> https://bugs.winehq.org/attachment.cgi?id=61927 no$gba ver.2.9a from http://problemkaputt.de/gba.htm Host is linux mint 19, it works on mint 18.3 but after I do a fresh install to mint 19 it crash. I have try stable or devel version, both crash when open. -- 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 43036] New: SetNamedPipeHandleState returns ERROR_ACCESS_DENIED when setting PIPE_NOWAIT
by wine-bugs＠winehq.org 29 Nov '18

29 Nov '18

https://bugs.winehq.org/show_bug.cgi?id=43036 Bug ID: 43036 Summary: SetNamedPipeHandleState returns ERROR_ACCESS_DENIED when setting PIPE_NOWAIT Product: Wine Version: 2.7 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dan-wine(a)berrange.com Distribution: --- In GNULIB, there is code which tries to create an implementation of the POSIX pipe() method for Windows, using the methods _pipe, _get_osfhandle and SetNamedPipeHandleState. This code works when run on real windows systems (i've tried Win2k8 myself), but fails when run under Wine (I've tested versions 2.5 and 2.7 in Fedora), with ERROR_ACCESS_DENIED from the SetNamedPipeHandleState method Since GNULIB code is fairly complex to follow I created this short demo program: $ cat > demo.c <<EOF #include <sys/unistd.h> #include <stdio.h> #include <windows.h> int nonblock(int fd) { HANDLE h = (HANDLE)_get_osfhandle(fd); char errbuf[1024]; DWORD state; if (GetNamedPipeHandleState (h, &state, NULL, NULL, NULL, NULL, 0) == 0) { FormatMessage(FORMAT_MESSAGE_FROM_SYSTEM, NULL, GetLastError(), MAKELANGID(LANG_NEUTRAL, SUBLANG_DEFAULT), errbuf, 1024, NULL); fprintf(stderr, "Failed GetNamedPipeHandleState (%lu) %s", GetLastError(), errbuf); return -1; } if ((state & PIPE_NOWAIT) != 0) { return 0; } state |= PIPE_NOWAIT; if (SetNamedPipeHandleState (h, &state, NULL, NULL) == 0) { FormatMessage(FORMAT_MESSAGE_FROM_SYSTEM, NULL, GetLastError(), MAKELANGID(LANG_NEUTRAL, SUBLANG_DEFAULT), errbuf, 1024, NULL); fprintf(stderr, "Failed SetNamedPipeHandleState (%lu) %s", GetLastError(), errbuf); return -1; } return 0; } int main(int argc, char **argv) { int fd[2]; if (_pipe(fd, 4096, 0) < 0) { fprintf(stderr, "Failed to create pipe\n"); return -1; } if (nonblock(fd[0]) < 0){ fprintf(stderr, "Could not set non-blocking on fd[0]\n"); return -1; } if (nonblock(fd[1]) < 0){ fprintf(stderr, "Could not set non-blocking on fd[1]\n"); return -1; } fprintf(stderr, "Created non-blocking pipe pair\n"); } EOF $ i686-w64-mingw32-gcc -Wall -mconsole -o pipe.exe pipe.c $ ./pipe.exe fixme:winediag:start_process Wine Staging 2.7 is a testing version containing experimental patches. fixme:winediag:start_process Please mention your exact version when filing bug reports on winehq.org. fixme:sync:GetNamedPipeHandleStateW 0x2c 0x61f8f8 (nil) (nil) (nil) (nil) 0: semi-stub Failed SetNamedPipeHandleState (5) Access denied. Could not set non-blocking on fd[0] Strangely, this only seems to fail on fd[0] - if I let it run on fd[1] it will work. The original GNULIB code I hit the problem on is here: http://git.savannah.gnu.org/cgit/gnulib.git/tree/lib/pipe2.c http://git.savannah.gnu.org/cgit/gnulib.git/tree/lib/nonblocking.c The Fedora Wine 2.7 package I tested on was built with these sources: SHA512 (wine-2.7.tar.xz) = 1e61b9a4aa1f5f42fb27d11d5254a9ba90f348ad9c4d1ddd4b5da47cd7de638290a20accf7447db9c0e4ced4c2144497cdf5fc906a5eac60e923dabb61f65d3a SHA512 (wine-2.7.tar.xz.sign) = b03f4376b10bd8ea66e5e6fc0862a4f948e009862a374677c326744b31c9d9fdcf1efd3b789149fcb6fe617f9c75b1b47d61f884e06e8c0fe16633a99911b667 SHA512 (wine-staging-2.7.tar.gz) = 0abc89af701ae1b95c0eb08e72894c7bc40bdfe792e05b8af9282eab8407bb90b7dfcd4eb3a193a88759ce5d6ea6c2aa9696cac2d744f543c92529bb0d2636ee -- 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 45529] New: Custom color scheme applied but wine not respecting current text color of scheme on window columns and statusbar.
by wine-bugs＠winehq.org 29 Nov '18

29 Nov '18

https://bugs.winehq.org/show_bug.cgi?id=45529 Bug ID: 45529 Summary: Custom color scheme applied but wine not respecting current text color of scheme on window columns and statusbar. Product: Wine Version: 3.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: uxtheme Assignee: wine-bugs(a)winehq.org Reporter: mt_talpur(a)yahoo.com Distribution: --- Created attachment 61923 --> https://bugs.winehq.org/attachment.cgi?id=61923 shows current issue with color scheme applied. When changing the color scheme via registry it does change overall looks of window elements but the text of window columns and statusbar remains black no matter what color scheme is applied though it should respect the currently used text color On windows this does not happen. -- 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 14