[Bug 47775] New: Wine `start` doesn't support launching files with a full UNIX path specified

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=47775

Bug ID: 47775
           Summary: Wine `start` doesn't support launching files with a
                    full UNIX path specified
           Product: Wine
           Version: 4.16
          Hardware: x86
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: wineserver
          Assignee: [e-mail]
          Reporter: [e-mail]
      Distribution: ---

Steps to reproduce:

1) Download any MSI file
2) Run it this way:

$ wine start /full/path/to/app.msi

Get this error

0009:err:start:wmain Unknown option 'L"/full/path/to/app.msi"'

[Bug 47775] Wine `start` doesn't support launching files with a full UNIX path specified

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=47775

--- Comment #1 from Artem S. Tashkinov  ---
Why do I need this. I want to setup a binfmt_misc handler for MSI files:

# MSI Windows Installer
:windowsMSI:E::msi::/opt/wine/bin/start:

where start is a copy of any virtual wine application (e.g. winepath).

Alas, my idea doesn't work. Of course, I could try stripping the full path in
my start handler but it looks like a lot of unnecessary work.

[Bug 47775] Wine `start` doesn't support launching files with a full UNIX path specified

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=47775

--- Comment #2 from Artem S. Tashkinov  ---
Strangely wine itself can launch EXE files with a full path specified with no
issues.

[Bug 47775] Wine `start` doesn't support launching files with a full UNIX path specified

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=47775

Alexandre Julliard  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |INVALID
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #3 from Alexandre Julliard  ---
Use wine start /unix.

[Bug 47775] Wine `start` doesn't support launching files with a full UNIX path specified

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=47775

--- Comment #4 from Artem S. Tashkinov  ---
(In reply to Alexandre Julliard from comment #3)
> Use wine start /unix.

I'm curious how difficult it would be to get away with using this option and
parse an argument automatically - it doesn't look to be difficult, e.g.

/full/path

or

C:\Windows\Path

are quite distinct.

[Bug 47775] Wine `start` doesn't support launching files with a full UNIX path specified

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=47775

--- Comment #5 from Artem S. Tashkinov  ---
Anyways, if anyone finds this bug report here's how I solved it for myself:

$ cat /opt/wine/bin/winestart

#!/bin/sh
wine start /unix "$@"

[Bug 47775] Wine `start` doesn't support launching files with a full UNIX path specified

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=47775

--- Comment #6 from Alexandre Julliard  ---
The problem is not Windows paths, but start takes various options that start
with /, so there are ambiguous cases.

[Bug 47775] Wine `start` doesn't support launching files with a full UNIX path specified

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=47775

Ken Sharp  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #7 from Ken Sharp  ---
Closing bugs marked as invalid.