-
-
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
[5.x] AppImage fails to start on LINUX #19837
Comments
I have this issue on a trixie install too. 5.6.0 and 5.8.1 appImages affected. Apt logs have a bunch of updates to qt6 on 10/26. libqt6opengl6? |
I am having the same issue on Trixie, with 5.8.1 and 5.9.0-Beta1 As a normal user and under Sudo.... |
Same issue here with Debian Trixie and 5.8.1. Output of --debug attached. |
This seems to happen only on AMD GPUs, not necessarily just on trixie. This happens even on the older
|
I've an Intel CPU (core I7 6700K) with an integrated GPU (HD Graphics 530),
and I've the problem with debian sid.
It used to work (Ultimaker Cura 5.8.0) on the same hardware
Regards
Jean-Luc
Le mar. 5 nov. 2024 à 21:26, TheRealOne78 ***@***.***> a
écrit :
… This seems to happen only on AMD GPUs, not necessarily just on trixie.
This happens even on the older modern builds
—
Reply to this email directly, view it on GitHub
<#19837 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABRCJ4BQ5H3LDPXQDLMOKGTZ7ESZHAVCNFSM6AAAAABQ4VVD62VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJYGA4TCMBWGY>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
I also have the problem on Intel GPU (8. gen CPU with Intel UHD Graphics 620). Both systems have latest Debian Trixie. The problem startet with an recent apt upgrade where some libqt6 packages were updated. |
I just made an
So I turned to latest AppImage, and got the same issue as described here (Could not initialize GLX) on a core2duo with a HD6770:
--debug shows:
Same with I kept trying older versions, and the I hope that helps |
My debug results looks pretty much the same. |
Same here on Debian trixie on a Lenovo Laptop. But it fails with the same error.
|
This problem seams to be related to the libz3-4 package. Cura works with version 4.8.12-3.1+b2 but not with version 4.8.12-3.1+b3 and later. Because b3 is simply a rebuild with different tools and libraries, the real problem probably lies elsewhere but I've yet to find it. My work around for now is to extract libz3.so.4 from the b2 package and put it in a custom LD_LIBRARY_PATH when running cura. |
Confirmed. Works with older libz3-4_4.8.12-3.1_amd64.deb from debian 12 "bookworm" |
Unpacking the AppImage, dropping the libz3.so.4 from libz3-4_4.8.12-3.1_amd64.deb into there, and starting Cura with ./AppRun works too. |
Where is the bug though? In libz3-4 or somewhere else? |
Nah, it's just Cura being incompatible with a newer libz3-4 version, probably because of some function call change. |
Hello there, Just as a feedback, I can confirm those points (on Debian 13/Trixie up to date as 2024-12-06)
Congrats to @gigem for having found that! |
I have no libz3 library in my gentoo distro at all, but this error is present. libz3 is missing both in my system and in UltiMaker-Cura-5.9.0-linux-X64.AppImage. Moreover, libz3 has never been installed at all. |
same error here and no libz3! my guess is that this bug is related to amdgpu and not to libz3 |
I confirm this, because for me, from multiple systems running the same package versions but various intel/nvidia/amd GPUs, only systems which use AMD GPUs are affected. |
I also have an AMD GPU. |
I've a core i7-6700K with the integrated graphic attachment (Intel HD
Graphics 530/
And I've the problem.
Jean-Luc
Le mer. 18 déc. 2024 à 14:56, andrey ***@***.***> a écrit :
… only systems which use AMD GPUs are affected.
I also have an AMD GPU.
—
Reply to this email directly, view it on GitHub
<#19837 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABRCJ4ARIKITFIA37FAR6EL2GF5JPAVCNFSM6AAAAABQ4VVD62VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJRGM4DQOBYGA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Do you also have an AMD dedicated GPU, or just the integrated GPU?
… I've a core i7-6700K with the integrated graphic attachment (Intel HD
Graphics 530/
And I've the problem.
|
Nope
Le mer. 18 déc. 2024 à 18:33, TheRealOne78 ***@***.***> a
écrit :
… Do you also have an AMD dedicated GPU, or just the integrated GPU?
> I've a core i7-6700K with the integrated graphic attachment (Intel HD
> Graphics 530/
> And I've the problem.
—
Reply to this email directly, view it on GitHub
<#19837 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABRCJ4B2X3ZPACBL2SFDKYL2GGWVTAVCNFSM6AAAAABQ4VVD62VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJRHEYDINJRGI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
@t-cc If MESA is compiled with Rusticl the AppImage fails to start on some Intel/AMD iGPUs, so many distributions are affected! You can downgrade (no nice solution) mesa to an older version and the AppImage will start again. To fix this issue the code that initializes GLX should be updated to work with latest release of mesa. |
I can confirm the problem on Debian trixie (testing) with Intel HD Graphics 620. |
I managed to build Cura from source and run it successfully. How to create appimage? Documentation is lacking support on this topic. I have tried to use |
Cura Version
5.8.1
Operating System
Linux debian trixie, kde desktop
Printer
all printers
Reproduction steps
Try to start cura from the App Image file on debian trixie
Actual results
Expected results
Cura starts
Add your .zip and screenshots here ⬇️
stderr.log
The text was updated successfully, but these errors were encountered: