Package Details: creality-print-bin 1:7.0.0.4127-2

Git Clone URL: https://aur.archlinux.org/creality-print-bin.git (read-only, click to copy)
Package Base: creality-print-bin
Description: 3D slicer for Creality printers
Upstream URL: https://www.creality.com
Licenses: AGPL-3.0-only
Conflicts: creality-print
Provides: creality-print
Submitter: vitaliikuzhdin
Maintainer: vitaliikuzhdin
Last Packager: vitaliikuzhdin
Votes: 1
Popularity: 0.007787
First Submitted: 2025-05-28 13:02 (UTC)
Last Updated: 2026-01-18 12:32 (UTC)

Pinned Comments

Latest Comments

1 2 Next › Last »

vitaliikuzhdin commented on 2026-01-12 12:02 (UTC) (edited on 2026-01-12 13:29 (UTC) by vitaliikuzhdin)

Sorry about the delay with the update. You'll have to wait for a while unless someone wants to become a co-maintainer and bump the pkgver for me. In the meantime, could those experiencing startup crashes please try this: https://forum.mxlinux.org/viewtopic.php?p=842932#p842932

vitaliikuzhdin commented on 2026-01-04 14:20 (UTC)

@caturix, it seems like the easiest solution is to use creality-print-appimage or the FlatPak. This might explain the cause: https://gitlab.archlinux.org/archlinux/packaging/packages/prusa-slicer/-/commit/ee55e54248b684436c414df62df09346f5b43f25

caturix commented on 2025-12-30 13:04 (UTC) (edited on 2025-12-30 14:03 (UTC) by caturix)

Hey, I just installed it and tried installing the before mentioned dependencies but is still get this then trying to launch:

[2025-12-30 13:56:38.597623] [0x00007f4813a5dfc0] [trace] Initializing StaticPrintConfigs

[2025-12-30 13:56:38.601761] [0x00007f4813a5dfc0] [error] main start

[2025-12-30 13:56:38.601766] [0x00007f4813a5dfc0] [error] main linux

[2025-12-30 13:56:38.601778] [0x00007f4813a5dfc0] [error] main check linux

[2025-12-30 13:56:38.601780] [0x00007f4813a5dfc0] [error] main google_breakpad init

[2025-12-30 13:56:38.601809] [0x00007f4813a5dfc0] [error] main google_breakpad init finished

add font of HarmonyOS_Sans_SC_Bold returns 1 add font of HarmonyOS_Sans_SC_Regular returns 1 add font of NanumGothic-Regular returns 1 add font of NanumGothic-Bold returns 1

(CrealityPrint:131816): Gtk-CRITICAL **: 13:56:40.629: gtk_cell_layout_get_cells: assertion 'GTK_IS_CELL_LAYOUT (cell_layout)' failed

(CrealityPrint:131816): Gtk-CRITICAL **: 13:56:40.629: gtk_cell_layout_get_cells: assertion 'GTK_IS_CELL_LAYOUT (cell_layout)' failed

(CrealityPrint:131816): Gtk-CRITICAL **: 13:56:40.630: gtk_cell_layout_get_cells: assertion 'GTK_IS_CELL_LAYOUT (cell_layout)' failed

(CrealityPrint:131816): Gtk-CRITICAL **: 13:56:40.630: gtk_cell_layout_get_cells: assertion 'GTK_IS_CELL_LAYOUT (cell_layout)' failed

(CrealityPrint:131816): Gtk-CRITICAL **: 13:56:40.631: gtk_cell_layout_get_cells: assertion 'GTK_IS_CELL_LAYOUT (cell_layout)' failed

(CrealityPrint:131816): Gtk-CRITICAL **: 13:56:40.631: gtk_cell_layout_get_cells: assertion 'GTK_IS_CELL_LAYOUT (cell_layout)' failed

(CrealityPrint:131816): Gtk-CRITICAL **: 13:56:40.632: gtk_cell_layout_get_cells: assertion 'GTK_IS_CELL_LAYOUT (cell_layout)' failed

(CrealityPrint:131816): Gtk-CRITICAL **: 13:56:40.632: gtk_cell_layout_get_cells: assertion 'GTK_IS_CELL_LAYOUT (cell_layout)' failed

(CrealityPrint:131816): Gtk-CRITICAL **: 13:56:40.633: gtk_cell_layout_get_cells: assertion 'GTK_IS_CELL_LAYOUT (cell_layout)' failed

(CrealityPrint:131816): Gtk-CRITICAL **: 13:56:40.633: gtk_cell_layout_get_cells: assertion 'GTK_IS_CELL_LAYOUT (cell_layout)' failed

Dump path: /tmp/fc4f0672-8587-4b5c-274b30af-ec3f9bc4.dmp

Unhandled unknown exception; terminating the application.

Meriemi commented on 2025-12-15 08:27 (UTC) (edited on 2025-12-15 08:27 (UTC) by Meriemi)

I had the same problem on kde wayland as @TheOtherOne19, a fix it by installing extra/plasma-wayland-protocols

TheOtherOne19 commented on 2025-11-07 13:05 (UTC)

It finally worked! It works with plasma-wayland and when it opens the window has the Xorg logo. It won't work neither with sway (wayland) nor with qtile (x11), so maybe the issue is related to the auto-tiling.

TheOtherOne19 commented on 2025-11-06 14:30 (UTC) (edited on 2025-11-06 14:31 (UTC) by TheOtherOne19)

Hi, I couldn't make it work with X11 no matter what I tried, so I installed sway and gave it a try. It throws the exact same error when run on Wayland. Now I don't know how to proceed.

vitaliikuzhdin commented on 2025-10-26 21:57 (UTC)

@TheOtherOne19, I managed to get it running on an X session without any issues: https://files.catbox.moe/5j78jg.png

My setup is a standard Plasma installation, I just had to install plasma-x11-session. I have very few packages installed, so you might want to compare my list with yours to see what’s missing: https://pastebin.com/MDsbruay

TheOtherOne19 commented on 2025-10-22 23:20 (UTC)

Hi, thanks for the help. I have wayland installed on my Xorg PC now but the exact same error persists. I'll investigate how other Xorg users aproach running wayland apps when this happends, as it as my first time with this kind of issue. If I find a way to make work again I'll come back.

vitaliikuzhdin commented on 2025-10-22 21:41 (UTC)

@TheOtherOne19, I previously had wayland listed as an optional dependency, but I pushed an update two days ago that now makes it mandatory. Could you please try updating and see if that fixes the issue for you? Honestly, if this still doesn’t work, I’m not sure how else to approach it. I’ve only ever dealt with issues running Xorg-based apps on Wayland, not the other way around, since I haven’t used Xorg much.

TheOtherOne19 commented on 2025-10-22 20:51 (UTC)

Hi, both vanilla Arch setups use Xorg, while Garuda uses Wayland. So that may be the cause of this problem. I tried commenting the packages outputed by pacman -Q, that are unique to the Garuda setup, but that exceeds the 5000 character limit.

1 2 Next › Last »