Closed jrgiacone closed 1 year ago
I'm not a maintainer.
I'm not a maintainer.
I apologize, I saw you on the contributors section for the default.nix
Unfortunately I don't know how can this be fixed on a packaging level. Have you checked if there are issues related on the Heroic repo? This might help in understanding what to fix, specially because I don't have on hand my gaming rig anymore.
Another question that comes to mind that might be helpful to troubleshoot this (to see if this issue is from Legendary or the Heroic package): The legendary binary being used on your case is from the AppImage. Can you try running the same command but with the legendary-gl
package on Nixpkgs? You can just copy the command on the first line and replace the legendary
path.
I tried with rare and legendary-gl, it also does not launch with proton
Then this might be something to consider with legendary developers, or at least there isn't much we can do at packaging level (unless someone can provide a clue of what is missing).
Then this might be something to consider with legendary developers, or at least there isn't much we can do at packaging level (unless someone can provide a clue of what is missing).
Yea I am not sure, it works great on fedora and arch in my testing with no issues, I tried on their discord and their github and they just closed it saying ask for help on discord, which no one was able to
FYI, today I will throw an updated version on NUR, but using the .deb instead of the AppImage so I can customize the internals. The idea is using legendary
and gogdl
from nixpkgs and my NUR repo respectively and patching some of the code from the app.asar
. Can you please try from it and see how it goes @jrgiacone?
FYI, today I will throw an updated version on NUR, but using the .deb instead of the AppImage so I can customize the internals. The idea is using
legendary
andgogdl
from nixpkgs and my NUR repo respectively and patching some of the code from theapp.asar
. Can you please try from it and see how it goes @jrgiacone?
Hi I tried, but no matter what im getting a different error now with it stating FileNotFoundError: [Errno 2] No such file or directory: '/home/jrgiacone/.config/heroic/tools/proton/Proton-GE-Proton7-18/files/bin/wine64'
however the file is most definitely there, same with any version of proton @WolfangAukang
[cli] INFO: Logging in...
[Core] INFO: Trying to re-use existing login session...
[cli] INFO: Checking for updates...
[Core] INFO: Getting authentication token...
[cli] INFO: Launching 4f272a49a39742b795d63e1f483a7c7d...
Proton: Upgrading prefix from 7.0-100 to GE-Proton7-18 (/home/jrgiacone/Games/Heroic/Prefixes/whileTrueLearn/)
Proton: Prefix has an invalid version?! You may want to back up user files and delete this prefix.
Traceback (most recent call last):
File "/home/jrgiacone/.config/heroic/tools/proton/Proton-GE-Proton7-18/proton", line 1597, in <module>
rc = g_session.run()
File "/home/jrgiacone/.config/heroic/tools/proton/Proton-GE-Proton7-18/proton", line 1555, in run
rc = self.run_proc([g_proton.wine64_bin, "c:\\windows\\system32\\steam.exe"] + sys.argv[2:] + self.cmdlineappend)
File "/home/jrgiacone/.config/heroic/tools/proton/Proton-GE-Proton7-18/proton", line 1533, in run_proc
return subprocess.call(args, env=local_env, stderr=self.log_file, stdout=self.log_file)
File "/nix/store/1zby0qylgvhdsxca67baccfrygbsi27n-python3-3.8.13/lib/python3.8/subprocess.py", line 340, in call
with Popen(*popenargs, **kwargs) as p:
File "/nix/store/1zby0qylgvhdsxca67baccfrygbsi27n-python3-3.8.13/lib/python3.8/subprocess.py", line 858, in __init__
self._execute_child(args, executable, preexec_fn, close_fds,
File "/nix/store/1zby0qylgvhdsxca67baccfrygbsi27n-python3-3.8.13/lib/python3.8/subprocess.py", line 1704, in _execute_child
raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: '/home/jrgiacone/.config/heroic/tools/proton/Proton-GE-Proton7-18/files/bin/wine64'
FYI, I haven't tried this one yet, I might be able to check it this week.
FYI, I haven't tried this one yet, I might be able to check it this week.
did you have any luck getting a version of proton to work?
Unfortunately I haven't been able to test that one yet, haven't gotten the time.
Unfortunately I haven't been able to test that one yet, haven't gotten the time.
No worries, jon recommended this on reddit, but I have yet to get it properly working/packageable :
stating file does not exist. It is most definitely in the folder though.
file does not exist. is common when an executable tries to load an ELF binary which doesn't have a corrected ELF interpreter, and the RPATH patched to find any other libraries.
Try doing steam-run with the launcher.
The expression https://github.com/nix-community/nur-combined/blob/1e909717432c64091cc6b690bb41d77c006ad877/repos/wolfangaukang/pkgs/heroic/default.nix#L15 should probably be using buildFHSUserEnvBubbleWrap if it's going to be launching other executables which are packaged outside of nixpkgs.
That would make sense. I think that when you package AppImages, it wraps the application in a FHS environment, so now that I have set that up with the .deb (on the NUR case), it is not wrapped anymore. I can try to rewrite the current setup and post it here, and if you want to test it, that would be great.
I can totally test it out!
FYI @jrgiacone I have contacted you through email
I have a branch with a FHS user-env wrapper for the heroic launcher currently on master
, but tar crashes when run by the DXVKInstaller.
(17:11:52) ERROR: [DXVKInstaller]: Extraction of vkd3d failed with: Error: Command failed: tar -I zstd -xvf /home/aidan/.config/heroic/tools/vkd3d/vkd3d-proton-2.6.tar.zst -C /home/aidan/.config/heroic/tools/vkd3d
*** stack smashing detected ***: terminated
tar: Child died with signal 6
tar: Error is not recoverable: exiting now
~I'm wondering if switching from the AppImage to the tarball release would make any difference.~
EDIT: Never mind, that error happens even when run outside the FHS env.
@aidalgol Based on your branch, I created #187631, that modifies the name of the current heroic
package as unwrapped and it is now using the tarball.
Describe the bug
The heroic launcher cannot access installed versions of proton or use proton
Steps To Reproduce
Steps to reproduce the behavior:
Expected behavior
should launch as tested on archlinux install
Log File from error
Additional context
Add any other context about the problem here.
Notify maintainers
@WolfangAukang @siddhantk232 @dotlambda
Metadata