Skip to content
This repository has been archived by the owner on May 10, 2018. It is now read-only.

AppImage for 2.2.4 not loading #2574

Open
slicer69 opened this issue Jan 28, 2018 · 4 comments
Open

AppImage for 2.2.4 not loading #2574

slicer69 opened this issue Jan 28, 2018 · 4 comments
Labels

Comments

@slicer69
Copy link

I'm testing out the 2.2.4 release of QupZilla via the AppImage package. I found at first QupZilla would fail to load. Running from a terminal showed that the library libQupZilla.so.2 was missing. I unpacked the AppImage and found if I changed the name of the file "lib/QupZilla.so.2.2.4" to "lib/QupZilla.so.2" then the browser launches without error.

I've run the AppImage on two machines and only one encountered the library name error, the other is working fine. I've confirmed the SHA256 checksum of my download is okay, so I'm not sure what would cause one to work and the other not.

Perhaps in the next version of the AppImage there could be a symlink added so that QupZilla.so.2 points to QupZilla.so.2.2.4 to avoid the system not finding the correct library?

@ghost
Copy link

ghost commented Jan 28, 2018

Perhaps in the next version of the AppImage there could be a symlink added so that QupZilla.so.2 points to QupZilla.so.2.2.4 to avoid the system not finding the correct library?

That's already done in any AppImage version!

@slicer69
Copy link
Author

It's not done in version 2.2.4. I just unpacked the AppImage and confirmed there is no file or link in the archive called libQupZilla.so.2. And if I run "ldd" on the QupZilla executable I get the error message: "libQupZilla.so.2 => not found"

@ghost
Copy link

ghost commented Jan 28, 2018

When unpacking Appimage, it does not extract the SYMLINKS (i don't know whether that's a bug or intended). If you mount it, you will see that the files are there (they are created in compilation process, but not when the Appimage was packaged).
You have something on this system that prevents the execution from /tmp/* directory. Do you have active Selinux on it?

@slicer69
Copy link
Author

SELinux may be the culprit. I'll see if I can work around that.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants