-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UltiMaker Cura is not a proper AppImage #18280
Comments
I get the same message also, on Debian Testing with appimaged 817. Cura does run fine though. |
Uh. That's a very... helpfull message from the OS. Is there any way that it can tell us why it believes it to be an invalid appimage? |
Looks like the message is coming from here: |
This file seems to throw the error: https://github.com/probonopd/go-appimage/blob/09fd0186774aefa2351c42b4bb22f92ce0c4f235/internal/helpers/updateinformation.go It seems to be related to update information, so yeah it has no impact on usability, but also seems like a simple fix (but I have no experience with building AppImages). Edit: Line 92 specifically which get called when |
So the stephen@Stephens-PC:~/Applications$ readelf -p .upd_info UltiMaker-Cura-5.6.0-linux-X64.AppImage
String dump of section '.upd_info':
[ 0] guess
stephen@Stephens-PC:~/Applications$ readelf -p .upd_info balenaEtcher-1.7.9-x64.AppImage
String dump of section '.upd_info':
No strings found in this section. Although I feel like appimaged should skip validation when the method isn't supported, unless |
GitHub's search reveals this line to be the likely problem:
I'd recommend removing it, or setting it to |
Cura Version
5.6.0
Operating System
Pop!_OS 22.04
Printer
Lulzbot TAZ 6
Reproduction steps
~/Applications/
Actual results
See system notice
Cura runs fine otherwise except the changelog splash screen appears at every launch.
Expected results
No system notice
Add your .zip and screenshots here ⬇️
cura.log
The text was updated successfully, but these errors were encountered: