Arch Linux User Repository

@Rhinoceros Go to System Settings / Workspace Behavior / Recent Files. Click the "Clear History" and "Defaults" buttons to reset it. Then "Apply".

What happens when you run the AppImage directly. The AppImage file may be found in the src directory. If running the AppImage directly presents with the same problem, an issue has already been opened upstream: Ultimaker/Cura/14145

The installed packages shouldn't matter if the original AppImage was created correctly, but if you don't mind, would you create a pastebin with a list of packages. pacman -Q > packages.txt

@xiota I'm not sure what you mean by "Recent File history". Is this the same as the KDE Plasma history? I can see my recent files in the (older) "Applications menu" plasmoid, if that's what you mean?

@prurigro here my env: https://pastebin.com/gukX8tC9

pacman -S --needed plasma-desktop shows this package is already installed... but I'm not sure if you meant to check the dependencies. pacman -Dk plasma-desktop shows everything is okay though.

In the build directory (pkg/cura-bin/opt/ultimaker-cura), I tried launching both ./UltiMaker-Cura and ./AppRun, and in both cases the dialogue windows still failed.

The KDE dialogs don't work as expected when Recent File history is disabled. In that case, switching to GTK dialogs "works" by using the GTK history settings.

So far, no one who has had problems with KDE dialogs has responded to report the state of their history settings. If Recent File history is disabled, there is nothing to fix.

@Rhinoceros: So my daughter got her laptop a couple of months ago, and I installed the minimal plasma-desktop group (just core KDE components), mpv, firefox, steam and one or two other things for her. I installed cura-bin yesterday and tested the file dialogue, and it works perfectly there.

So that said, there are two potential angles I'm thinking this could be- one is that you installed a while ago and that some core KDE component didn't get picked up as KDE was upgraded. To check that you could try "pacman -S --needed plasma-desktop" and see if anything interesting looking pops up as missing; if this ends up being the issue I'll add whatever did the trick as an optional dependency. The other is my theory that there could be something fishy happening in your env.

I'd still be interested to hear if the UltiMaker-Cura-5.3.1-linux-modern.AppImage in the package's build directory works correctly.

@xiota: thanks for the thought! I might actually borrow that idea for a non-aur package I wanted use to keep a nightly build for something up to date :) As for cura, it shouldn't be more than a day or so before an upsteam update makes it to this package (unless they change the naming format again and breaks my regex again lol).

@Rhinoceros: It just occurred to me, can you test the appimage in the build directory to make sure you do get a file open dialogue there?

@prurigro There isn't really a need for a -latest-bin as long as you're able to keep this one updated. There are already too many cura-*-bin packages that are all basically doing the same thing. I noticed that many of them are out of date, and thought an autoupdate feature might make maintenance easier.

@Rhinoceros: Thanks for the info- I'm gonna try to recreate your issue tonight my installing cura on my daughter's laptop (which has KDE but not much else). Interesting that you have what I assumed would be the main dependency. Do you think you could post a pastebin of your env too? I can try sourcing that env and see if things behave differently.

@xiota: I actually run a script to check for updated versions of cura (and the rest of the packages I maintain) most nights (https://git.darkcloud.ca/kmacmart/aur-package-updates). I also test cura to make sure it runs before pushing the update (though apparently my KDE environment has something that not everyone does). I'm hesitant to include an auto update system (even an optional one) since it bypasses the checksum component and testing. What you've shared is cool, but I feel like it might be better done in a cura-latest-bin package without the toggle?

@prurigro What do you think about adding autoupdate capability to the PKGBUILD? When enabled, the PKGBUILD would check for new releases without having to wait for a manual update.

_autoupdate="false"

if [ x"$_autoupdate" == "xtrue" ] ; then
  _github=$(curl -s https://api.github.com/repos/Ultimaker/Cura/releases)
  _github=$(echo $_github | grep -E '"https://.*-([0-9]+\.[0-9]+(\.[0-9]+)?)-linux-modern\.AppImage"' | head -1)

  _download=$(echo $_github | sed -E 's@^.*"(https://.*\.AppImage)"$@\1@')
  _appimage_sum='SKIP'

  _pkgver=$(echo $_download | sed -E 's@^https://.*/download/([0-9]+\.[0-9]+(\.[0-9]+)?)/.*\.AppImage$@\1@')
else
  _pkgver=5.3.1

  _download="https://github.com/Ultimaker/Cura/releases/download/$_pkgver/UltiMaker-Cura-$_pkgver-linux-modern.AppImage"
  _appimage_sum=81bb4ecdd050b0d2eaaa7ed45251a2613ce83084e7e57ba4a0d660c71d59bac22e2cad47531fedefe7d00dbdc0781834fa8604ef95c7342d68bdcbd465afa38b
fi

# ...

source=(
  "$_download"
  'AppRun-UltiMaker-Cura.patch'
  'AppRun-CuraEngine.patch'
)
sha512sums=(
  "$_appimage_sum"
  'bf5fa289d8f4193e186a0d8d7e5dc5e902789674bf6c2a068655d639f1be1e7c9d9757c4709801f10c86501c6722a94a97051f662f6d1d85294d1cba16145f63'
  '5a005722d6b97abe9b8fce1aa74877b5be75ec58f03afb3049d4a4df431caf4e8aba825716696f010557ac1682bfecc9e4133297c3280528af4be2e30b560860'
)

pkgver() {
  echo $_pkgver
}

# ...

If you want, you can download and test previous releases. However, I doubt the issue is related to Cura version. cura-appimage-bin was stuck at version 5.2.1, and that is the version this package was at when reports of issues first appeared in comments.