Chromebooks Linux virtual environment vs Cura

[NathanStenzel 0]

I was not able to use Cura on my Chromebook for at least a month now. I have tried a number of appimage versions including the current one. Is anyone else having better luck? Here is some of my system information followed by the error message for running the appimage. It was a similar error message for earlier versions.  I also tried to compile, but that did not go too well since Chromebooks easily run out of space and qt5.qml stuff not being in the Debian python packages list and this thing complaining about pip being an externally managed package management.

Asus Chromebook model CX22N
 
Linux version 6.6.30-02726-gb84bbdf6955e (cros-kernel@chromium.org) (Chromium OS 18.0_pre516547 clang version 18.0.0
My ChomeOS version is 126.0.6478.222 (Official Build) (64-bit)

 

Error message running the appimage:
 

/UltiMaker-Cura-5.8.1-linux-X64.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_UltiMaZ5D0tB/share/cura/resources/qml/Actions.qml" and "file:///tmp/.mount_UltiMaZ5D0tB/share/cura/resources/qml/Actions.qml"
The Wayland connection broke. Did the Wayland compositor die?

[Slashee_the_Cow 442]

Cura is not supported on Chromebooks. Their Linux environment is significantly different to a native Linux installation which, as you can see, can lead to various errors. The Linux environment is also updated at Google's whim and vital components may change without warning.

[Dustin 160]

https://support.ultimaker.com/s/article/1667337917781
Chrome OS has always been listed as not supported.

I just updated the article to include call out for chromebooks directly as well, as people don't always realize its same problem.
 

[NathanStenzel 0]

Well, I tried to install it on my desktop computer in a Docker but that had slicing break on slicing. There are not any other interface layers else than your Uranium one, is there? I imagine I could run cura-engine, but it is the interface that is an issue.
I never cared for the minimum window size of Cura. It conflicts with my text and screen resolution settings for my vision. There are no scroll bars either.
Maybe if there were other projects for the interface level or a how to for the topic, I could even help out with other interfaces.

[Slashee_the_Cow 442]

2 hours ago, NathanStenzel said:

There are not any other interface layers else than your Uranium one, is there? I imagine I could run cura-engine, but it is the interface that is an issue.

The main build based on Uranium is AFAIK the only official build of the Cura interface. I don't know of any forks or manufacturer-branded versions of Cura that run a completely custom interface (as opposed to a thoroughly themed version of it, like earlier versions of Creality Print), but I don't know all the forks and manufacturer-branded versions of Cura (I do know to hate Elegoo's Cura fork though.) If there are any then @ahoeben is probably the most likely (at least of the regular forum-ites) to know.

 

2 hours ago, NathanStenzel said:

Well, I tried to install it on my desktop computer in a Docker but that had slicing break on slicing.

Could it be Cura doesn't invoke CuraEngine from the command line but rather opens it at the start and connects over a localhost network port have anything to do with that? If you look at the cura.log file in the Cura configuration folder it'll show you what port CuraEngine is listening on, you might have to open that. And maybe run a packet capture if you want to see everything Cura is sending to CuraEngine.

 

2 hours ago, NathanStenzel said:

Maybe if there were other projects for the interface level or a how to for the topic, I could even help out with other interfaces.

To the best of my knowledge (I know a bit about programming, but I'm not involved in Cura development at all) the Cura interface and CuraEngine aren't intertwined, Cura just calls CuraEngine as required, so you just need to make your own calls.

 

Building an entirely new front-end from scratch would be a pretty big undertaking though.

[Dustin 160]

Docker is a virtualized environment.. I know it was not explicitly called out on the article.. but it was inferred under "Virtual Environments" 

I have updated the article to call this out directly and to be more clear about it.
 

[NathanStenzel 0]

20 hours ago, Slashee_the_Cow said:

Could it be Cura doesn't invoke CuraEngine from the command line but rather opens it at the start and connects over a localhost network port have anything to do with that? If you look at the cura.log file in the Cura configuration folder it'll show you what port CuraEngine is listening on, you might have to open that. And maybe run a packet capture if you want to see everything Cura is sending to CuraEngine.

 

To the best of my knowledge (I know a bit about programming, but I'm not involved in Cura development at all) the Cura interface and CuraEngine aren't intertwined, Cura just calls CuraEngine as required, so you just need to make your own calls.

It would be nice if the Cura-engine github page had details on that. I am not seeing anything.