proton-caller icon indicating copy to clipboard operation
proton-caller copied to clipboard

flummoxed about error codes 53 and 1.

Open Hebgbs opened this issue 2 years ago • 4 comments

Right, I have a recently-installed copy of EndeavourOS, which I chose to use over my copy of Manjaro MATE which had worked before. I also tried with a copy of Manjaro KDE, where I still encounter the same errors. So walk me through what I am missing here;

I run an executable I know had worked in the past, since it's an installer for a game I was playing before I elected to distro-hop. I request for proton-call to run the application without defining the Proton version to use since I have 7.0 installed. I get this:

wine: failed to open [redacted]: c0000135
proton-call: proton exited with: code: 53

I define to use Proton Experimental because that's what had worked before. This is what I get:

Traceback (most recent call last):
  File "/mnt/Windows/Program Files (x86)/Steam/steamapps/common/Proton - Experimental/proton", line 28, in <module>
    from filelock import FileLock
ModuleNotFoundError: No module named 'filelock'
proton-call: proton exited with: code: 1

What?! That's got to be a Python thing right? I don't even know how to adequately describe this issue. But I feel like I am missing something. Though, I somehow resolved the missing Soldier issue I was having before… I think? If I get that again after following some kind suggestions from this thread, I'll ask about that. But so far this software isn't working in spite of my best efforts on a relatively-fresh Arch-based system instance.

Hebgbs avatar Apr 27 '22 23:04 Hebgbs

I want to update expressing that Proton via Steam works but this doesn't. I do nto understand what i am doing wrong when I had tried both using the local Steam directory in my home and remote Steam directory in the NTFS paartition Windows runs from, since I dual-boot and that option — using Proton from NTFS — had worked before.

I have no idea what is wrong, aside from maybe I am being retarded.

Hebgbs avatar May 02 '22 00:05 Hebgbs

It is most likely a bug in proton collar. I have not had the chance to look over it yet.

caverym avatar May 02 '22 03:05 caverym

wine: RLIMIT_NICE is <= 20, unable to use setpriority safely
wine: failed to open "/Media/Games/Lineage_2/GW/system/l2.exe": c0000135
proton-call: proton exited with: code: 53

I have a similar error. P.S. distr Arch

guglovich avatar Jun 05 '22 13:06 guglovich

Same here:

proton-call -r '/media/artik/Twelve Minutes/setup.exe' 
warning: using default common
esync: up and running.
wine: RLIMIT_NICE is <= 20, unable to use setpriority safely
wine: failed to open "/media/artik/Twelve Minutes/setup.exe": c0000135
proton-call: proton exited with: code: 53

What worked for me, was to place the installer in the drive_c of my wine folder to make it work:

proton-call -r '/home/artik/.wine/drive_c/12m/setup.exe' or proton-call -r '/home/artik/.proton-caller/Proton Custom/pfx/drive_c/12m/setup.exe'

Now it works. Seems to be a path issue

artik avatar Jun 09 '22 15:06 artik