Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Cura 5.0 AppImage won't launch (summary of worakrounds are in the end of the first message) #11856

Closed
leoheck opened this issue Apr 21, 2022 · 170 comments
Closed

Cura 5.0 AppImage won't launch (summary of worakrounds are in the end of the first message) #11856

leoheck opened this issue Apr 21, 2022 · 170 comments
Labels
Type: Bug The code does not produce the intended behavior.

Comments

@leoheck
Copy link
Contributor

leoheck commented Apr 21, 2022 •
edited
Loading

Cura 5.0 won't launch, see the console log.
Currently using ./Ultimaker-Cura-5.0.0-linux.AppImage

➜  Applications ./Ultimaker-Cura-5.0.0-linux.AppImage 
PyInstaller/loader/pyimod03_importers.py:495: 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
libGL error: MESA-LOADER: failed to open iris: /tmp/.mount_UltimaXxmREJ/libstdc++.so.6: version `GLIBCXX_3.4.30' not found (required by /lib/x86_64-linux-gnu/libLLVM-13.so.1) (search paths /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri)
libGL error: failed to load driver: iris
libGL error: MESA-LOADER: failed to open iris: /tmp/.mount_UltimaXxmREJ/libstdc++.so.6: version `GLIBCXX_3.4.30' not found (required by /lib/x86_64-linux-gnu/libLLVM-13.so.1) (search paths /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri)
libGL error: failed to load driver: iris
libGL error: MESA-LOADER: failed to open swrast: /tmp/.mount_UltimaXxmREJ/libstdc++.so.6: version `GLIBCXX_3.4.30' not found (required by /lib/x86_64-linux-gnu/libLLVM-13.so.1) (search paths /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri)
libGL error: failed to load driver: swrast
^Z
[1]  + 768770 suspended  ./Ultimaker-Cura-5.0.0-linux.AppImage

image

Possible workarounds

  • Ubuntu 18.04
  • Mint 19.3
  • Ubuntu 22.04 (good on X11, sure how it works on Wayland/Xwayland)
  • Manjaro 21.2.6.1
  • Arch

This requires appimagetool

AppImage=./Ultimaker-Cura-5.0.0-linux.AppImage
./${AppImage} --appimage-extract 
mv squashfs-root/libstdc++.so.6 squashfs-root/libstdc++.so.6.removed
./appimagetool-x86_64.AppImage squashfs-root 
mv -f Ultimaker_Cura-x86_64.AppImage ${AppImage}
  • Debian 12.0
LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libstdc++.so.6 ./Ultimaker-Cura-5.0.0-linux.AppImage
  • Fedora 36
LD_PRELOAD=/usr/lib64/libstdc++.so.6 ./Ultimaker-Cura-5.0.0-linux.AppImage
# Reported on KDE with Wayland and Intel graphics.
QT_QPA_PLATFORM=xcb LD_PRELOAD=/usr/lib64/libstdc++.so.6 ./Ultimaker-Cura-5.0.0-linux.AppImage
  • OpenSuse Tumbleweed
QT_QPA_PLATFORM=xcb LD_PRELOAD=/lib64/libstdc++.so.6 ./Ultimaker-Cura-5.0.0-linux.AppImage
@leoheck leoheck added the Type: Bug The code does not produce the intended behavior. label Apr 21, 2022
@leoheck
Copy link
Contributor Author

leoheck commented Apr 21, 2022

Also, there is no new icon, there is no icon, nothing.
It is the second icon here.
image

@leoheck
Copy link
Contributor Author

leoheck commented Apr 21, 2022

Ah, Cura 4.13.1 is working fine.

@nallath
Copy link
Member

nallath commented Apr 22, 2022 •
edited
Loading

Could you try if LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libstdc++.so.6 ./Ultimaker-Cura-5.0.0-beta+1-linux.AppImage

Fixes it? We already had one report that this would resolve it. It's not a proper fix, but it might work as a workaround

@nallath nallath mentioned this issue Apr 22, 2022
Closed
2 tasks
@TechNomad615
Copy link

I just tried the LD_PRELOAD and received this error:
LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libstdc++.so.6 ./Ultimaker-Cura-5.0.0-beta+1-linux.AppImage
ERROR: ld.so: object '/usr/lib/x86_64-linux-gnu/libstdc++.so.6' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/usr/lib/x86_64-linux-gnu/libstdc++.so.6' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/usr/lib/x86_64-linux-gnu/libstdc++.so.6' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/usr/lib/x86_64-linux-gnu/libstdc++.so.6' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/usr/lib/x86_64-linux-gnu/libstdc++.so.6' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
PyInstaller/loader/pyimod03_importers.py:495: 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: EGL not available

@oliof
Copy link
Contributor

oliof commented Apr 22, 2022

This is an issue with library incompatibilities between the graphics drivers and libstdc++ that comes with the AppImage. FreeCAD AppImage (any AppImage with applications requiring shared library loading between the App and your X11/Wayland environment) has the same issue.

As Ubuntu 22.04 was released today only, it's only partially surprising that it is not fully supported IMO.

The LD_PRELOAD workaround above worked for me on pop!_os 22.04 which is based on Ubuntu 22.04 (and also still in beta). You may need to find the right path to the libstdc++ your graphics drivers use to make it work.

This issue is inherent with AppImage. According to the AppImage best practice you should package the standard libs that cover the oldest OS release you want to support. That this breaks shared library loading for people that use current graphics hardware and driver libraries seems of little import to them.

From my point of view, Ultimaker has two options, neither of them compelling:

  1. Build Cura on the now released Ubuntu 22.04. This may or may not break the build on older releases and requires investigation how far back a build is supported.

  2. Provide multiple builds which will lead to confusion when people try to run the wrong build.

(and to cut to the chase, neither flatpack nor snap are free from issues either, so switching the packager is not a solution IMO).

@leoheck
Copy link
Contributor Author

leoheck commented Apr 22, 2022

@nallath the following process does not solve for me.

LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libstdc++.so.6 ./Ultimaker-Cura-5.0.0-beta+1-linux_c714ec65293e8f948ace6fd69440b1d4.AppImage

@leoheck
Copy link
Contributor Author

leoheck commented Apr 22, 2022

@oliof cool, these are the libs I could find. None of them are working with Cura 5.0, however, Cura 4.13 does work without any special setup. Maybe something else is missing in this AppImage. And yes, I saw the same issue with the Appimage of FreeCad

➜  Applications sudo find /usr -name "libstdc++*"   
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.30
/usr/lib/gcc/x86_64-linux-gnu/11/libstdc++.so
/usr/lib/gcc/x86_64-linux-gnu/11/libstdc++.a
/usr/lib/gcc/x86_64-linux-gnu/11/libstdc++fs.a

@leoheck
Copy link
Contributor Author

leoheck commented Apr 22, 2022

Ah, it is related with the graphics card. Alright. I will have to check how it works because I am using NVIDIA drivers.

@leoheck
Copy link
Contributor Author

leoheck commented Apr 22, 2022 •
edited
Loading

Weird that my lib has a reference to this GLIBCXX_3.4.30

➜  Applications strings /usr/lib/x86_64-linux-gnu/libstdc++.so.6 | grep GLIBCXX
GLIBCXX_3.4
GLIBCXX_3.4.1
GLIBCXX_3.4.2
GLIBCXX_3.4.3
GLIBCXX_3.4.4
GLIBCXX_3.4.5
GLIBCXX_3.4.6
GLIBCXX_3.4.7
GLIBCXX_3.4.8
GLIBCXX_3.4.9
GLIBCXX_3.4.10
GLIBCXX_3.4.11
GLIBCXX_3.4.12
GLIBCXX_3.4.13
GLIBCXX_3.4.14
GLIBCXX_3.4.15
GLIBCXX_3.4.16
GLIBCXX_3.4.17
GLIBCXX_3.4.18
GLIBCXX_3.4.19
GLIBCXX_3.4.20
GLIBCXX_3.4.21
GLIBCXX_3.4.22
GLIBCXX_3.4.23
GLIBCXX_3.4.24
GLIBCXX_3.4.25
GLIBCXX_3.4.26
GLIBCXX_3.4.27
GLIBCXX_3.4.28
GLIBCXX_3.4.29
GLIBCXX_3.4.30
GLIBCXX_DEBUG_MESSAGE_LENGTH

But it looks like when I run Cura, it uses a lib from inside the AppImage.

➜  Applications LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libstdc++.so.6 ./Ultimaker-Cura-5.0.0-beta+1-linux_c714ec65293e8f948ace6fd69440b1d4.AppImage
PyInstaller/loader/pyimod03_importers.py:495: 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
libGL error: MESA-LOADER: failed to open iris: /tmp/.mount_Ultimap8B3jp/libstdc++.so.6: version `GLIBCXX_3.4.30' not found (required by /lib/x86_64-linux-gnu/libLLVM-13.so.1) (search paths /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri)
libGL error: failed to load driver: iris
libGL error: MESA-LOADER: failed to open iris: /tmp/.mount_Ultimap8B3jp/libstdc++.so.6: version `GLIBCXX_3.4.30' not found (required by /lib/x86_64-linux-gnu/libLLVM-13.so.1) (search paths /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri)
libGL error: failed to load driver: iris
libGL error: MESA-LOADER: failed to open swrast: /tmp/.mount_Ultimap8B3jp/libstdc++.so.6: version `GLIBCXX_3.4.30' not found (required by /lib/x86_64-linux-gnu/libLLVM-13.so.1) (search paths /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri)
libGL error: failed to load driver: swrast

See, it is using /tmp/.mount_Ultimap8B3jp/libstdc++.so.6 instead of the one I am preloading /usr/lib/x86_64-linux-gnu/libstdc++.so.6

The one I am preloading exists on my system. See:

➜  Applications ls -lsa /usr/lib/x86_64-linux-gnu/libstdc++.so.6                                                                      
1 lrwxrwxrwx 1 root root 19 Mar 19 07:36 /usr/lib/x86_64-linux-gnu/libstdc++.so.6 -> libstdc++.so.6.0.30

➜  Applications ls -lsa /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.30
1137 -rw-r--r-- 1 root root 2260320 Mar 19 07:36 /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.30

@oliof
Copy link
Contributor

oliof commented Apr 22, 2022

Yes, that is how AppImage works, it collects the runtime and standard libraries from the system it is built on. and GLIBCXX_3.4.30 is not covered in the one that's included here because it wasn't part of Ubuntu releases prior to 22.04 which wasn't a stable release until today.

No idea why the LD_PRELOAD workaround does not work on your machine, since I have the same layout. Here is the wrapper script I use to reference in my .desktop file (but it also can be used on the command line of course):

#!/bin/bash
LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libstdc++.so.6 <path_to>/AppImages/Ultimaker-Cura-5.0.0-beta+1-linux.AppImage

I am using an absolute path, but I have confirmed that it also works when I use a relative path. Since your shell prompt looks slightly non-default in your examples, maybe you are not using bash?

running it yields the following output, and Cura 5 starts up fine:

PyInstaller/loader/pyimod03_importers.py:495: 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
Cyclic dependency detected between "file:///tmp/.mount_UltimaLZurP1/share/cura/resources/qml/Actions.qml" and "file:///tmp/.mount_UltimaLZurP1/share/cura/resources/qml/Actions.qml"
QQmlEngine::setContextForObject(): Object already has a QQmlContext

@oliof
Copy link
Contributor

oliof commented Apr 22, 2022

FWIW I went through building an AppImage using Cura Build Environment on pop!_os 22.04 and as expected that launches without error. I do not have access to older environments to check whether this would run on 20.04 / 18.04 releases.

It misses some built-in plugins, but that's more likely due to my lack of experience with the build system than anything else.

@leoheck
Copy link
Contributor Author

leoheck commented Apr 22, 2022

could you share your appimage so I can test it on my system @oliof ?

@leoheck
Copy link
Contributor Author

leoheck commented Apr 25, 2022 •
edited
Loading

I was able to run it. It looks like preloading the system lib with LD_PRELOAD is doing nothing on my system.

AppImage=./Ultimaker-Cura-5.0.0-linux_07ecc3f54905e865167d2bcd7cfe459c.AppImage

# Extract the package
${AppImage} --appimage-extract 

# Remove (rename) libstdc out of the sight... 
mv squashfs-root/libstdc++.so.6 squashfs-root/libstdc++.so.6.removed

# Recreate the AppImage file (thanks luzpaz)
./appimagetool-x86_64.AppImage squashfs-root 

# Rename generated AppImage to the original name
mv -f Ultimaker_Cura-x86_64.AppImage ${AppImage}

Edit: Added a script to fix the AppImage since it is not launching at all on Ubuntu 2022.04.

@oliof
Copy link
Contributor

oliof commented Apr 25, 2022 via email

@leoheck
Copy link
Contributor Author

leoheck commented Apr 25, 2022

Please, looks this comment here: #11856 (comment)
This is the way I am trying. It does nothing on my system. I insist IT does not work as you people are proposing here.
On my system, the libstdc++.so that is inside the AppImage is not being replaced by my system's version of it.

@fvrmr
Copy link
Contributor

fvrmr commented Apr 26, 2022

Thank you all for reporting!
I created a ticket for this, devs see CURA-9205

@leoheck leoheck mentioned this issue Apr 29, 2022
Closed
@leoheck
Copy link
Contributor Author

leoheck commented May 2, 2022

Extra things I saw in this release

  • Desktop icon is missing.
  • Sign in to the Ultimaker platform is not working
  • Octoprint plugin is not working

@oliof
Copy link
Contributor

oliof commented May 2, 2022

the author of the Octoprint plugin has released a prerelease version that provides basic functionality (connectivity and upload of files), but requires more work. This is not surprising as all plugins need updating for Cura 5 due to the library and API changes.

The icon works in the task switcher, I don't see it anywhere else but I start Cura through a script so I don't know how that'd work

@leoheck
Copy link
Contributor Author

leoheck commented May 2, 2022 •
edited
Loading

Cura does not open .stl files too. I think it is not usable on Linux yet. Actually it does not do anything. It does not launch the file browser to load a file, it does not launch the popup window to login Ultimaker's website. It does nothing.

@oliof
Copy link
Contributor

oliof commented May 3, 2022 via email

@leoheck
Copy link
Contributor Author

leoheck commented May 3, 2022

I would love to open another issue @oliof , but there are too many fields and required things. Too much text I have to read.. seriously, this template to report issues, sucks all the energy I have to create the bug reports. I have already started a new issue here at least 4 times this week. But I dropped the idea after some time since I have to fill all those required things.

It is crazy that these things are getting horrible with time and are a show stopper for reporters like me. I do these things while I am working. So, it has to be quick and easy. And it can be improved later. This repo could at least have an alternative blank template to report issues, seriously.

@nallath
Copy link
Member

nallath commented May 3, 2022 •
edited
Loading

It is crazy that these things are getting horrible with time and are a show stopper for reporters like me. I do these things while I am working. So, it has to be quick and easy. And it can be improved later. This repo could at least have an alternative blank template to report issues, seriously.

You can use a blank one, but we would rather not have people use that. The amount of poor reports that we get without it is simply staggering. We also have to do this during work, so we want to make sure that we can do this somewhat efficient. With a blank template, we got people reporting "cura crashed" as the full set of information that they gave us (and if we were lucky, we got a very unhelpful screenshot from windows saying something like "Cura stopped responding"

I understand that it's a balancing act for both sides, but filling in the template takes less time than it does to write the post you just did ;)

@oliof
Copy link
Contributor

oliof commented May 3, 2022 via email

@leoheck
Copy link
Contributor Author

leoheck commented May 3, 2022 •
edited
Loading

but filling in the template takes less time than it does to write the post you just did ;)

@nallath Well, this is your opinion. Not a fact. But that is fine.

Personally as an end-user I think you're just lacking the courtesy to your fellow community members

@oliof I don't think you understand the point here. By the way, are you saying that you don't want to have users' feedback on issues and features? Because this is what I am getting here. Seriously. If you are saying that, those 1.6k issues that help to improve the platform are useless, right? Is this what you are saying?

