July 2020 - Wine-bugs - list.winehq.org

[Bug 45962] New: FileMaker Pro 16 crashes on startup
by wine-bugs＠winehq.org 17 Mar '21

17 Mar '21

https://bugs.winehq.org/show_bug.cgi?id=45962 Bug ID: 45962 Summary: FileMaker Pro 16 crashes on startup Product: Wine Version: 3.17 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: larrycoleman.email(a)gmail.com Distribution: --- Created attachment 62513 --> https://bugs.winehq.org/attachment.cgi?id=62513 The "Show Details" from when FileMaker crashes I am running on Ubuntu 16.04. I installed WineHQ 3.17. FileMaker Pro requires .Net Framework. I used Winetricks to install .NET Framework 4.6.1. I then installed FileMaker Pro 16. When trying to run FileMaker, I get a "Program Error" message "The program FileMaker Pro.exe has encountered a serious problem and needs to close. We are sorry for the inconvenience." -- 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 13

[Bug 42443] New: MyDiff Program doesn't launch
by wine-bugs＠winehq.org 17 Mar '21

17 Mar '21

https://bugs.winehq.org/show_bug.cgi?id=42443 Bug ID: 42443 Summary: MyDiff Program doesn't launch Product: Wine Version: 1.6.2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: le.pocher.julien(a)gmail.com Distribution: --- Created attachment 57275 --> https://bugs.winehq.org/attachment.cgi?id=57275 Bug backtrace The executable MyDiff.exe file won't run. See backtrace. -- 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 12

[Bug 33287] New: Filemaker Pro12 crashes when opening database file
by wine-bugs＠winehq.org 17 Mar '21

17 Mar '21

http://bugs.winehq.org/show_bug.cgi?id=33287 Bug #: 33287 Summary: Filemaker Pro12 crashes when opening database file Product: Wine Version: 1.4.1 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: jmeador(a)momentapharma.com Classification: Unclassified I can install Filemaker Pro 12 with a valid serial number into BioLinux 7, which is Ubuntu 12.04. Wine was installed as 4.1 via the Ubuntu Software Center and I cannot get the dev version of 1.5 to install via this or the commandline. It says that the binaries are not available. When running from the commandline, I get this output: :~$ wine "c:\program files (x86)\FileMaker\FileMaker Pro 12\FileMaker Pro.exe" p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory When I look for this directory in /usr/lib/i386-linux-gnu/ there are no files or folders called pkcs11 so perhaps this is missing from the wine1.4 installer? When installing, the installer gets to the end and then crashes and says the registration program cannot run, however, the program will start and appears to run ok until you open a database file, and I have tried several. Once I try to open a file, it crashes. The FileMaker Pro binary and other files are installed into /Program File (x86)/FileMaker/... I am attaching the backtrace file as well which was obtained from running the program from the graphical method. The computer is an HP Xeon processor with 64-bit Ubuntu 12.04 and 128 GB ram Thanks for any help you can provide. -- 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.

2 16

[Bug 39288] New: Filemaker Pro 12 crashes when trying to open a Filemaker database file
by wine-bugs＠winehq.org 17 Mar '21

17 Mar '21

https://bugs.winehq.org/show_bug.cgi?id=39288 Bug ID: 39288 Summary: Filemaker Pro 12 crashes when trying to open a Filemaker database file Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ben(a)berwers.org Distribution: --- Created attachment 52366 --> https://bugs.winehq.org/attachment.cgi?id=52366 Filemaker Pro 12 crashes when trying to open a Filemaker file. Filemaker Pro 12 has a serious problem and stops when I try to open any file. Please see attached backtrace report when opening a testfile. By the way Filemaker Pro 6 works fine. Unfortunately I cannot switch back to the 6-version. Hope you can help me, what goes wrong. Thanks in advance, Ben Berwers -- 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 49328] New: Lego raiders crash with native d3drm and native amstream
by WineHQ Bugzilla 17 Mar '21

17 Mar '21

