-
-
Notifications
You must be signed in to change notification settings - Fork 559
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
AppImageAssistant 0.9.2 stopped working on ArchLinux #6
Comments
Maybe an archlinux problem? https://bugs.archlinux.org/task/21459 |
On my system, /usr/bin/python is a link to /usr/bin/python2 to avoid that bug, so I don't think it's related Besides, the whole point of AppImages is that they should work regardless of the distro! I guess AppImgeAssistant should include the python interpreter, i.e. with virtualenv |
Note to self: Investigate Arch Linux Live ISO booting https://wiki.archlinux.org/index.php/GRUB#Booting_ISO9660_image_file_directly_via_GRUB |
This might be the root cause: [antergos@Antergos-ISO ~]$ python --version Unlike other distributions, Arch Linux appears to set Python 3 as the default. This should be a partial workaround on Arch-based systems: However, I still get: |
Affects also OpenSUSE 13.1 (64bit) and this distro uses python2 when called as 'python': (the same happens with AppDirAssistant 0.3.3) note: my system was missing python-vte, installing that enabled me to run the AppDirAssistant after uncompressing (though that didn't work out later during the strace step), but the downloaded image still doesn't work note: running uncompressed AppRun throws a segfault |
Since a748c0f it should theoretically be python3 compatible, although I have not tried. As for the segfault, that is really strange. Where did you get your binary from? Try using the ones from https://github.com/probonopd/AppImageKit/releases/ - do they work better? |
I got them from portablelinuxapps.org so I guess they're official. AppImageAssistant from the releases throws the same error, both packaged and extracted. (I gave both python-gtk and python-vte installed) AppRun from releases throws a segfault also, here's the output of strace: http://paste.opensuse.org/79595974 (the last line means "Segmentation Fault") (interesting - in AppDirAssistant, after uncompressing, AppRun was a binary, and here it's a script) |
Please check if 635c270 solves this, since now python2 is used explicitly rather than python. |
Still cannot run.
|
Even building with the build.sh script and from git I'm getting this failure |
@ShadowCreator are you referring to a general error with AppImages or to a runtime error when trying to run AppImageAssistant? |
Sorry I wasn't more specific, AppImageAssistant isn't working. AppImages On Sun, Jan 31, 2016 at 8:42 PM, probonopd notifications@github.com wrote:
|
Thanks ShadowCreator. I will not invest time into making AppImageAssistant work on Arch because I am not an Arch user but would welcome pull requests. |
That's all right, I've been having a look myself. For some reason it runs from the AppImageAssistant.AppDir folder but not On Sat, Feb 6, 2016 at 5:08 AM, probonopd notifications@github.com wrote:
|
for anyone having this error on arch the reason is the bundled vte.so in the AppImageAssistant simply deleting /AppImageAssistant.AppDir/usr/share/pyshared/vte.so allows the AppImageAssistant to run on Arch |
AppImageAssistant hast been replaced by |
AppImageAssistant 0.9 runs perfectly fine, but AppImageAssistant 0.9.2 and 0.9.3 don't.
I receive this error in both:
If I unpack the AppImage and run the AppRun, I get the same error, but if I run the AppImageAssistant instead, it works correctly.
If I place the AppRun from 0.9 into 0.9.3, it works, but as soon as I add this, it fails:
The text was updated successfully, but these errors were encountered: