Arch Linux User Repository

I am pretty sure the Cura application window used to have a Cura icon. Now it just has the generic application icon (the blue one with white gears).

@LukasDoe This is an issue not with the AUR package but with Cura's AppImage; see problems opening file-open dialogue and problems with 5.4.0 crashing. A workaround is to use a file management program like PCManFM to drag and drop files into Cura; that feature still works. I expect it would work with any modern window manager, since I'm running dwm and it works for me, and that's a very bare bones window manager.

Hangs around 30 seconds at this:

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

And then prints this mess:

Cyclic dependency detected between "file:///tmp/.mount_curafyqSbm/share/cura/resources/qml/Actions.qml" and "file:///tmp/.mount_curafyqSbm/share/cura/resources/qml/Actions.qml" qt.qml.context: file:///tmp/.mount_curafyqSbm/share/cura/resources/qml/Settings/SettingView.qml:427:16 Parameter "index" is not declared. Injection of parameters into signal handlers is deprecated. Use JavaScript functions with formal parameters instead. file:///tmp/.mount_curafyqSbm/share/cura/resources/qml/PrintSetupSelector/Recommended/RecommendedPrintSetup.qml:96:17: QML QQuickItem: Binding loop detected for property "height" file:///tmp/.mount_curafyqSbm/share/cura/resources/qml/PrintSetupSelector/Recommended/RecommendedPrintSetup.qml:96:17: QML QQuickItem: Binding loop detected for property "height" file:///tmp/.mount_curafyqSbm/share/cura/resources/qml/PrintSetupSelector/Custom/CustomPrintSetup.qml:163:13: QML ProfileWarningReset: Binding loop detected for property "width" file:///tmp/.mount_curafyqSbm/share/cura/resources/qml/PrintSetupSelector/Custom/CustomPrintSetup.qml:163:13: QML ProfileWarningReset: Binding loop detected for property "width" file:///tmp/.mount_curafyqSbm/share/cura/resources/qml/PrintSetupSelector/Custom/CustomPrintSetup.qml:163:13: QML ProfileWarningReset: Binding loop detected for property "width"

… and when tryong to open a file with file -> open it crashes with this:

/tmp/.mount_curafyqSbm/AppRun: line 25: 11647 Segmentation fault (core dumped) $scriptdir/UltiMaker-Cura "$@"

Can't open files in the app and it crash after clicking "open files"

$ 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
Cyclic dependency detected between "file:///opt/ultimaker-cura/share/cura/resources/qml/Actions.qml" and "file:///opt/ultimaker-cura/share/cura/resources/qml/Actions.qml"
file:///opt/ultimaker-cura/share/cura/resources/qml/PrintSetupSelector/Recommended/RecommendedPrintSetup.qml:96:17: QML QQuickItem: Binding loop detected for property "height"
file:///opt/ultimaker-cura/share/cura/resources/qml/PrintSetupSelector/Recommended/RecommendedPrintSetup.qml:96:17: QML QQuickItem: Binding loop detected for property "height"
/usr/bin/cura: line 25: 479286 Segmentation fault      (core dumped) $scriptdir/UltiMaker-Cura "$@"

@k4pu77 Those packages were based on differences between installed packages on my system and someone else's. Based on later testing, they don't appear to be dependencies for this package.

I get the same messages when I run cura. Maybe try deleting existing cura config and cache (rm ~/.config/cura* ~/.cache/cura)?

Does running cura -platformtheme gtk3 make any difference?

@xiota I tried installing the dependencies you mentioned as well, but cura doesn't start either:

ä sudo pacman -S libdbusmenu-qt6 pyside6 qt6-tools qt6-wayland qt6-websockets

$ 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
Cyclic dependency detected between "file:///opt/ultimaker-cura/share/cura/resources/qml/Actions.qml" and "file:///opt/ultimaker-cura/share/cura/resources/qml/Actions.qml"
QQmlEngine::setContextForObject(): Object already has a QQmlContext
file:///opt/ultimaker-cura/share/cura/resources/qml/PrintSetupSelector/Recommended/RecommendedPrintSetup.qml:96:17: QML QQuickItem: Binding loop detected for property "height"
file:///opt/ultimaker-cura/share/cura/resources/qml/PrintSetupSelector/Recommended/RecommendedPrintSetup.qml:96:17: QML QQuickItem: Binding loop detected for property "height"

I am stuck with the loading screen of cura.

@xiota I tried installing those five packages, but unfortunately it's still broken.

I also previously tried running cura from the terminal, but there was nothing obvious. FWIW this is the output.

$ 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
qt.gui.icc: fromIccProfile: failed size sanity 2
Cyclic dependency detected between "file:///opt/ultimaker-cura/share/cura/resources/qml/Actions.qml" and "file:///opt/ultimaker-cura/share/cura/resources/qml/Actions.qml"
QQmlEngine::setContextForObject(): Object already has a QQmlContext
file:///opt/ultimaker-cura/share/cura/resources/qml/PrintSetupSelector/Recommended/RecommendedPrintSetup.qml:96:17: QML QQuickItem: Binding loop detected for property "height"
file:///opt/ultimaker-cura/share/cura/resources/qml/PrintSetupSelector/Recommended/RecommendedPrintSetup.qml:96:17: QML QQuickItem: Binding loop detected for property "height"

@purigro I'm not entirely convinced it's an issue with upstream, because the "fix" proposed there worked for others, but not for me. It would be good for others experiencing this bug to try the nightly as well.

I'm not really keen on using flatpaks tbh. I'd much rather use the native package manager if possible.

Ahh, the two of you did some good work chasing this down yesterday! The fact that it isn't working on the upstream AppImage and the upstream issue in the tracker would suggest that there isn't much for this package to do, but then it's odd that I'm able to use the qt file open dialogue in two reasonably different KDE installs.

@Rhinoceros: Just a thought, but assuming you're not against the whole concept of flatpaks, I noticed cura seems to have an up to date build on flathub. In addition to providing a containerized installation like the AppImage, flatpak also provides its own environment and toolkit dependencies which might sidestep the problem you're having.

Installing those qt6 dependencies suggested by xiota seems like a good next step though. If you install them one at a time and one of them does the trick, let me know and I can look at incorporating it into the package as an optional dependency for KDE users.

@Rhinoceros I have some Qt6 packages installed that you don't. It looks like cura does use Qt6, so maybe installing them would help.

libdbusmenu-qt6
pyside6
qt6-tools
qt6-wayland
qt6-websockets

Also, if you run cura from a terminal, some diagnostic messages might be helpful.

@xiota Thanks again for persisting! I cleared the history, although the "Defaults" button was greyed out. This didn't help the cura issue.

I ran the AppImage directly as suggested. This was also broken for me.

Thanks for the link to the upstream issue. FWIW there was a nightly that may have fixed this issue. I downloaded the AppImage and ran this directly, but unfortunately the open dialogue still doesn't appear. From the comments, it appear it fixed the problem for others (although a few Arch people complain about segfaults, which I don't see). i.e. I'm not sure if it necessarily is an issue upstream.

Here is a list of my installed packages.