Arch Linux User Repository

Apologies for not getting back to everyone sooner, I was quite sick for a couple of months (thankfully better now).

@sbrl: This does appear to be an issue with upstream, or possibly not an issue if AppImage simply started including a more complete mini distribution? Either way, at least some of the libraries are getting depended upon and it would be a difficult task to work through and separate out which files are strictly necessary and which aren't (even if it launched, there's no guarantee some option wouldn't expect the library or binary). I could probably delete the etc folder on that note, but it wouldn't recover much disk space. I'm open to suggestions though!

@Richardk2n: Thanks for figuring out the cause and sharing your solution!

@Richardk2n

Same problem here. I found that I had Arch package appimagelauncher-bin stuck in version 2.0-something. Removed, installed AUR appimagelauncher, everything works.

Since 1 version after 5.10.1-1 of this package, the PKGBUILD seems to generate a large number of additional file on the filesystem compared to the aforementioned version.

is this a bug in the PKGBUILD or upstream?

Additional file list: https://pastebin.com/xBXNFGbd

This just concerned me as the package seems to erroneously contain e.g. journalctl etc which seems anomalous to me.

Tested with build via rua of version 5.10.2-1, full generated filename cura-bin-5.10.2-1-x86_64.pkg.tar.zst.

Looks like AppImageLauncher is outdated and does not support new compressions yet. A problem since January at least. Found multiple issues on github about this. Maybe there is some exec magic possible to bypass the call of AppImageLauncher.

@sausix Tried that without success.

But made me google the correct thing.

Apparently, when you have AppImageLauncher installed, newer AppImages will not work at all anymore.

An uninstall and reboot fixed the issue.

@Richardk2n Works for me. Try deleting the AUR cache. Maybe some downloaded file is broken. Run the commands of prepare() in the PKGBUILD manually to find the issue.

Does not update for me

This doesn't look like a squashfs image.

Any idea, what this could mean?

Hi everybody!

Thanks for your comments. I will use xwayland for now and will investigate the issue further with the cura people. If I find something relevant I'll let you know.

Thanks again!

It's running on XWayland forcefully because of this change: https://github.com/Ultimaker/Cura/commit/55feaaf8b1af49a3e92cc5b9de8c2ee5decd8b93

You can edit /opt/ultimaker-cura/AppRun.env and remove or comment out that line. But at least for me (NVidia user) Cura does not run on pure Wayland "again":

QEGLPlatformContext: Failed to create context: 3009 and the 3D area is white again.

Deleting wayland related so-files inside the package files did not help. I think it's related to the PyQt6 version inside the AppImage. It ships some binaries related to Wayland.

Hard to debug something like that. Ultimakter probably forces to XWayland because is runs best for the majority. In fact XWayland on NVidia does not flicker anymore. So at least for me running Cura in XWayland is ok for now.

I can confirm: No matter what I try, Cura always starts in Xwayland mode running on labwc 0.9.0. It’s reliable, though. That’s all that matters.