Arch Linux User Repository

@xiota Thanks for all that information. I'm not sure what else could have changed. Perhaps the newer version doesn't work in combination with my dependencies, etc. Either way, the patches fix the problem on my system. Not really sure where else to go from here in terms of troubleshooting.

cura-appimage-bin was out of date, and the maintainer wasn't responding to comments/issues. You can still clone the git repository and build it if you want. It was based on an older version of the appimage that this package is based on.

I see nothing that would account for any difference in behavior.

• Dependencies are the same.
• This package extracts the appimage instead of running it directly, but the same AppRun script is eventually used.
• The other package attempts to detect Wayland and set QT_QPA_PLATFORM=xcb, but fails to do so because of a typo.

Dialogs work as expected on my computer with Plasma. They do not work when Recent File history is disabled.

Thanks for the quick response @prurigro.

Yes, I do have xdg-desktop-portal-kde installed. I have plasma-meta installed actually, so it's a dependency on that. I'm happy to troubleshoot more if you have any hints on where to look.

I'm not entirely sure what the difference is between the old cura-appimage-bin and this one. This package still does use the appimage, right?

@Rhinoceros: Hey, I just re-tested cura's open file dialogue using this package in KDE and it worked correctly. It's been working correctly for me here since switching to the builtin scripts so I'm wondering now if it isn't a dependency issue. Do you have xdg-desktop-portal-kde installed? The problem with specifing gtk in the package is that it breaks things for people who only have the kde one installed (and in theory, KDE users with both would still prefer the KDE-styled one, I know I do).

This package originally did use the appimage and the biggest issue vs extracted was the startup time. I wouldn't be opposed to maintaining a replacement for cura-appimage-bin in tandem with this one if we can't get the issue sorted for some percent of KDE users though (I could just update both at the same time).

I read through the comments, but I'm not entirely sure what users are meant to do to fix this package. In order to get file dialogues working in KDE, I followed @wallace11's suggestion, and patched two files. This seems the only solution proposed to fix *.desktop files.

Is there a way to incorporate any of these fixes into the PKGBUILD itself? It's not great for all KDE users to have to manually patch files. FWIW the recently-deleted cura-appimage-bin package worked perfectly fine on my system out-of-the-box. (I'm not sure why it was deleted.)

Thanks @alphabyte for flagging this out of date- my update checker's regex skipped the latest update because they changed Ultimaker to UltiMaker :)

What would be a way to debug this package or collect logs? running it from the shell doesn't produce any meaningful error message or problems. it gives me black screen after a fresh install on sway/wayland.

Fixed by adding to /usr/bin/Ultimaker-Cura:

# Force to run in XWayland
export QT_QPA_PLATFORM=xcb

Using i3, I can't seem to open any models. Attempting to open files doesn't seem to do anything.

On startup, I get the following logs in the console:

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:///opt/cura5/share/cura/resources/qml/Actions.qml" and "file:///opt/cura5/share/cura/resources/qml/Actions.qml"
QQmlEngine::setContextForObject(): Object already has a QQmlContext

But that's about it. Attempting to Open File(s)... doesn't log anything. It just does nothing.

QT_QPA_PLATFORMTHEME controls the dialogs that Qt uses. xdgdesktopportal tries to use native dialogs, while gtk3 forces the use of GTK3 dialogs. If previously used paths are not recalled, there may be a problem with desktop configuration, like file history is disabled.

Rather than editing the script, the platform theme can be changed with a command-line parameter. This overrides the environment variable.

cura -platformtheme gtk3

It's probably best to leave the script in the package alone. Changing it could cause problems for other users, and most desktop environments provide an easy way to edit the app menu.