Не запускается cyberpunk 2077 отчет об ошибке

➜  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

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}

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

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 

QT_QPA_PLATFORM=xcb LD_PRELOAD=/lib64/libstdc++.so.6 ./Ultimaker-Cura-5.0.0-linux.AppImage

Copy link

Contributor

Author

Copy link

Contributor

Author

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

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

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).

Copy link

Contributor

Author

Copy link

Contributor

Author

Copy link

Contributor

Author

Copy link

Contributor

Author

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

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.

Copy link

Contributor

Author

Copy link

Contributor

Author

you need to use LD_PRELOAD, not LD_LIBRARY. But I’ve had a discussion with the AppImage Core developer on Twitter and they’ve pointed nallath towards a solution that will allow dynamic loading of of system libstdc++ if needed.

Gesendet von ProtonMail mobile

…

Copy link

Contributor

Author

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

Copy link

Contributor

Author

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

Copy link

Contributor

Author

Copy link

Contributor

Author

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

Personally as an end user I think you’re just lacking the courtesy to your fellow community members trying to follow specific issues that are being tracked by word salading everything in here. Contrary to you I made an effort to understand the issue and helped find a fix for future releases, and I’m only interested to read about progress on this issue here.

So besides the fact that you’re incredibly rude to the developers on this project, you’re also making it hard for me to follow this specific issue by insisting to treat this issue as if you owned it. You don’t.

Gesendet von ProtonMail mobile

…

Copy link

Contributor

Author

@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.

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

5.1 still can’t launch on its own and with the patching out from the appimage fix, the saving of gcode doesnt work

@Miosame I’m gonna need a bit more specific information, regarding the version. Which build number are you using and which of the AppImage did you try. The regular AppImage or did you try the latest-Linux?

Can you try the AppImage called latest-Linux from this run https://github.com/Ultimaker/Cura/actions/runs/2666506668

Should be finished in ~20 minutes or so.
If the problem still occurs then please upload your logs as well.

Ah, Cura 4.13.1 is working fine.

getting a segfault on arch linux with that

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)

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

I am having this exact same issue.
Using Debian 11

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.

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

Copy link

Contributor

Author

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

Copy link

Contributor

Author

@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

Copy link

Contributor

Author

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?

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.

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.

Copy link

Contributor

Author