Arch Linux User Repository

Just in case anyone has the problem with cura not opening any file dialogs at all, changing QT_QPA_PLATFORMTHEME to gtk3 in /opt/ultimaker-cura/AppRun solved it for me.

@xiota
That did the trick! Thank you so much for the hint!
With that being said, I now had to change the desktop entry for how I launch Cura (using rofi).
Here's what I ended up doing and worked for me:

• /opt/ultimaker-cura/AppRun: QT_QPA_PLATFORMTHEME change from xdgdesktopportal to gtk3

• /usr/share/applications/cura.desktop: change Exec to Exec=/opt/ultimaker-cura/AppRun %F

I hope this information will help with fixing the issue without resorting to clunky solutions :)

@johnride: Yeah, as @xiota mentioned, base-devel is typically assumed to be installed when you're building packages. I'd recommend running pacman -S --needed base-devel right now to pull everything from there in.

@wallace11: Hey, I don't think the save or open dialogues have ever remembered the last path for me, are you saying it's done that correctly for you at one point or another? I just tested the installed package as well as the pure AppImage and got the same results in both cases (no memory). EDIT: Not having ever worked for me includes the old official package.

@wallace11 Does changing QT_QPA_PLATFORMTHEME=xdgdesktopportal to QT_QPA_PLATFORMTHEME=gtk3 in the AppRun make a difference? If not, can you comment out each export line one by one until you find which one may be causing problems?

AppRun patch has given me quite some headache because when saving to disk it would not remember the last path and would not insert the file name - it's completely empty. I downgraded to pkgver 2 for now until either me or someone else finds a solution.

For reference, I'm on a DE (bspwm) and got both xdg-desktop-portal and xdg-desktop-portal-gtk installed. The former got a couple of updates recently and I tried all versions with no success.

patch is part of base-devel. I've never seen a package with anything from base-devel included as a build dependency.

patch should be added as a build dependency. Just had a build fail because it was not installed.

Thanks for the package otherwise!

Hi,

to get cura5 to run correctly in KDE + Wayland the last line of the script /user/bin/cura5 should be as follows:

QT_QPA_PLATFORM=xcb LD_PRELOAD=/usr/lib/libstdc++.so.6 QT_QPA_PLATFORMTHEME=xdgdesktopportal QT_QPA_PLATAFORM=xdgdesktopportal ./Ultimaker-Cura $@

After the above is applied Cura5 works as espected. If run from terminal, the below warnings are outputted:

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

Greetings, a clean build will finish creating and installing the package however the following errors are thrown when attempting to launch the app:

(Ultimaker-Cura:1156227): GLib-GIO-ERROR **: 10:11:22.258: Settings schema 'org.gnome.settings-daemon.plugins.xsettings' does not contain a key named 'antialiasing' /usr/bin/cura5: line 5: 1156227 Trace/breakpoint trap (core dumped) LD_PRELOAD=/usr/lib/libstdc++.so.6 QT_QPA_PLATFORMTHEME=xdgdesktopportal QT_QPA_PLATAFORM=xdgdesktopportal ./Ultimaker-Cura $@

The main advantage of hardlinks over symlinks is they can never be broken. They are also real files, so will work where symlinks might not. I tried writing a script to symlink the duplicate files, but cura wouldn't run. Didn't put much effort into trying to figure out why because hardlinks work and the space saving would be the same.

Reflinks are currently supported by Btrfs, XFS, and ZFS. Their uses are similar except that reflink contents can diverge. I use hardlinks to keep copies of notes in multiple locations. I use reflinks to clone WINE prefixes, where some files are expected to diverge. I've used both to clone directories (cp -l) prior to doing temporary work that will be deleted (so I don't have to search for build artifacts) and to make incremental backups (rsync).

Hardlinks and reflinks are both created nearly instantaneously, so for very large packages, creating ref/hardlinks instead of copying files could be worth considering.