[Bug 53698] New: winemenubuilder "could not be started"
https://bugs.winehq.org/show_bug.cgi?id=53698 Bug ID: 53698 Summary: winemenubuilder "could not be started" Product: Wine Version: 7.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: cmd Assignee: wine-bugs(a)winehq.org Reporter: hi-angel(a)yandex.ru Distribution: --- Wiki claims one can create a menu entry for an .lnk file by running winemenubuilder https://wiki.winehq.org/Winemenubuilder However, running winemenubuilder with any arguments (whether it's the ones from the wiki or just a simple `--help`) results in same errors "ShellExecuteEx failed: File not found." It is worth noting that the exact same text is printed if you execute a `wine foo`, which means that wine apparently somehow doesn't see winemenubuilder. Same thing happens if you execute explicitly `wine ~/.wine/drive_c/windows/system32/winemenubuilder.exe --help` # Steps to reproduce wine winemenubuilder --help # Expected Either a help message or an error about invalid argument # Actual 0084:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 0084:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 0084:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 0084:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 Application could not be started, or no application associated with the specified file. ShellExecuteEx failed: File not found. # Additional information OS: Fedora 36 Wine repository is used the official one by winehq -- 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.
https://bugs.winehq.org/show_bug.cgi?id=53698 Ken Sharp <imwellcushtymelike(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Component|cmd |-unknown Severity|normal |trivial Status|UNCONFIRMED |NEEDINFO Keywords| |download, source --- Comment #1 from Ken Sharp <imwellcushtymelike(a)gmail.com> --- winemenubuilder is looking for a filename. --help is not a filename.
File not found.
As an enhancement, maybe, it could check the command line for (invalid) options, but using it incorrectly is not a bug in the software. Please show the output when an actual filename is passed (and exists). -- 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.
https://bugs.winehq.org/show_bug.cgi?id=53698 --- Comment #2 from Konstantin Kharlamov <hi-angel(a)yandex.ru> --- (In reply to Ken Sharp from comment #1)
winemenubuilder is looking for a filename. --help is not a filename.
File not found.
As an enhancement, maybe, it could check the command line for (invalid) options, but using it incorrectly is not a bug in the software.
Please show the output when an actual filename is passed (and exists).
Sure: λ touch 1 λ wine winemenubuilder ./1 […fixmes here…] Application could not be started, or no application associated with the specified file. ShellExecuteEx failed: File not found. As I mentioned in the 1st post, really anything you pass to winemenubuilder results in these errors, so I don't think it even tries to start `winemenubuilder` — the error really looks like wine isn't finding the app. -- 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.
participants (1)
-
WineHQ Bugzilla