flathub / com.ultimaker.cura Goto Github PK

Updated Cura to 5.5.0 and noticed that GUI wouldn't launch. Running from command line results in:

neil@vivobook:~> flatpak run com.ultimaker.cura
PyInstaller/loader/pyimod02_importers.py:352: 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
Fontconfig warning: "/etc/fonts/conf.d/05-flatpak-fontpath.conf", line 5: unknown element "reset-dirs"
Fontconfig error: "/etc/fonts/conf.d/05-flatpak-fontpath.conf", line 6: invalid attribute 'salt'
Fontconfig error: "/etc/fonts/conf.d/05-flatpak-fontpath.conf", line 7: invalid attribute 'salt'
Fontconfig warning: "/run/host/font-dirs.xml", line 4: unknown element "remap-dir"
Fontconfig error: "/run/host/font-dirs.xml", line 4: invalid attribute 'as-path'
Fontconfig error: Cannot load config file from /run/host/font-dirs.xml
Fontconfig warning: "/etc/fonts/conf.avail/05-reset-dirs-sample.conf", line 6: unknown element "reset-dirs"
Cyclic dependency detected between "file:///app/cura/share/cura/resources/qml/Actions.qml" and "file:///app/cura/share/cura/resources/qml/Actions.qml"
/app/bin/start-cura-flatpak.sh: line 2:     3 Segmentation fault      (core dumped) /app/cura/AppRun "$@"

Environment
OS: openSUSE Aeon
Desktop: GNOME 45
Session: Wayland

Ultimaker has just released Cura 5.2.0:
https://github.com/Ultimaker/Cura/releases/tag/5.2.0

With the upcoming Cura release 5.0, Cura will be updating its Python version to 3.10.0 and Qt to version 6.2. We're packaging the new versions inside of the AppImage.

This update is necessary to support the new MacOS versions. It is not necessary to continue supporting Linux, so it's not really a problem here. However this update means that some code will eventually be written that only works in the newest versions of these dependencies. These are the major dependencies that we're updating that might be relevant to this repository:

• Qt and PyQt are updated to version 6.2.0. This means code breakage: It's importing PyQt6 everywhere, so PyQt6 needs to be available instead of PyQt5.
• Python is updated to 3.10.0. For the moment, it's kept backwards compatible with at least Python 3.9 (which is the one used here, looking at the patches made). No guarantees for the future though, so you might want to update the Python version and references to 3.9.
• Sip is updated to 6.5.0. This is a really big change in the way we build the Python bindings for some C++ libraries Cura uses. Externally though, not a whole lot should change. In theory, CMake should just build it from scratch, as long as Sip 6.5 is available.
• Shapely (the Python package) is replaced by Pyclipper (because until very recently they didn't support Python 3.10 yet on MacOS). This itself is not a difficult change, just a different package to request from Pip. However it also drops the need for Geos. Geos is no longer a dependency. This probably speeds up your build a bit.
• Many Python packages have been updated. This is necessary to support Python 3.10.

As of this writing, we're still having some trouble packaging the MacOS image with the updated Sip version, but these changes are likely to remain stable at this point.

Until Cura 4.13.1 the flatpak could be build entirely from the source code. With version 5.0 Ultimaker started using conan in their build system, which does not work well with flatpak-builder. Since than the Flatpak is build by just extracting the offical AppImage into the Flatpak enviorment. It would be nicer if a way is found to build the Cura flatpak from source code. This would also bring back the support for aarch64. Ultimaker even offered to integrate Flatpak specific parts into their Repo.

For more information:
Conan Flatpak examples
Manifest of Cura 4.13.1

I just discovered a bug after upgrading to Cura 5.3.1, which causes my entire system to crash, whenever I click preview for a sliced project. I described it in Cura issue 15311 (there also are logs included).
I think it might be related to some flatpak permission issue, because the AppImage of the same version works on my pc and in the logs before the crash Cura complains with
2023-04-21 09:27:50,053 - WARNING - [JobQueueWorker [1]] USBPrinting.AutoDetectBaudJob.run [56]: serial.serialutil.SerialException: [Errno 13] could not open port /dev/ttyS0: [Errno 13] Permission denied: '/dev/ttyS0'

I would greatly appreciate if this could be addressed since I prefer using the flatpak version to the AppImage.

See flatpak/flatpak#4763

Currently, the Cura Flatpak exports a worse mime-type description with no translations to the system when a better one already exists in the upstream shared-mime-info package. This could probably be removed in this package and upstream.

Currently, plugins dependent on external binaries don't work. For example, the AutoTowers Generator plugin requires an openscad binary to be available in $PATH, this plugin is in the top 10 most popular Cura plugins.

I'm not sure about the policy of exposing host binaries to flatpaks, but I see that the FreeCAD OpenSCAD Workbench was in the same situation and a fix was merged, so maybe we can have it for Cura as well.

I haven't tried building flatpaks before, but I can follow flathub/org.freecadweb.FreeCAD@4a44ce2 and submit a similar PR for Cura if I get a green light.

After a successful installation, I am unable to execute Ultimaker Cura. When I try to run it in the terminal, I receive the following information:

ChromeOsFlex Versión 123.0.6312.132 (Build oficial) (64 bits)

kazukimafufafu@penguin:~$ flatpak install flathub com.ultimaker.cura
Looking for matches…

com.ultimaker.cura permissions:
ipc network wayland x11 devices file access [1] system dbus access [2]

[1] /media, /run/media, home
[2] org.freedesktop.UDisks2


    ID                          Branch         Op         Remote          Download

1. [✓] com.ultimaker.cura stable i flathub 350.8 MB / 400.0 MB

Installation complete.
kazukimafufafu@penguin:~$ flatpak run com.ultimaker.cura
Fontconfig warning: "/etc/fonts/conf.d/05-flatpak-fontpath.conf", line 5: unknown element "reset-dirs"
Fontconfig error: "/etc/fonts/conf.d/05-flatpak-fontpath.conf", line 6: invalid attribute 'salt'
Fontconfig error: "/etc/fonts/conf.d/05-flatpak-fontpath.conf", line 7: invalid attribute 'salt'
Fontconfig warning: "/run/host/font-dirs.xml", line 4: unknown element "remap-dir"
Fontconfig error: "/run/host/font-dirs.xml", line 4: invalid attribute 'as-path'
Fontconfig warning: "/run/host/font-dirs.xml", line 5: unknown element "remap-dir"
Fontconfig error: "/run/host/font-dirs.xml", line 5: invalid attribute 'as-path'
Fontconfig error: Cannot load config file from /run/host/font-dirs.xml
Fontconfig warning: "/etc/fonts/conf.avail/05-reset-dirs-sample.conf", line 6: unknown element "reset-dirs"
qt.qpa.wayland: Ignoring unexpected wl_surface.enter received for output with id: 7 screen name: "Screen5" screen model: "unknown" This is most likely a bug in the compositor.
qt.qml.typeresolution.cycle: Cyclic dependency detected between "file:///app/cura/share/cura/resources/qml/Actions.qml" and "file:///app/cura/share/cura/resources/qml/Actions.qml"
The Wayland connection broke. Did the Wayland compositor die?

Could you please provide assistance in resolving this issue?
Thank you for your help and assistance with this matter!

Qt gets forced to use X11 by this environment variable:

But the X11 socket is not available when using Wayland:

If you want to prefer XWayland over Wayland remove --socket=fallback-x11 and set --env=QT_QPA_PLATFORM=xcb;wayland.

Can't eject after storing slice into sd, it says "there are files opened by xdg-document-portal"

#14 added filesystem permissions for /media to allow access to SD card contents, but systems using udisks2 mount external storage in /run/media by default (see UDISKS_FILESYSTEM_SHARED).

While /run/media is the default, /media seems to be a common alternative configuration, so permissions should probably be set for both locations to ensure SD cards work out of the box for most installations.

The Cura Vesion 5.1.1 does not start on Ubuntu.

Here is the Terminal Output:

flatpak run com.ultimaker.cura
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
Gtk-Message: 12:37:28.477: Failed to load module "canberra-gtk-module"
Gtk-Message: 12:37:28.478: Failed to load module "canberra-gtk-module"
QApplication: invalid style override 'adwaita' passed, ignoring it.
Available styles: Windows, Fusion
Fontconfig warning: "/etc/fonts/conf.avail/05-reset-dirs-sample.conf", line 6: unknown element "reset-dirs"
QQmlApplicationEngine failed to load component
QQmlComponent: Component is not ready
QQmlComponent: Component is not ready
QQmlComponent: Component is not ready

I installed Cura yesterday on an Elementary OS 7.1 box and when attempting to start, I get the big blue logo, then it dissapears and it spits back in the terminal:

PyInstaller/loader/pyimod02_importers.py:352: 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
QApplication: invalid style override ‘adwaita’ passed, ignoring it.
Available styles: Windows, Fusion
Fontconfig warning: “/etc/fonts/conf.d/05-flatpak-fontpath.conf”, line 5: unknown element “reset-dirs”
Fontconfig error: “/etc/fonts/conf.d/05-flatpak-fontpath.conf”, line 6: invalid attribute ‘salt’
Fontconfig error: “/etc/fonts/conf.d/05-flatpak-fontpath.conf”, line 7: invalid attribute ‘salt’
Fontconfig warning: “/run/host/font-dirs.xml”, line 4: unknown element “remap-dir”
Fontconfig error: “/run/host/font-dirs.xml”, line 4: invalid attribute ‘as-path’
Fontconfig warning: “/run/host/font-dirs.xml”, line 5: unknown element “remap-dir”
Fontconfig error: “/run/host/font-dirs.xml”, line 5: invalid attribute ‘as-path’
Fontconfig error: Cannot load config file from /run/host/font-dirs.xml
Fontconfig warning: “/etc/fonts/conf.avail/05-reset-dirs-sample.conf”, line 6: unknown element “reset-dirs”
QQmlApplicationEngine failed to load component
QQmlComponent: Component is not ready

I’m not the most Linux centric person in the whole world.

Any thoughts on what this is trying to tell me?

Thank you

chris

From one day to the other stopped working... not sure if an update of cura or system was installed in the meantime
I did some python stuff in between but used virtualenvironments.. so don't think thats the reason.. and well.. it's a flatpak right?

PyInstaller/loader/pyimod02_importers.py:352: 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
Fontconfig warning: "/etc/fonts/conf.d/05-flatpak-fontpath.conf", line 5: unknown element "reset-dirs"
Fontconfig error: "/etc/fonts/conf.d/05-flatpak-fontpath.conf", line 6: invalid attribute 'salt'
Fontconfig error: "/etc/fonts/conf.d/05-flatpak-fontpath.conf", line 7: invalid attribute 'salt'
Fontconfig warning: "/run/host/font-dirs.xml", line 4: unknown element "remap-dir"
Fontconfig error: "/run/host/font-dirs.xml", line 4: invalid attribute 'as-path'
Fontconfig error: Cannot load config file from /run/host/font-dirs.xml
Fontconfig warning: "/etc/fonts/conf.avail/05-reset-dirs-sample.conf", line 6: unknown element "reset-dirs"
Cyclic dependency detected between "file:///app/cura/share/cura/resources/qml/Actions.qml" and "file:///app/cura/share/cura/resources/qml/Actions.qml"
QQmlApplicationEngine failed to load component

When an argument is used "--socket=wayland" the application after launch shows only a transparent window. When using only --socket=x11 in a wayland session, everything works fine.
OS: KDE Neon (based on ubuntu 22.04)
GPU: Nvidia 3060
KDE: 5.27
Qt: 5.15.8