https://bugs.winehq.org/show_bug.cgi?id=56620
Bug ID: 56620 Summary: Netgear Powerline Utility 3: File not found Product: Wine Version: 9.7 Hardware: x86-64 URL: https://web.archive.org/web/20221023012754/https://www .downloads.netgear.com/files/GDC/XAVN2001/NETGEAR_Powe rline_Setup_V3.1.0.4_230-10802-06.zip OS: Linux Status: NEW Keywords: download, regression Severity: normal Priority: P2 Component: shell32 Assignee: wine-bugs@winehq.org Reporter: imwellcushtymelike@gmail.com CC: yshuiv7@gmail.com Regression SHA1: 85d029e3b01f6dd35a86cc07796af982d66e4a03 Distribution: Ubuntu
Created attachment 76380 --> https://bugs.winehq.org/attachment.cgi?id=76380 "File not found" dialog
After installing the Netgear Powerline Utility v3, the app loads without any issue.
However, on second load, a dialog window pops up showing "File not found" three times. The executable NamePipeServer.exe fails to load, but the application loads nonetheless. The app isn't usable due to other bugs.
This started with commit 85d029e3b01f6dd35a86cc07796af982d66e4a03.
85d029e3b01f6dd35a86cc07796af982d66e4a03 is the first bad commit commit 85d029e3b01f6dd35a86cc07796af982d66e4a03 Author: Yuxuan Shui yshui@codeweavers.com Date: Mon Mar 18 18:32:00 2024 +0000
shell32: Rely solely on SHELL_FindExecutable for ShellExecute.
This does two things:
1. ShellExecute no longer searches in the directory where the current executable is in. 2. We always CreateProcess with a fully qualified path, so we CreateProcess won't do its own path resolution.
Serendipitously this also fixes some existing todos in tests.
Nothing is printed in the console.
Reverting this commit in current git resolves the issue.
Tried with both a 32- and 64-bit wineprefix.
$ sha1sum NETGEAR_Powerline_Setup_V3.1.0.4_230-10802-06.exe 5a7506b35fb1e2b70f300b9cfc8df417e9d5f651 NETGEAR_Powerline_Setup_V3.1.0.4_230-10802-06.exe
https://bugs.winehq.org/show_bug.cgi?id=56620
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Fixed by SHA1| |3a5e01927fc9edce660b7f4c449 | |5c44550f702f2 Resolution|--- |FIXED
--- Comment #1 from Alexandre Julliard julliard@winehq.org --- It should be fixed by 3a5e01927fc9edce660b7f4c4495c44550f702f2.
https://bugs.winehq.org/show_bug.cgi?id=56620
Ken Sharp imwellcushtymelike@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |UNCONFIRMED Resolution|FIXED |--- Ever confirmed|1 |0
--- Comment #2 from Ken Sharp imwellcushtymelike@gmail.com --- Still occurs in current git.
wine "c:\Program Files\netgear\netgear powerline utility\netgear_powerline_utility.exe"
https://bugs.winehq.org/show_bug.cgi?id=56620
Ken Sharp imwellcushtymelike@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever confirmed|0 |1
--- Comment #3 from Ken Sharp imwellcushtymelike@gmail.com --- Forgot to add the console output:
0244:fixme:win:NtUserFlashWindowEx 0x31f3d0 - semi-stub QEventDispatcherWin32::unregisterTimer: invalid argument vfnRecordDevices open file error
https://bugs.winehq.org/show_bug.cgi?id=56620
--- Comment #4 from Alexandre Julliard julliard@winehq.org --- You need to run it from the app directory.
https://bugs.winehq.org/show_bug.cgi?id=56620
--- Comment #5 from Ken Sharp imwellcushtymelike@gmail.com --- Ah yes, that works. Is that not a bug then?
https://bugs.winehq.org/show_bug.cgi?id=56620
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords|regression | Status|NEW |RESOLVED Regression SHA1|85d029e3b01f6dd35a86cc07796 | |af982d66e4a03 | Resolution|--- |INVALID
--- Comment #6 from Alexandre Julliard julliard@winehq.org --- No there's no bug, it behaves exactly the same way on Windows.
https://bugs.winehq.org/show_bug.cgi?id=56620
Ken Sharp imwellcushtymelike@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #7 from Ken Sharp imwellcushtymelike@gmail.com --- So it does. I don't know what was going on during the bisect in Comment #0. Sorry for the noise!