What is the problem with having a way to submit a blank issue? This gives flexibility to users like me to want to contribute but don't have time to spend filling out useless forms.

I am not even asking you to fix these issues. I am just returning what I am seeing on the screen, so you can have your product improved. I am not asking or demanding anything. I am using my free time, to help you guys, to be aware of issues there your software is going to find when released. You should not treat users like that. Seriously.

But moving one here... why don't we have a blank template for reporting issues instead of jailing all users, who want to contribute to the project, forcing them to fill a poor form?

Gesendet vom Gmail Desktop

@oliof
Copy link
Contributor

oliof commented May 3, 2022

@leoheck I am not saying what you claim and your bad faith argument is not buying you any points.

As @nallath said, you can submit a blank template issue, but the developers ask you to use the template. You could consider being corteous, or ignoring the request and not use the template, or you can continue poisoning this issue. Either path reflects mostly on you.

Also, if you think you earn any points by insulting me although I am just a user of the product -- like you, only with some empathy for the developers -- I think you are mistaken. Seriously (-:

PS: To make it clear: I have no affiliation to Ultimaker or Cura other than being an end user. And I would like to follow this issue to see whether the library dependency issue on distributions derived from Ubuntu 22.04 will be resolved in a future beta release or not. I would like to follow other issues in, well, other issues.

@fvrmr fvrmr mentioned this issue May 4, 2022
Closed
2 tasks
@piontec
Copy link

piontec commented May 4, 2022

FYI: I'm on wayland on ubuntu 22.04 and I can start cura 5.0 beta AppImage with

LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libstdc++.so.6 cura-beta

but it fails when I configure for wayland:

➜  QT_QPA_PLATFORM=wayland LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libstdc++.so.6 cura-beta
PyInstaller/loader/pyimod03_importers.py:495: 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
/tmp/.mount_cura-bfnDvPl/Ultimaker-Cura: symbol lookup error: /lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined symbol: wl_proxy_marshal_flags

@jellespijker jellespijker mentioned this issue Jul 15, 2022
Open
2 tasks
This was referenced Jul 22, 2022
Closed
Closed
@wernight
Copy link

wernight commented Aug 7, 2022

On Crostini (Chromebook) running Debian based Linux, .Ultimaker-Cura_5.1.0-beta-linux.AppImage works perfectly but the final version doesn't due to this error. Also the workaround does not work:

$ LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libstdc++.so.6 ./Cura.AppImage 
/tmp/.mount_Cura.AY08IvS/Ultimaker-Cura: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.35' not found (required by /tmp/.mount_Cura.AY08IvS/libgcc_s.so.1)
/tmp/.mount_Cura.AY08IvS/Ultimaker-Cura: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /tmp/.mount_Cura.AY08IvS/libgcc_s.so.1)

@jellespijker
Copy link
Member

Devs see CURA-9516 for the ticket to make it one AppImage again

@krishnaTORQUE
Copy link

krishnaTORQUE commented Aug 29, 2022 •
edited
Loading

I am having this exact same issue.
Using Debian 11

@jellespijker jellespijker unpinned this issue Sep 4, 2022
@velechit
Copy link

velechit commented Oct 8, 2022 •
edited
Loading

Running Ubuntu 22.04, got this working. Not sure if this is going to break anything else.
(Requires appimagetool : https://github.com/AppImage/AppImageKit/releases )

  1. Extract the AppImage and replace the libstdc++.so.6 with the one on your system and recreate the appimage (this should solve OpenGL issue)
   > ./Ultimaker-Cura-5.2.0-beta.2-linux.AppImage --appimage-extract
   > mv squashfs-root/libstdc++.so.6 squashfs-root/libstdc++.so.6.removed
   > cp /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.30 squashfs-root/libstdc++.so.6
   > ./appimagetool-x86_64.AppImage squashfs-root
   > mv Ultimaker_Cura-x86_64.AppImage Ultimaker-Cura-5.2.0-beta.2-linux.AppImage
  1. Fix glib schema
   > cp /usr/share/glib-2.0/schemas ~/glib_schema.bck
   > sudo gvim /usr/share/glib-2.0/schemas/org.gnome.settings-daemon.plugins.xsettings.gschema.xml
  1. In this file, move the 3 keys from deprecated section to main section and re-compile the glib schema
   > sudo glib-compile-schemas /usr/share/glib-2.0/schemas

Now, the AppImage should run without any additinal changes.

I am not sure if moving the deprecated keys back to main causes any issues or breaks anything. anyone else if finds issue here please let me know.

@lotw69
Copy link

lotw69 commented Oct 9, 2022

Just download the flatpak version instead, works perfect on all distros

@leoheck
Copy link
Contributor Author

leoheck commented Oct 9, 2022

AppImage is also working too, at least for Ubuntu 22.04 (use the one that has Modern distro or something like this in its name)

@dmitrygribenchuk
Copy link
Contributor

Hey. Issue return with 5.2.2
LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libstdc++.so.6 also solve the problem

@leoheck
Copy link
Contributor Author

leoheck commented Feb 22, 2023 •
edited
Loading

@dmitrygribenchuk really? there is 2 versions.. one has the word modern in it's name, the other doesn't. Which one are you using? Can you try the other one?

@dmitrygribenchuk
Copy link
Contributor

@leoheck oh, my fault.
UltiMaker-Cura-5.2.2-linux-modern - working fine
I use Ubuntu 22.04

~/Downloads$ ./UltiMaker-Cura-5.2.2-linux.AppImage
PyInstaller/loader/pyimod02_importers.py:499: 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
libGL error: MESA-LOADER: failed to open iris: /usr/lib/dri/iris_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/x86_64-linux-gnu/dri:$${ORIGIN}/dri:/usr/lib/dri, suffix _dri)
libGL error: failed to load driver: iris
libGL error: MESA-LOADER: failed to open iris: /usr/lib/dri/iris_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/x86_64-linux-gnu/dri:$${ORIGIN}/dri:/usr/lib/dri, suffix _dri)
libGL error: failed to load driver: iris
libGL error: MESA-LOADER: failed to open swrast: /usr/lib/dri/swrast_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/x86_64-linux-gnu/dri:$${ORIGIN}/dri:/usr/lib/dri, suffix _dri)
libGL error: failed to load driver: swrast

~/Downloads$ ./UltiMaker-Cura-5.2.2-linux-modern.AppImage
PyInstaller/loader/pyimod02_importers.py:499: 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
Cyclic dependency detected between "file:///tmp/.mount_UltiMaYkfPUp/share/cura/resources/qml/Actions.qml" and "file:///tmp/.mount_UltiMaYkfPUp/share/cura/resources/qml/Actions.qml"
QQmlEngine::setContextForObject(): Object already has a QQmlContext

@leoheck
Copy link
Contributor Author

leoheck commented Feb 22, 2023

UltiMaker-Cura-5.2.2-linux-modern - working fine

@dmitrygribenchuk awesome. Cheers!

By the way, this "modern" could be explained better on the Releases page.

@ChaosBlades ChaosBlades mentioned this issue Feb 28, 2023
Open
2 tasks
@eGit
Copy link

eGit commented Jul 30, 2023

Does this solution also offer a workaround for us sad users stuck with GLIBC 2.27 for longer (I am not using a 18.04 derivate but a still supported distro with old GLIBC).

Cura 5.4 appimage that works with GLIBC 2.27 systems?

Would be nice. Why do we have AppImage if it can't fix this little hiccup?

@JordyProvost
Copy link

For me :

  • UltiMaker_Cura-5.3.0-alpha+xmas-linux-modern.AppImage is working fine
  • UltiMaker-Cura-5.4.0-linux.AppImage is not working
$ LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libstdc++.so.6 ./UltiMaker-Cura.AppImage 
Traceback (most recent call last):
  File "cura_app.py", line 28, in <module>
  File "PyInstaller/loader/pyimod02_importers.py", line 352, in exec_module
  File "cura/CrashHandler.py", line 24, in <module>
ImportError: /usr/local/mesa/23.1.4/lib/x86_64-linux-gnu/libEGL.so.1: undefined symbol: wl_proxy_marshal_flags
[637738] Failed to execute script 'cura_app' due to unhandled exception!

