Package Details: creality-print-appimage 6.3.0.3420-1

Git Clone URL: https://aur.archlinux.org/creality-print-appimage.git (read-only, click to copy)
Package Base: creality-print-appimage
Description: Creality Print is a slicer dedicated to FDM printers.
Upstream URL: https://github.com/CrealityOfficial/CrealityPrint
Keywords: creality
Licenses: AGPL-3.0-only
Conflicts: creality-print
Provides: creality-print
Submitter: maximdeclercq
Maintainer: chadsr
Last Packager: chadsr
Votes: 4
Popularity: 0.002558
First Submitted: 2023-01-16 15:47 (UTC)
Last Updated: 2025-09-30 09:20 (UTC)

Latest Comments

1 2 Next › Last »

chadsr commented on 2025-09-30 09:40 (UTC)

@vitaliikuzhdin I think it makes sense to keep it available, in case of some upstream bundling changes that do end up causing issues.

Indeed, if https://aur.archlinux.org/packages/creality-print-bin is working as expected, then many users may prefer that route.

vitaliikuzhdin commented on 2025-09-28 13:07 (UTC)

I wonder if there is a need to keep the AppImage version. Normally, it is useful since AppImage bundles all the dependencies needed to run the application, but for some reason, Creality doesn't do this. IMO, it's better to just unpack it as a standard binary, which also properly declares its dependencies. What do you think?

vitaliikuzhdin commented on 2025-08-14 08:03 (UTC)

Please update to 6.2.1.3044, it no longer has the issue with libOSMesa.so.

vitaliikuzhdin commented on 2025-07-12 17:48 (UTC)

@chadsr, libOSMesa is provided by mesa-amber, but it's just an outdated branch of mesa for legacy applications. I've pushed the update to creality-print-bin, but it seems like I should revert the change. mesa-amber conflicts with mesa and even provides an old version of it, which results in a broken GUI session for me.

chadsr commented on 2025-07-12 15:40 (UTC)

Unfortunately, the v6.2.0 appimage build is missing libOSMesa.so: https://github.com/CrealityOfficial/CrealityPrint/issues/393

I will refrain from updating until they (hopefully) release an appimage with working dependencies.

vitaliikuzhdin commented on 2025-05-28 13:18 (UTC) (edited on 2025-05-28 15:09 (UTC) by vitaliikuzhdin)

The second v6 Linux build was published today, and it seems to run fine for me on Wayland, both in AppImage mode (creality-print-appimage) and as an extracted binary (creality-print-bin). It still uses X11, though.

RainOrigami commented on 2025-05-05 16:32 (UTC)

@chadsr unfortunately the same error still shows up but now it freezes at the splash screen instead of crashing. I think I'll stick to v6 in a Windows VM for now.

chadsr commented on 2025-05-05 16:00 (UTC)

@RainOrigami Running with the xcb plugin should work:

env QT_QPA_PLATFORM=xcb creality-print

RainOrigami commented on 2025-05-05 15:43 (UTC)

This (5.1.7.10514-1) does not seem to work under wayland even with the workaround from @feiticeir0

It crashes with:

IO:  fatal IO error 2 (No such file or directory) on X server ":0"
      after 894 requests (894 known processed) with 0 events remaining.

0x8081 commented on 2024-11-23 22:40 (UTC)

Patch to update to v5.1.6.10470:

--- a/PKGBUILD
+++ b/../PKGBUILD
@@ -1,5 +1,5 @@
 pkgname=creality-print-appimage
-pkgver=4.3.8.6991
+pkgver=5.1.6.10470
 pkgrel=1
 pkgdesc="Creality Print is a slicer dedicated to FDM printers."
 arch=('x86_64')
@@ -17,7 +17,7 @@ _install_path="/opt/appimages/${_appimage_name}"

 noextract=("${_filename}")
 sha512sums_x86_64=(
-  '600f86b5a1f635b6ffecc2f64c79044e03290edc1ccc2b2b86f103b9294bb9025d90c707317fd01f204301ad7b5c984bc135ba29e7ae2e74f0be6b424c7e605e'
+  '659ef0f441b4991b8d965e971c92c31a3345b1ee0fce0eb36087fa836f1755d17aaaa308473637ed4481a203cb0cc529c2ddc348ce06ca20554a4c68d957e067'
   '5c0982b7475dae73cbc0ce5b96771b969ff7779daae452cf2e0d5d26fb43981c3e614485593f5306dfda9b3d3a6a2a8f319ef62b07d668479c60d82c8c1631b0'
 )
 source_x86_64=(

1 2 Next › Last »