Fun installing and running Cura on a Chromebook...

[CathGaredig 0]

OK! So by wandering around all over the place, I finally figured out how to invoke the UltiMaker Cura app on my Chromebook (evil critter that it is). I gave it my 3D printer (Creality Ender-3 S1) and the app opened right up... and then I tried to load a file and got this:

 

PyInstaller/loader/pyimod02_importers.py:352: DeprecationWarning: the imp module is deprecated in favour of importlib and slated for removal in Python 3.12; see the module's documentation for alternative uses
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.
Cyclic dependency detected between "file:///home/bcmoorman/squashfs-root/share/cura/resources/qml/Actions.qml" and "file:///home/bcmoorman/squashfs-root/share/cura/resources/qml/Actions.qml"
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.
Segmentation fault (core dumped)

 

I could use an assist, please. My main laptop has let out its Magic Smoke and will no longer stay booted, because it's an HP and several years old; I'm using this li'l Chromebook until I can get the main desktop up and running, and I can only reprint the dragon I printed last week, because it's the only printable file on my SD card. AIEEEEE!!!  I don't think there's enough PLA on my roll to finish the dragon, as it was resized to "BIIIG DRAGON" sized (maximum size I could get on the print plate). It took about 30+ hours to print, and I'm not willing to risk a 30+ hour print because I don't know what my S1 will do when it runs out of filament.... 

 

Thanks in advance!

~Sal

 

[Slashee_the_Cow 438]

Cura isn't officially supported on Chromebooks. There's a long thread of various problems and potential solutions people have had here. I haven't read through that whole thread, but in your case I'm not sure it's going to be fixable without messing up the rest of the device (changing screen IDs in the settings for whatever Wayland compositor it's using).