-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't install on Manjaro Linux - No such file or directory #1
Comments
Hrm looks like the AppImage failed to build for some reason prior to step 15. I'll do a build and see if I can replicate it. |
So it looks like this may be an issue with fuse, which is required by pkg2appimage. I can replicate the issue, trying to find a fix for it. |
Ok, I think I've resolve this. You'll need to make sure you have fuse v2 installed on the host system in addition to docker. Fuse is required under-the-hood by pkg2appimage, but we didn't explicitly check for that before. It looks like docker/apparmor became more strict on newer distros, which prevented pkg2appimage from being able to use fuse inside the docker container. I've updated the readme file and also added some code-checks to check for docker and fuse. Also, I made the script more strict, and it should now fail properly if a command it calls fails. Try out the bugfix-01 branch and see if that works for you. LMK if you bump into other issues with that patch. I tested this on Ubuntu 22.04, but I can install Manjaro in a VM to troubleshoot additional distro-specific issues if necessary. |
With fuse v2 installed I was able to go past all 20 steps in installation, but no files were generated to /out, and no log file is present in directory |
Ok. Thanks for the update. If you have a chance to post what's written to stdout, I'd appreciate it. What version of Manjaro are you on? I'll do a clean install in a VM tonight and see how far I get. |
Here is full stdout - log.txt |
Ok. Status update. I got Manjaro KDE edition installed in a VM, and fixed the issues that prevented installation. It looks like the PlasticSCM guys renamed some files which broke some of the commands used to build the AppImage. So that part works now. However, when I run it, I'm getting an error about "failed to initialize GTK" on Manjaro. So I'm looking into that next. |
So I pushed some more commits to that bugfix-01 branch. The script now clearly reports success or failure status. I also added some scripts for analyzing the resulting AppImage. The AppImage should build correctly now on Manjaro. The GUI boots up, and I can log in, but then the app reports that GTK error. I tested this on Ubuntu 22.04 also, and I'm seeing the same GTK issue there. So tomorrow I'll go back and test on 20.04 and 18.04 and see if it still occurs there. It used to work on those platforms, anyways. The log files under |
Ok. Getting closer. Turns out the PlasticSCM folks have done a pretty major overhaul. They renamed some packages, removed some commands, and removed their mono and gtk dependencies. This script should now be more robust to such changes. It appears to work now for me on Ubuntu 22.04 and Manjaro. |
Pushed up all the changes I have to the bugfix-01 branch. LMK if you still have issues with it. |
I tried this on Arch. I think it builds fine, but it had trouble linking the files. I ran it again with Running with |
Installation script is getting error at step 15
The text was updated successfully, but these errors were encountered: