Gcenx / macOS_Wine_builds

Official Winehq macOS Packages
501 stars 23 forks source link

Any idea how to debug 'Application could not be started, or no application associated with the specified file."? #25

Closed brandonros closed 3 years ago

brandonros commented 3 years ago

I know this is a wine bug and not the purpose of your package, just thought I'd check with you in case you knew.

 ./Contents/Resources/wine/bin/wine64 /Users/brandonros/Desktop/WinOLS.exe 
0040:err:rpc:rpcrt4_ncacn_np_handoff Failed to retrieve the computer name, error 2
0040:err:rpc:rpcrt4_ncacn_np_handoff Failed to retrieve the computer name, error 2
0040:err:rpc:rpcrt4_ncacn_np_handoff Failed to retrieve the computer name, error 2
0040:err:rpc:rpcrt4_ncacn_np_handoff Failed to retrieve the computer name, error 2
Application could not be started, or no application associated with the specified file.
ShellExecuteEx failed: Internal error.

Brandons-MacBook-Air:Wine Devel.app brandonros 2021-08-26 14:49:27 $ 0040:err:rpc:rpcrt4_ncacn_np_handoff Failed to retrieve the computer name, error 2
00cc:fixme:rpc:handle_bind_error unexpected status value 1765
0040:err:rpc:rpcrt4_ncacn_np_handoff Failed to retrieve the computer name, error 2
0058:err:rpc:RpcAssoc_BindConnection rejected bind for reason 0
00d0:fixme:rpc:handle_bind_error unexpected status value 1765
0094:err:rpc:RpcAssoc_BindConnection rejected bind for reason 0
0040:err:rpc:rpcrt4_ncacn_np_handoff Failed to retrieve the computer name, error 2
00d4:fixme:rpc:handle_bind_error unexpected status value 1765
006c:err:rpc:RpcAssoc_BindConnection rejected bind for reason 0
Gcenx commented 3 years ago

Yeah I’m aware of Bug 51632 this was resolved with two upstream patches, it was going to be one but I’d recommended splitting the build directory workaround into a separate patch.

This will be resolved within wine-6.16.

Gcenx commented 3 years ago

The linked bug resolves

0040:err:rpc:rpcrt4_ncacn_np_handoff Failed to retrieve the computer name, error 2

The other problem might be related to that or something else entirely, was this application 64Bit?

brandonros commented 3 years ago

lol... the installer was 32-bit but the application was 64-bit... thanks.

Gcenx commented 3 years ago

lol... the installer was 32-bit but the application was 64-bit... thanks.

Sadly that still externally common for 64Bit Windows software to be packaged within a 32Bit installer.