QIDITECH / QIDISlicer

QIDISlicer gets your 3D printing easier and faster.
https://qidi3d.com/
GNU Affero General Public License v3.0
40 stars 10 forks source link

Download error on Slicer 1.1.1 and Appimage v1.1.2 impossible to launch on Linux Distribution #55

Open denisbkm opened 3 months ago

denisbkm commented 3 months ago

Hello all Dev Qidi, I think I'm not the only one having this problem because after testing on different Linux virtual machines (PopOS, Fedora, Debian, Ubuntu...) here is what I get as an error when I download the update from Qidi Slicer 1.1.1 :

Downloading the new QIDISlicer failed: Error getting: https://github.com/QIDITECH/QIDISlicer/releases/download/V1.1.2/QIDISlicer_1.1.2_Linux.AppImage: HTTP 0, HTTP body data size exceeded limit (136314880 bytes)

Another problem: if you download the Appimage from Github, then when you launch the application in a terminal, I always get this error on all Linux distributions: §./QIDISlicer_1.1.2_Linux.AppImage §/tmp/.mount_QIDISly7eTUk/usr/bin/bin/qidi-slicer: error while loading shared libraries: libicuuc.so.66: cannot open shared object file: No such file or directory

I've tried adding the library, but it doesn't work - there must be a build problem in the Appimage :o/

Maybe you should try building in Flatpack like PrusaSlicer does for Linux distributions, and it's also less complicated for the end user when updating.

Hopefully my comment will help you debug v1.1.2 : o)

QIDITECH commented 3 months ago

We tried to add libwebkit2gtk-4.0 to the installation package, but this seemed to cause a bigger problem. We have re-uploaded the installation package, please re-download and run the software.

denisbkm commented 3 months ago

Hello, Following your comment : 1) Update since the software works and there is no more problem "...HTTP 0, HTTP body data size exceeded limit..." 2) New installation 1.1.2 works on Debian Distribution base :o)

=> Bug New installation 1.1.2 which does not work on Fedora/RedHat based Distribution :o/ §/tmp/.mount_QIDISlSLhmDZ/AppRun: ligne 10 : [: /home/.../Documents/QIdi : opérateur binaire attendu §/tmp/.mount_QIDISlSLhmDZ/usr/bin/bin/qidi-slicer: error while loading shared libraries: libwebkit2gtk-4.0.so.37: cannot open shared object file: No such file or directory

There is a possibility that this library is too old and is no longer used with Wayland 🥴️ Hopefully this will help you with your debugging :o)

QIDITECH commented 3 months ago

Thank you for your testing and we will continue to find ways to improve the dependencies. libwebkit2gtk-4.0 can only be manually installed by the customer

denisbkm commented 3 months ago

For Fedora 39 users here is some information : normally Fedora "webkitgtk" packages are superior with the latest update: -> webkit2gtk4.1 -> webkitgtk6.0

Capture d’écran du 2024-03-25 15-07-57

-> see the page https://packages.fedoraproject.org/pkgs/webkitgtk/webkit2gtk4.0/

1) copy the name of the packet and do in a terminal:

sudo dnf install webkit2gtk4.0-2.44.0-2.fc39

then this will put the dependencies : Last metadata expiration check done 00:01:29 ago Mon Mar 25 2024 2:06:51 PM. Dependencies resolved. ==================================================== ============================= Architecture Package Version Deposit Size ==================================================== ============================= Facility: webkit2gtk4.0 x86_64 2.44.0-2.fc39 updates 25 M Installing dependencies: javascriptcoregtk4.0 x86_64 2.44.0-2.fc39 updates 8.4 M

Summary of the transaction ==================================================== ============================= Install 2 Packages

Total download size: 33M Size of installed packages: 107M Do you want to continue ? [y/N]: y Download packages: (1/2): javascriptcoregtk4.0-2.44.0-2.fc39.x86_6 11 MB/s 8.4 MB 00:00 (2/2): webkit2gtk4.0-2.44.0-2.fc39.x86_64.rpm 20 MB/s 25 MB 00:01
Total 20 MB/s 33 MB 00:01
Fedora 39 - x86_64 - Updates 1.6 MB/s 1.6 kB 00:00

Importing the GPG key 0x18B8E74C: User: “Fedora (39) fedora-39-primary@fedoraproject.org” Footprint: E8F2 3996 F232 1864 0CB4 4CBE 75CF 5AC4 18B8 E74C Source: /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-39-x86_64 Do you want to continue ? [y/N]: y The key has been imported successfully Testing the transaction Transaction verification was successful. Launching the test transaction Test transaction successful. Execution of the transaction Preparation: 1/1 Installation: javascriptcoregtk4.0-2.44.0-2.fc39.x86_64 1/2 Installation: webkit2gtk4.0-2.44.0-2.fc39.x86_64 2/2 Running the scriptlet: webkit2gtk4.0-2.44.0-2.fc39.x86_64 2/2 Checking: javascriptcoregtk4.0-2.44.0-2.fc39.x86_64 1/2 Checking: webkit2gtk4.0-2.44.0-2.fc39.x86_64 2/2

Installed: javascriptcoregtk4.0-2.44.0-2.fc39.x86_64 webkit2gtk4.0-2.44.0-2.fc39.x86_64

Finished !

2) Then set the permission to execute the Appimage 3) Launch QIdiSlicer 1.1.2 which will work correctly (X11 or Wayland) 👍️

As it is not a Flatpack, I advise you not to integrate QidiSlicer with the Desktop to have the launch icons, as there will be no automatic replacement in a future update. For example, I installed version 1.1.1 with integration, then did a 1.1.2 installation with integration, but it is version 1.1.1 that is launched if you click on the QidiSlicer icon on your desktop. => Instead, launch directly from the Appimage.

Hope this helps everyone 😇️

johnsonm commented 2 months ago

You don't really need to install the exact version with dnf.

Just dnf install webkit2gtk4.0 (or, for atomic desktops, rpm-ostree install webkit2gtk4.0) works fine.

@QIDITECH I would have expected it and its dependencies to be in the appimage — I think when you included it literally you didn't include the specific packages it depended on and that was the problem I am guessing you are alluding to.