Raezroth / Linux-ARM-Gaming-Chroot

Guide to setup a MultiArch Chroot container to run Steam and Wine.
GNU General Public License v3.0
75 stars 8 forks source link

Manjaro Plasma Pinephone Pro (incompatibile/ not working.) (closed due to lack of fix/other.) #8

Closed MadameMalady closed 1 year ago

Raezroth commented 1 year ago

Was the path you entered an absolute path?

Also, the installer script should create a Steam shortcut to launch from phosh & plasma mobile's app drawer.

Raezroth commented 1 year ago

That locale error is expected and can be ignored. We end up manual setting LC_ALL and LC_LANGUAGE in /root/.bashrc

There will be few things that will show errors due running in chroot but can be ignored. The setup process can also have wait time. Freezing can occur depending on host distro from what i found, but it is best to be patient.

CalcProgrammer1 commented 1 year ago

I had a similar experience installing it in Danctnix Arch. I ran the script, targeted /chroot/gaming as the chroot path. It created the chroot just fine, but it did not install the gaming_chroot_terminal command or create a desktop file or anything. When I manually chroot in, su user doesn't work, nor does su user1 even though /home/user1 exists.

Raezroth commented 1 year ago

I have done a few commits to try to fix the user creation bug and the shortcut creation bug. If you can try creating the chroot again with the new edits and let me know. That would be great.

Raezroth commented 1 year ago

remove " /opt/steam " " /bin/gaming_chroot_terminal" "/bin/steam-box" and try running the installer as root?? it should have prompt you to run it with sudo or doas though.

Raezroth commented 1 year ago

also make sure you run the installer from inside the git clone path.

CalcProgrammer1 commented 1 year ago

Just tried again on Arch, same thing. I did a git pull on master to make sure I was up to date, ran the script from

/home/adam/Linux-ARM-Gaming-Chroot/

Set chroot path to

/chroot/gaming

I had the failures writing steam-box and the gaming chroot script and those commands are not available.

Also, why /bin? Why not /usr/local/bin?

Are you supposed to run the script itself as root?

Raezroth commented 1 year ago

The script should automatically ask for sudo or doas password so that wasn't it. I just move the scripts to a bin folder in the user's home directory and added that to path to fix permission issues

Raezroth commented 1 year ago

I also fixed in the script where they get created to and the uninstall option now deletes the shortcuts as well

CalcProgrammer1 commented 1 year ago

I created a scripts folder in the chroot target (/chroot/gaming) and ran the script as root and it worked. If the scripts directory doesn't exist it fails.

Raezroth commented 1 year ago

The latest commit should have a few fixes for that and some other things. even adding user1 to sudo group

Raezroth commented 1 year ago

Try cloning the installer script again. I updated to create a bin directory in the user's home folder and link it in path.

Raezroth commented 1 year ago

I had to clone the repo again to actually get the changes to the script for some reason

Raezroth commented 1 year ago

I have went through and worked out all the bugs I can currently. The variables are there to help the installer and with out them, the installer would break itself.