LD_PRELOAD, or remaking the image with the bash code below does not work.

AppImage=./UltiMaker-Cura.AppImage

# Extract the package
${AppImage} --appimage-extract 

# Remove (rename) libstdc out of the sight... 
mv squashfs-root/libstdc++.so.6 squashfs-root/libstdc++.so.6.removed
find /usr/lib/x86_64-linux-gnu/ -type f -iname libstdc++.so.* -exec cp "{}" squashfs-root/libstdc++.so.6 \;

# Recreate the AppImage file (thanks luzpaz)
./appimagetool-x86_64.AppImage squashfs-root 

# Rename generated AppImage to the original name
mv -f UltiMaker_Cura-x86_64.AppImage ${AppImage}

The issue was the same here :

#12081

But this one has been marked as duplicate, so im here and nothing seems to work....

Anyone to help me ?

Thanks in advance.

@leoheck
Copy link
Contributor Author

leoheck commented Aug 15, 2023

Hi @JordyProvost what is your Operating System and its version?

@JordyProvost
Copy link

JordyProvost commented Aug 18, 2023 •
edited
Loading

Hi @leoheck

Thanks for your answer.

I'm on Debian 12.1 bookworm, but i'm using Mesa 23.1.4 from git.

Regards,

@leoheck
Copy link
Contributor Author

leoheck commented Aug 18, 2023 •
edited
Loading

If this UltiMaker_Cura-5.3.0-alpha+xmas-linux-modern.AppImage is working fine, you should use this one:
UltiMaker-Cura-5.4.0-linux-modern.AppImage. Have you tried it?

@JordyProvost
Copy link

Omg, sorry, this was so obvious...its working flawlessly, thank you very much !
I will download from Github and not from the website anymore since the version proposed is not the "modern" one.

@leoheck
Copy link
Contributor Author

leoheck commented Aug 18, 2023

Awesome, have a good day dude.

@gcoppex gcoppex mentioned this issue Oct 18, 2023
Closed
2 tasks
@Hatsune-Cthulhu
Copy link

Guess they've just decided to stop releasing the -modern versions of the appimage. This should not be closed, it's still an issue.

@oliof
Copy link
Contributor

oliof commented Jun 16, 2024 via email

@Hatsune-Cthulhu
Copy link

they stopped releasing the -modern AppImage because they found a way to solve the issue using a single AppImage. Gesendet von Proton Mail für Android
…
-------- Ursprüngliche Nachricht -------- Am 16.06.24 13:17 um Hatsune Cthulhu schrieb :
Guess they've just decided to stop releasing the -modern versions of the appimage. This should not be closed, it's still an issue. — Reply to this email directly, [view it on GitHub](#11856 (comment)), or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>

Clearly they didn't fix it, otherwise I wouldn't be here asking about the -modern builds. I just updated and now I'm having to use environment variables to get it to work in Wayland.

@sadsephiroth
Copy link

they stopped releasing the -modern AppImage because they found a way to solve the issue using a single AppImage. Gesendet von Proton Mail für Android
…
-------- Ursprüngliche Nachricht -------- Am 16.06.24 13:17 um Hatsune Cthulhu schrieb :
Guess they've just decided to stop releasing the -modern versions of the appimage. This should not be closed, it's still an issue. — Reply to this email directly, [view it on GitHub](#11856 (comment)), or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>

Clearly they didn't fix it, otherwise I wouldn't be here asking about the -modern builds. I just updated and now I'm having to use environment variables to get it to work in Wayland.

Very correct, same issue in Arch with KDE for a while now.

@mechano
Copy link

mechano commented Oct 12, 2024

The problem appeared again on Ubuntu 24.10:

/tmp/.mount_UltiMaoolREW/UltiMaker-Cura: symbol lookup error: /lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined symbol: wl_display_create_queue_with_name

Cura is 5.8.1

@php4fan
Copy link

php4fan commented Oct 27, 2024

Why is this closed?? The latest appImage is still broken

@mechano
Copy link

mechano commented Oct 27, 2024 •
edited
Loading

You can find a workaround here:

#19739

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Type: Bug The code does not produce the intended behavior.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests