Arch Linux User Repository

I ran into the same error that @fow0ryl stated. I believe Cura cannot open my home directory, so Cura crashes.

My workaround is to move the model to /tmp and open it directly like this:

mv MODEL /tmp
UltiMaker-Cura /tmp/MODEL

I use btrfs, FWIW.

@thorou: sorry about not catching this sooner- I've updated the launcher script and credited you.

@fow0ryl: I can't seem to recreate the error you're hitting. Is there anything unique about your environment?

Did not work for me ...

Some errors when starting cura

$ 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"
qt.qml.context: file:///opt/ultimaker-cura/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.

trying "File Open" crashes ...

/usr/bin/cura: Zeile 3: 37522 Speicherzugriffsfehler  (Speicherabzug geschrieben) /opt/ultimaker-cura/AppRun "$@"

+1 so it ranks higher up

There is an upstream issue with the AppImage, where the main window will not open when QT_STYLE_OVERRIDE is set (https://github.com/Ultimaker/Cura/issues/17163, https://github.com/Ultimaker/Cura/issues/12940)

The simple workaround is to add unset QT_STYLE_OVERRIDE to the bash script here.

Should this be added to the package, or is this something users should apply themselves? Setting the variable to one of the supported styles also breaks, so I don't see any scenario in which you wouldn't want the fix.

Hey everyone, sorry about the delay getting back to you all. I was sick with the flu for a couple of weeks and have been catching up on stuff ever since.

It does appear that the latest update really borked the .desktop file (it seems like it was truncated as it just sort of ends after Comments=). I've pushed an update to the package that corrects the package, using the previous version as a guide for the mimetypes. I also used an absolute path for the icon because why not if it makes things more generally compatible (interesting to know about the file extension making it expect absolute!).

The category switched from graphics to utilities, but that might not be a mistake? Feel free to comment if you think it was though.

Hello, the latest update seems to have borked the file association for Cura and now it's no longer listed in the "Open With Other App" program list window in Gnome.

@prurigro: Yes the file is included in /usr/share/pixmaps. I use rofi and researched a little bit and found this issue: https://github.com/davatorium/rofi/issues/942

There is mentioned the following documentation from xdg-desktop-icon --manual:

Icon=Icon File
    The icon to use for the application. This can either be an absolute path to
    an image file or an icon-name. If an icon-name is provided an image lookup
    by name is done in the user's current icon theme. The xdg-icon-resource
    command can be used to install image files into icon themes. The advantage
    of using an icon-name instead of an absolute path is that with an icon-name
    the application icon can be provided in several different sizes as well as
    in several differently themed styles.

so adding the extension .png set it as absolute path and then cura-icon.png is wrong. So it should be an absolute path /usr/share/pixmaps/cura-icon.png to force usage of the delivered png file.

@prurigro Seems to be common to not use a file extension for icon images in desktop files. Maybe it's to work better with themes. Could be fixed with a sed command in prepare().

The apprun patch could also be replaced with a sed command.

Might be good to use exec to avoid a fork in the UltiMaker-Cura script.

@bitdrifter: The package should include cura-icon.png for you, does it not? I'm installing the ones included in the package for both the icon and the .desktop file.