[Bug 42632] New: attempt to open Doom wine-2.3 staging fails to open

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

            Bug ID: 42632
           Summary: attempt to open Doom wine-2.3 staging fails to open
           Product: Wine-staging
           Version: 2.3
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
          Assignee: wine-bugs(a)winehq.org
          Reporter: winehq(a)fermulator.fastmail.org
                CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
                    sebastian(a)fds-team.de
      Distribution: ---

Created attachment 57571
  --> https://bugs.winehq.org/attachment.cgi?id=57571
wine patches output

Followed
 - https://github.com/wine-compholio/wine-staging/wiki/Installation

Installed Doom (legit version PAID!).

Upon attempt to open, via wine-staging 2.3, nothing really happens but for a
few seemingly irrelevant log messages.

What am I missing?
(is it a bug or user fail?)

{{{
$ /opt/wine-staging/bin/wine64 --version
wine-2.3 (Staging)

$ /opt/wine-staging/bin/wine64 ./DOOMx64.exe 
fixme:winediag:start_process Wine Staging 2.3 is a testing version containing
experimental patches.
fixme:winediag:start_process Please mention your exact version when filing bug
reports on winehq.org.
fixme:heap:RtlSetHeapInformation 0x340000 0 0x33fd20 4 stub
fixme:ver:GetCurrentPackageId (0x32ded0 (nil)): stub
}}}

The patches output is attached, and check-libs:
{{{
$ /opt/wine-staging/bin/wine64 --check-libs
libcairo.so.2: /usr/lib/x86_64-linux-gnu/libcairo.so.2
The futex facility returned an unexpected error code.Aborted
}}}

-- 
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.

[Bug 42632] attempt to open Doom wine-2.3 staging fails to open

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

--- Comment #1 from winehq(a)fermulator.fastmail.org <winehq(a)fermulator.fastmail.org> ---
Forgot to include other output:

{{{
$ /opt/wine-staging/bin/wine64 ./DOOMx64vk.exe 
fixme:heap:RtlSetHeapInformation 0x340000 0 0x33fd20 4 stub
fixme:ver:GetCurrentPackageId (0x32ded0 (nil)): stub

$ /opt/wine-staging/bin/wine ./DOOMx64.exe 
fixme:heap:RtlSetHeapInformation 0x330000 0 0x32fd20 4 stub
fixme:ver:GetCurrentPackageId (0x31ded0 (nil)): stub

$ /opt/wine-staging/bin/wine ./DOOMx64vk.exe 
fixme:heap:RtlSetHeapInformation 0x330000 0 0x32fd20 4 stub
fixme:ver:GetCurrentPackageId (0x31ded0 (nil)): stub
}}}

-- 
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.

[Bug 42632] attempt to open Doom wine-2.3 staging fails to open

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

--- Comment #2 from winehq(a)fermulator.fastmail.org <winehq(a)fermulator.fastmail.org> ---
Created attachment 57572
  --> https://bugs.winehq.org/attachment.cgi?id=57572
old wine 1.6 output for reference (not really relevant)

of course, this is the output of the OLD version of wine (not wine-staging)

not really relevant to this report, but including to show that I am indeed
running wine-staging, as countered by this attachment which is against the
non-staging version

-- 
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.

[Bug 42632] attempt to open Doom wine-2.3 staging fails to open

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

fjfrackiewicz(a)gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |fjfrackiewicz(a)gmail.com

--- Comment #3 from fjfrackiewicz(a)gmail.com ---
(In reply to winehq(a)fermulator.fastmail.org from comment #0)
> $ /opt/wine-staging/bin/wine64 ./DOOMx64.exe

I may be wrong but it looks like you're trying to run the DOOM executable as if
it were a Linux binary or executable shell script with that 

./DOOMx64.exe

You should only need to run 

wine DOOMx64.exe 

or 

wine DOOMx64vk.exe (for the Vulkan version)

Also, do you have the game installed via Steam or what? Because if I am running
the Steam version via the terminal I usually navigate to the following
directory: 

/.wine_doom_2016/drive_c/Program Files (x86)/Steam/steamapps/common/DOOM

So you may need to do something similar to my use case....

-- 
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.

[Bug 42632] attempt to open Doom wine-2.3 staging fails to open

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

--- Comment #4 from winehq(a)fermulator.fastmail.org <winehq(a)fermulator.fastmail.org> ---
(In reply to fjfrackiewicz from comment #3)
> (In reply to winehq(a)fermulator.fastmail.org from comment #0)
> > $ /opt/wine-staging/bin/wine64 ./DOOMx64.exe
>
> I may be wrong but it looks like you're trying to run the DOOM executable as
> if it were a Linux binary or executable shell script with that
>
> ./DOOMx64.exe
>
> You should only need to run
>
> wine DOOMx64.exe
>
> or
>
> wine DOOMx64vk.exe (for the Vulkan version)
>
> Also, do you have the game installed via Steam or what? Because if I am
> running the Steam version via the terminal I usually navigate to the
> following directory:
>
> /.wine_doom_2016/drive_c/Program Files (x86)/Steam/steamapps/common/DOOM
>
> So you may need to do something similar to my use case....

No. The "./" is simply a relative path. Note that my examples are prefixed with
some "wine" path.

-- 
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.

[Bug 42632] attempt to open Doom wine-2.3 staging fails to open

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

winetest(a)luukku.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |winetest(a)luukku.com

--- Comment #5 from winetest(a)luukku.com ---
You need to cd into the exe directory and start the exe wine doom.exe or
something similar. There will be no ./ in front of doom game excutable even
your directories would have.

I just tested wine ./exe name and it seems to work, but it's not the way it was
intended.

-- 
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.

[Bug 42632] attempt to open Doom wine-2.3 staging fails to open

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

--- Comment #6 from winetest(a)luukku.com ---
(In reply to winehq(a)fermulator.fastmail.org from comment #4)
> (In reply to fjfrackiewicz from comment #3)
> > (In reply to winehq(a)fermulator.fastmail.org from comment #0)
>
> No. The "./" is simply a relative path. Note that my examples are prefixed
> with some "wine" path.

You need to start the exes from the directory without any ./ 

This bug sounds so invalid since none else is complaining about this.

-- 
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.

[Bug 42632] attempt to open Doom wine-2.3 staging fails to open

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

--- Comment #7 from Austin English <austinenglish(a)gmail.com> ---
(In reply to winetest from comment #6)
> (In reply to winehq(a)fermulator.fastmail.org from comment #4)
> > (In reply to fjfrackiewicz from comment #3)
> > > (In reply to winehq(a)fermulator.fastmail.org from comment #0)
> >
> > No. The "./" is simply a relative path. Note that my examples are prefixed
> > with some "wine" path.
>
> You need to start the exes from the directory without any ./

Prepending ./ won't matter, please stop spreading misinformation and you've
been told before. This is my last warning.

-- 
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.

[Bug 42632] attempt to open Doom wine-2.3 staging fails to open

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

winehq(a)fermulator.fastmail.org <winehq(a)fermulator.fastmail.org> changed:

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

--- Comment #8 from winehq(a)fermulator.fastmail.org <winehq(a)fermulator.fastmail.org> ---
indeed, attempting to execute without "./" goes beyond

-- 
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.

[Bug 42632] attempt to open Doom wine-2.3 staging fails to open

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

Austin English <austinenglish(a)gmail.com> changed:

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

--- Comment #9 from Austin English <austinenglish(a)gmail.com> ---
Closing.

-- 
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.