Unable to Run Ultimaker Cura on ChromeOSFlex

[kafufafu]

After a successful installation, I am unable to execute Ultimaker Cura. When I try to run it in the terminal, I receive the following information:

ChromeOsFlex Versión 123.0.6312.132 (Build oficial) (64 bits)

kazukimafufafu@penguin:~$ flatpak install flathub com.ultimaker.cura Looking for matches…

com.ultimaker.cura permissions: ipc network wayland x11 devices file access [1] system dbus access [2]

[1] /media, /run/media, home
[2] org.freedesktop.UDisks2

    ID                          Branch         Op         Remote          Download

1. [✓] com.ultimaker.cura stable i flathub 350.8 MB / 400.0 MB

Installation complete. kazukimafufafu@penguin:~$ flatpak run com.ultimaker.cura Fontconfig warning: "/etc/fonts/conf.d/05-flatpak-fontpath.conf", line 5: unknown element "reset-dirs" Fontconfig error: "/etc/fonts/conf.d/05-flatpak-fontpath.conf", line 6: invalid attribute 'salt' Fontconfig error: "/etc/fonts/conf.d/05-flatpak-fontpath.conf", line 7: invalid attribute 'salt' Fontconfig warning: "/run/host/font-dirs.xml", line 4: unknown element "remap-dir" Fontconfig error: "/run/host/font-dirs.xml", line 4: invalid attribute 'as-path' Fontconfig warning: "/run/host/font-dirs.xml", line 5: unknown element "remap-dir" Fontconfig error: "/run/host/font-dirs.xml", line 5: invalid attribute 'as-path' Fontconfig error: Cannot load config file from /run/host/font-dirs.xml Fontconfig warning: "/etc/fonts/conf.avail/05-reset-dirs-sample.conf", line 6: unknown element "reset-dirs" qt.qpa.wayland: Ignoring unexpected wl_surface.enter received for output with id: 7 screen name: "Screen5" screen model: "unknown" This is most likely a bug in the compositor. qt.qml.typeresolution.cycle: Cyclic dependency detected between "file:///app/cura/share/cura/resources/qml/Actions.qml" and "file:///app/cura/share/cura/resources/qml/Actions.qml" The Wayland connection broke. Did the Wayland compositor die?

---

Could you please provide assistance in resolving this issue? Thank you for your help and assistance with this matter!

[Tim453]

Does the official AppImage work? Here someone else had the same problem.

[Tim453]

Can you also try if the 5.7.0 AppImage works?

[kafufafu]

Can you also try if the 5.7.0 AppImage works?

I have tested the following .AppImage versions:

Version 5.6.0 (starts correctly). Version 5.7.0 (fails to start). Version 5.7.1 (fails to start). The error in versions 5.7.X is the following in both cases:

kazukimafufafu@penguin:~$ ./5.7.1.AppImage qt.qpa.wayland: Ignoring unexpected wl_surface.enter received for output with id: 7 screen name: "Screen5" screen model: "unknown" This is most likely a bug in the compositor. qt.qml.typeresolution.cycle: Cyclic dependency detected between "file:///tmp/.mount_5.7.1.0m9fDF/share/cura/resources/qml/Actions.qml" and "file:///tmp/.mount_5.7.1.0m9fDF/share/cura/resources/qml/Actions.qml" The Wayland connection broke. Did the Wayland compositor die?

[Farroner1]

I have tested the following .AppImage versions: Version 5.6.0 (starts correctly). Version 5.7.0 (fails to start). Version 5.7.1 (fails to start).

Exactly the same behavior on a Chromebook with Debian 12 (Bookwork). 5.6.0 runs, the newer versions do not

[kafufafu]

@Farroner1

1) I finally ended up using Ubuntu and version 4.13.2 available from the app store. I'm increasingly convinced that it's a problem in the source code and opted to stop trying after breaking the system multiple times lol.

2) The current status of Ultimaker Cura 5.7.1 is: it doesn't work on most Linux distros and doesn't work on some computers with Windows 11.