https://bugs.winehq.org/show_bug.cgi?id=52958
Bug ID: 52958 Summary: vague error messaged "File not found" and "Invalid name" Product: Wine Version: 4.0.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: martijn@bytehazard.com Distribution: ---
Please add a more descriptive error message for the following errors:
"File not found" [ OK ]
and
"Invalid name" [ OK ]
Both with 'stop' icon, and shown 10 times in succession.
I *think* they are triggered via "ShellExecute" in my own VB6 legacy application. Sorry I can't be more specific than that because the errors are so vague.
For example, it would be tremendously helpful *which* file is not found (Wine/OS executable/dll file, the targeted command/executable, the file passed to targeted command/executable, or if it is an error triggered by the potentially launched application or Wine/OS?
Same for "invalid name". Invalid name what? Name of executable? Drive letter? Drive mapping? Folder name? File name? Extension name? Application name? OS name?
The only hint I have is that this message dialogue is Wine styled and thus not something triggered outside Wine environment. Maybe they are not even related to ShellExecute.
I'm aware this is probably the most useless bug report ever, I just want to encourage any developer who is reading this to write more useful error messages in the future. It has cost both of us more time to write/read this ticket than to improve the code that displays these errors. And I'm nowhere near finding a solution for my problem after hours and hours...
No hard feelings, I absolutely love Wine! Thanks for your efforts!
https://bugs.winehq.org/show_bug.cgi?id=52958
Zeb Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com
--- Comment #1 from Zeb Figura z.figura12@gmail.com --- I don't think Wine itself is triggering these message boxes; it's just drawing them with the text requested by the application. Unless they have more details on Windows in the same scenario, there's nothing we can do.
https://bugs.winehq.org/show_bug.cgi?id=52958
--- Comment #2 from martijn@bytehazard.com --- It is definitely not the Windows application triggering it, because I wrote it. The source code doesn't even contain the error messages.
I think it they are produced by the Wine "cmd" or "start" process.
I'm trying to launch a native Linux application via ShellExecute API, which never starts. So it's definitely produced by Wine. Or maybe indirectly if by error some file association is triggered and some other application is invoked, but this is in an otherwise empty prefix (and no visible or invisible Windows process is started in the process either, AFAIK).
I also found these Wine users reporting the exact same error messages: https://forum.winehq.org/viewtopic.php?t=17941 https://forum.winehq.org/viewtopic.php?t=11946
I'll try searching the Wine source code to find out what component this is related to.
Thanks!
https://bugs.winehq.org/show_bug.cgi?id=52958
--- Comment #3 from Nikolay Sivov bunglehead@gmail.com --- It's probably produced by ShellExecute().
https://bugs.winehq.org/show_bug.cgi?id=52958
--- Comment #4 from Zeb Figura z.figura12@gmail.com --- Ah, so I'm wrong. It's from do_error_dialog() in dlls/shell32/shlexec.c.
https://bugs.winehq.org/show_bug.cgi?id=52958
Ken Sharp imwellcushtymelike@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download, source