qupzilla icon indicating copy to clipboard operation
qupzilla copied to clipboard

AppImage for 2.2.4 not loading

Open slicer69 opened this issue 7 years ago • 4 comments

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?

slicer69 avatar Jan 28 '18 01:01 slicer69

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!

ghost avatar Jan 28 '18 06:01 ghost

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"

slicer69 avatar Jan 28 '18 14:01 slicer69

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?

ghost avatar Jan 28 '18 15:01 ghost

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

slicer69 avatar Jan 28 '18 18:01 slicer69