https://bugs.winehq.org/show_bug.cgi?id=49328 Bug ID: 49328 Summary: Lego raiders crash with native d3drm and native amstream Product: Wine Version: 5.10 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winegstreamer Assignee: wine-bugs(a)winehq.org Reporter: jeremielapuree(a)yahoo.fr Distribution: Ubuntu Created attachment 67360 --> https://bugs.winehq.org/attachment.cgi?id=67360 console ouput of the crash With native d3drm and native amstream, lego raiders crash. -- 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 42103] New: VSCode.exe v1.8.1 crash
by wine-bugs＠winehq.org 17 Mar '21

17 Mar '21

https://bugs.winehq.org/show_bug.cgi?id=42103 Bug ID: 42103 Summary: VSCode.exe v1.8.1 crash Product: Wine Version: 1.8.6 Hardware: x86 OS: FreeBSD Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: igeo.cu(a)gmail.com Unhandled exception: page fault on read access to 0x00000004 in 32-bit code (0x03486f49). Register dump: CS:0033 SS:003b DS:003b ES:003b FS:0013 GS:001b EIP:03486f49 ESP:0032fda0 EBP:0032fdcc EFLAGS:00010246( R- -- I Z- -P- ) EAX:00000000 EBX:62956770 ECX:00000000 EDX:0032fdc0 ESI:00000000 EDI:0013d498 Stack dump: 0x0032fda0: 62956770 00000003 00000002 0013d498 0x0032fdb0: 0013d4ac 0013d4ac 004b3989 00000000 0x0032fdc0: 00000000 00000000 00000014 0032fde4 0x0032fdd0: 03486e75 00000094 00000003 00000094 0x0032fde0: 00000094 0032fe00 034863ce 0013cef0 0x0032fdf0: 0032fe88 00000000 628f0000 00000007 Backtrace: =>0 0x03486f49 in code (+0x3086f49) (0x0032fdcc) 1 0x03486e75 in code (+0x3086e74) (0x0032fde4) 2 0x034863ce in code (+0x30863cd) (0x0032fe00) 3 0x01c88df6 in code (+0x1888df5) (0x0032fe14) 4 0x00472539 in code (+0x72538) (0x0032fea4) 5 0x02a823d2 in code (+0x26823d1) (0x0032fef0) 6 0x6293d32c call_process_entry+0xb() in kernel32 (0x0032ff08) 7 0x6293ff8b start_process+0xaa() in kernel32 (0x0032ff40) 8 0x6287f270 call_thread_func_wrapper+0xb() in ntdll (0x0032ff50) 9 0x628814b9 call_thread_func+0x78() in ntdll (0x0032ffb4) 10 0x6287f24e call_thread_entry_point+0x11() in ntdll (0x0032ffd4) 11 0x6285843c start_process+0x2b() in ntdll (0x0032ffe8) 12 0x6202dd2d wine_call_on_stack+0x1c() in libwine.so.1 (0x00000000) 13 0x6202ddec wine_switch_to_stack+0x2b() in libwine.so.1 (0xffffc398) 14 0x6285717f LdrInitializeThunk+0x2ce() in ntdll (0xffffc3e8) 15 0x6293f3de __wine_kernel_init+0x208d() in kernel32 (0xffffd2f0) 16 0x62858e7b __wine_process_init+0x59a() in ntdll (0xffffd3f8) 17 0x6202cdd0 wine_init+0x36f() in libwine.so.1 (0xffffd458) 18 0x60000ccb main+0x7a() in <wine-loader> (0xffffd894) 19 0x60000b9a _start1+0x139() in <wine-loader> (0xffffd8b8) 20 0x60000a58 _start+0x17() in <wine-loader> (0xffffd8dc) 0x03486f49: cmpw 0x4(%ecx),%ax Modules: Module Address Debug info Name (104 modules) PE 400000- 4126000 Export code PE 4130000- 42e5000 Deferred ffmpeg PE 10000000-10ca9000 Deferred node PE 537d0000-537f8000 Deferred uiautomationcore ELF 60000000-60002000 Dwarf <wine-loader> ELF 62001000-6201d000 Deferred ld-elf32.so.1 ELF 62026000-621d9000 Dwarf libwine.so.1 ELF 621d9000-621fd000 Deferred libthr.so.3 ELF 621fd000-62373000 Deferred libc.so.7 ELF 62387000-623b2000 Deferred libm.so.5 ELF 623c6000-623d9000 Deferred psapi<elf> \-PE 623d0000-623d9000 \ psapi ELF 623d9000-623f1000 Deferred version<elf> \-PE 623e0000-623f1000 \ version ELF 623f1000-623fb000 Deferred libprocstat.so.1 ELF 62800000-628da000 Dwarf ntdll<elf> \-PE 62810000-628da000 \ ntdll ELF 628da000-629e7000 Dwarf kernel32<elf> \-PE 628f0000-629e7000 \ kernel32 ELF 629e7000-62a23000 Deferred ws2_32<elf> \-PE 629f0000-62a23000 \ ws2_32 ELF 62a23000-62b2e000 Deferred gdi32<elf> \-PE 62a30000-62b2e000 \ gdi32 ELF 62b2e000-62b9a000 Deferred advapi32<elf> \-PE 62b40000-62b9a000 \ advapi32 ELF 62b9a000-62cd7000 Deferred user32<elf> \-PE 62bb0000-62cd7000 \ user32 ELF 62cd7000-62cfc000 Deferred iphlpapi<elf> \-PE 62ce0000-62cfc000 \ iphlpapi ELF 62cfc000-62d14000 Deferred libelf.so.2 ELF 62d14000-62d23000 Deferred libkvm.so.7 ELF 62d23000-62d35000 Deferred libutil.so.9 ELF 62d35000-62d4c000 Deferred userenv<elf> \-PE 62d40000-62d4c000 \ userenv ELF 62d4c000-62d96000 Deferred winmm<elf> \-PE 62d50000-62d96000 \ winmm ELF 62d96000-62eac000 Deferred ole32<elf> \-PE 62db0000-62eac000 \ ole32 ELF 62eac000-62f23000 Deferred rpcrt4<elf> \-PE 62ec0000-62f23000 \ rpcrt4 ELF 62f23000-62f45000 Deferred msacm32<elf> \-PE 62f30000-62f45000 \ msacm32 ELF 62f45000-63035000 Deferred comctl32<elf> \-PE 62f50000-63035000 \ comctl32 ELF 63035000-63095000 Deferred comdlg32<elf> \-PE 63040000-63095000 \ comdlg32 ELF 63095000-6326a000 Deferred shell32<elf> \-PE 630a0000-6326a000 \ shell32 ELF 6326a000-632d5000 Deferred shlwapi<elf> \-PE 63280000-632d5000 \ shlwapi ELF 632d5000-6330e000 Deferred winspool<elf> \-PE 632e0000-6330e000 \ winspool ELF 63317000-63378000 Deferred wininet<elf> \-PE 63320000-63378000 \ wininet ELF 63378000-6338d000 Deferred libz.so.6 ELF 6338d000-633ac000 Deferred mpr<elf> \-PE 63390000-633ac000 \ mpr ELF 633ac000-6345c000 Deferred msvcrt<elf> \-PE 633c0000-6345c000 \ msvcrt ELF 6345c000-63576000 Deferred oleaut32<elf> \-PE 63470000-63576000 \ oleaut32 ELF 63576000-635b2000 Deferred oleacc<elf> \-PE 63580000-635b2000 \ oleacc ELF 635b2000-63612000 Deferred dbghelp<elf> \-PE 635c0000-63612000 \ dbghelp ELF 63612000-63627000 Deferred dwmapi<elf> \-PE 63620000-63627000 \ dwmapi ELF 63627000-63668000 Deferred usp10<elf> \-PE 63630000-63668000 \ usp10 ELF 63668000-6368a000 Deferred imm32<elf> \-PE 63670000-6368a000 \ imm32 ELF 6368a000-636cc000 Deferred libncurses.so.8 ELF 636cc000-6375e000 Deferred libfreetype.so.6 ELF 6375e000-63770000 Deferred libbz2.so.4 ELF 63770000-637b0000 Deferred libfontconfig.so.1 ELF 637b0000-637d3000 Deferred libexpat.so.1 ELF 638de000-638f1000 Deferred api-ms-win-core-synch-l1-2-0<elf PE 638e0000-638f1000 Deferred api-ms-win-core-synch-l1-2-0 ELF 638f1000-63904000 Deferred api-ms-win-core-fibers-l1-1-1<el PE 63900000-63904000 Deferred api-ms-win-core-fibers-l1-1-1 PE 63904000-63917000 Deferred api-ms-win-core-localization-l1- PE 63910000-63917000 Deferred api-ms-win-core-localization-l1-C:\windows\system32\api-ms-win-core-localization-l1-2-1.dll ELF 63917000-639a2000 Deferred winex11<elf> \-PE 63920000-639a2000 \ winex11 ELF 639a2000-639b1000 Deferred libxext.so.6 ELF 639b1000-63acf000 Deferred libx11.so.6 ELF 63acf000-63aef000 Deferred libxcb.so.1 ELF 63aef000-63af2000 Deferred libxau.so.6 ELF 63af2000-63af4000 Deferred libpthread-stubs.so.0 ELF 63af4000-63af9000 Deferred libxdmcp.so.6 ELF 63af9000-63afc000 Deferred libxinerama.so.1 ELF 63afc000-63b01000 Deferred libxxf86vm.so.1 ELF 63b01000-63b09000 Deferred libxrender.so.1 ELF 63b09000-63b12000 Deferred libxrandr.so.2 ELF 63b12000-63b15000 Deferred libxcomposite.so.1 ELF 63b15000-63b23000 Deferred libxi.so.6 ELF 63b23000-63b2d000 Deferred libxcursor.so.1 ELF 63b2d000-63b32000 Deferred libxfixes.so.3 ELF 63b34000-63b69000 Deferred uxtheme<elf> \-PE 63b40000-63b69000 \ uxtheme ELF 63b69000-63b7c000 Deferred api-ms-win-core-string-l1-1-0<el PE 63b70000-63b7c000 Deferred api-ms-win-core-string-l1-1-0 ELF 63b7c000-63b8f000 Deferred api-ms-win-core-datetime-l1-1-1< PE 63b80000-63b8f000 Deferred api-ms-win-core-datetime-l1-1-1 Threads: process tid prio (all id:s are in hex) 00000008 (D) C:\Program Files\Microsoft VS Code\Code.exe 00000009 0 <== 0000000e services.exe 00000023 0 00000022 0 0000001c 0 00000014 0 00000010 0 0000000f 0 00000012 winedevice.exe 00000019 0 00000018 0 00000013 0 0000001a plugplay.exe 0000001f 0 0000001e 0 0000001b 0 00000020 winedevice.exe 00000025 0 00000024 0 00000021 0 00000028 explorer.exe 0000002c 0 0000002b 0 0000002a 0 00000029 0 System information: Wine build: wine-1.8.6 Platform: i386 Version: Windows 10 Host system: FreeBSD Host version: 11.0-RELEASE-p2 -- 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 8

[Bug 44355] New: FaceIt client : www.faceit.com/client
by wine-bugs＠winehq.org 17 Mar '21

17 Mar '21

https://bugs.winehq.org/show_bug.cgi?id=44355 Bug ID: 44355 Summary: FaceIt client : www.faceit.com/client Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: adil3.7896(a)gmail.com Distribution: --- Created attachment 60250 --> https://bugs.winehq.org/attachment.cgi?id=60250 Backtrace of the issue The FaceIt client was running properly when it suddenly closed with the following message: ...have to close the application due to Database issues. Please check Wine Application Database for more information. Here's the backtrace (attachment) please fix? -- 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 41713] New: Explorer.exe is wrong when started from the process creating the Wine prefix
by wine-bugs＠winehq.org 17 Mar '21

17 Mar '21

https://bugs.winehq.org/show_bug.cgi?id=41713 Bug ID: 41713 Summary: Explorer.exe is wrong when started from the process creating the Wine prefix Product: Wine Version: 1.9.8 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- To reproduce this do the following: rm -rf ~/.wine cd dlls/shell32/tests rm shelldispatch.ok make shelldispatch.ok This normally results in the following failure: shelldispatch.c:624: Test failed: got 0x80040152 Which corresponds to the following line: ok(hr == S_OK, "got 0x%08x\n", hr); /* TODO: remove when explorer startup with clean prefix is fixed */ if (hr != S_OK) return; The workaround is to ensure the Wine prefix has been created before running the test: rm -rf ~/.wine ./wine hostname ./server/wineserver -w cd dlls/shell32/tests rm shelldispatch.ok make shelldispatch.ok Note that wt-daily is now implementing this workaround (see https://github.com/fgouget/wt-daily) -- 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 13

[Bug 45232] New: TIDAL can't be installed with exe installer
by wine-bugs＠winehq.org 17 Mar '21

17 Mar '21

https://bugs.winehq.org/show_bug.cgi?id=45232 Bug ID: 45232 Summary: TIDAL can't be installed with exe installer Product: Wine Version: 3.8 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ieframe Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- Created attachment 61461 --> https://bugs.winehq.org/attachment.cgi?id=61461 Wine log The program instantly crashes, I assume due to the missing ieframe interface. Needs wine-staging patches, else it complains about being run as administrator. -- 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 7

[Bug 45749] New: Visual Studio 2017 Installer fails due to node.js/ libuv listen(named pipe) error
by wine-bugs＠winehq.org 17 Mar '21

17 Mar '21

https://bugs.winehq.org/show_bug.cgi?id=45749 Bug ID: 45749 Summary: Visual Studio 2017 Installer fails due to node.js/libuv listen(named pipe) error Product: Wine Version: 3.14 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jimbo1qaz(a)gmail.com Distribution: --- Created attachment 62190 --> https://bugs.winehq.org/attachment.cgi?id=62190 Visual Studio Installer logs (mostly useless) Running Kubuntu 18.04 64-bit. I created a 32-bit .wine32 prefix, installed dotnet46 via winetricks, then the Build Tools for Visual Studio installer (https://visualstudio.microsoft.com/downloads/#build-tools-for-visual-studio… ) (which shares the core with VS2017 installer. It's written in node.js and involves multiple processes communicating via what the source describes as "pipe"s). The error is "Hub Controller process exited prematurely with exit code 1 (NodeUncaughtFatalException)." Interestingly, the installer's source is user-readable and located in WINEPREFIX / drive_c/Program Files/Microsoft Visual Studio/Installer/resources/app/node_modules/microsoft-servicehub/host/. I was able to edit the .js files to add control flow logging: const fs = require('fs'); function logg(val, args){ fs.writeFileSync("C:\\"+process.hrtime()[1] + '_'+val, ""+args, function(err) {}); } Installer seems to be codenamed "microsoft-servicehub". Strangely, many of the Installer files appear to test for Windows and/or *nix, despite VS being Windows-only. It also references open-source VS Code, but I was unable to find any hits when Googling for quoted strings. ---------- The error message "Hub Controller process exited prematurely with exit code" is raised from within "drive_c/Program Files/Microsoft Visual Studio/Installer/resources/app/node_modules/microsoft-servicehub/controllerConnection.js": ControllerConnection.prototype.startController `var connectPromise` fails, calling `function (err)` to spawn a process (which crashes). ControllerConnection.prototype.onControllerProcessExited is responsible for noticing the process has terminated, and raising the exception. --------- The actual crash originates from "drive_c/Program Files/Microsoft Visual Studio/Installer/resources/app/node_modules/microsoft-servicehub/host/HubController.js". HubController.js is executed by several distinct processes, and `process.pid` is the same within `function HubController()` and the global scope. I systematically replaced all calls to `logger.error()` (info, etc.) to `logg()` (since Logger.error() called within subprocess did not show up in Visual Studio's debug logs). I get two sequentially numbered files, 1 millisecond apart: "429988399_Successfully started server on pipe 5d74f51d8cc5d690c261c26d3e9e3408e060bd352875558b9320be9c213e0610" "430873100_Terminating controller due to some unknown error: " with contents "listen EINVAL \\?\pipe\5d74f51d8cc5d690c261c26d3e9e3408e060bd352875558b9320be9c213e0610" This error is thrown by `function retryStartServer`. `e.code` is EINVAL, while the code only handles `e.code === ec.EADDRINUSE.code`. Looking at https://stackoverflow.com/questions/11040460/get-the-listen-einval-when-sta… suggests: > > EINVAL The socket is already connected. > Make sure something isn't already listening on that port. `man errno` suggests otherwise: > EINVAL Invalid argument (POSIX.1-2001). Adding `|| e.code === ec.EINVAL.code` and commenting `process.platform === 'win32' ||` sends the installer into an endless "kill and restart HubController" loop, which isn't what we want. Extra notes on control flow at https://gist.github.com/jimbo1qaz/1c972422fd5c31706920b9be5c2a0f42#server -------- The `EINVAL` error comes with a node.js stack trace: https://gist.github.com/jimbo1qaz/1c972422fd5c31706920b9be5c2a0f42#file-net… (The hexadecimal path originates from https://gist.github.com/jimbo1qaz/1c972422fd5c31706920b9be5c2a0f42#determin… ) https://github.com/nodejs/node/blob/68dff4a67b7222770f90fc5d9bdd884f8db4a24… `const ex = new Error(`${syscall} ${code}${details}`);` "listen EINVAL \\?\pipe\5d74f51d8cc5d690c261c26d3e9e3408e060bd352875558b9320be9c213e0610" I think the call which failed is `listen`, which returns EINVAL for some reason. ------------ Comparing my stack trace with node.js source code (node.dll 8.9.3): `Server.listen (net.js:1487:5)` = https://github.com/nodejs/node/blob/v8.9.3/lib/net.js#L1487 - listenInCluster(server=this, address=pipeName, port=-1, addressType=-1, backlog=backlog, fd=undefined, exclusive=options.exclusive); `listenInCluster (net.js:1392:12)` = https://github.com/nodejs/node/blob/v8.9.3/lib/net.js#L1392 - server._listen2(=address, =port, =addressType, =backlog, =fd); Unpeeling layers of abstraction on top of Windows named pipes: `Server.setupListenHandle [as _listen2] (net.js:1351:14)` = https://github.com/nodejs/node/blob/v8.9.3/lib/net.js#L1351 (Bullet points are not in stack trace, but I assume they executed) - `handle = new Pipe(PipeConstants.SERVER);` https://github.com/nodejs/node/blob/v8.9.3/lib/net.js#L1267 - `const { Pipe } = process.binding('pipe_wrap');` which refers to C++ code at https://github.com/nodejs/node/blob/v8.9.3/src/pipe_wrap.cc - pipes are handled by https://github.com/libuv/libuv - `var err = this._handle.listen(backlog || 511);` is the operation which fails = https://github.com/nodejs/node/blob/8a44289089a08b7b19fa3c4651b5f1f5d1edd71… - Routes to https://github.com/nodejs/node/blob/v8.9.3/src/pipe_wrap.cc#L154 - which calls uv_listen(). `return uv_translate_sys_error(err);` and EINVAL is located at https://github.com/libuv/libuv/blob/v1.x/src/win/error.c#L101 ... There are 7 Win32 errors all mapping to UV_EINVAL==EINVAL, but only WSAEINVAL can happen. - uv_listen() either [assert(0) and sets err=ERROR_INVALID_PARAMETER] (I hope not), calls uv_tcp_listen (I hope not) - Most likely calls uv_pipe_listen() = https://github.com/libuv/libuv/blob/1391a3d9d0996fcf1a116a9c6c58e8b1c730319… - It has 4 return paths, only `if (!(handle->flags & UV_HANDLE_BOUND)) { return WSAEINVAL;` is happening = https://github.com/libuv/libuv/blob/1391a3d9d0996fcf1a116a9c6c58e8b1c730319… - What initializes `handle->flags` without |=UV_HANDLE_BOUND? ok i'm getting a headache -- 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 20