Arch Linux

I could reproduce the issue, but after much fiddling around this seemed to be resolved. My guess that it's related to cura's settings. But I will need to investigate further.

I am also having this issue. Jelly, would you mind telling what kind of fiddling you did to make it work again?

Not really, I have the feeling it's due to the cura settings.

You can startup cura if you delete the config file in ~/.config/cura/4.1/cura.cfg. But as soon as you enter the "Stützstruktur" menu it crashes.

I also had the issue, so I also tried fiddling with the config file as Jelle suggested. In ~/.config/cura/4.1/cura.cfg removing the categories_expanded entry fixed the problem for me. After some more fiddling it turned out that just removing the following entries within categories_expanded was also enough:

support
speed_layer_0
platform_adhesion

When it runs again, you can disable some settings visibility as well to prevent crashes. I had to disable "Support Extruder" and "Build Plate Adhesion Extruder"

You can startup cura if you delete the config file in ~/.config/cura/4.1/cura.cfg. But as soon as you enter the "Stützstruktur" menu it crashes.

I can confirm that this is still happening and it's probably related to plugins (segfault happens while trying to load some plugins).

This is my logfile: https://pastebin.com/LN6xGhbY

And I've reported the issue upstream: https://github.com/Ultimaker/Cura/issues/6008

Removing the categories_expanded from the config file fixed it for me, but I also had to uncheck "support extruder" and everything under it in the settings visibility page, otherwise it still crashes when opening the "Support" submenu-page-expanding-thing

It didn't work for me. It's something related to threading in python 3.7, triggered by the `_updateThread` method of `/usr/lib/cura/plugins/USBPrinting/USBPrinterOutputDeviceManager.py` and `/usr/lib/cura/plugins/RemovableDriveOutputDevice/RemovableDrivePlugin.py`

One of Ultimaker's team member on GitHub commented on the GitHub issue I linked:

> The segfault for RockyTV is happening when the main window is loaded, not while the plug-ins are being loaded. Though granted, it's also complaining about missing dependencies during plug-in loading (libCharon and Zeroconf). Since it's happening while the main window is loading, it's most likely an issue with your version of Qt, i.e. not version 5.10 which we maintain.

I tried installing both python-libcharon and python-zeroconf and it still didn't work. Perhaps this is an issue with the current Qt version?

Could anyone test Smplayer (also QT) with hardware decoding enabled? It's crashing on all my systems, except my laptop which is running Nvidia's propriety driver.
Either QT, or the open source video drivers are borked.

For me the solution was to entirely remove Cura and all related components (pacman -Rcs), purge cached packages (pacman -Sc) and update the system. Then install Cura again, any mismatch in libraries seems to crash Cura.
If Cura still crashes, you'll have to delete your Cura profile/cache too (great isn't it?). Profile data is stored in homedir/.cache, homedir/.config, homedir/.local/share.

This is _no_ solution as cura still crashes if you need the "Support" menu.

Upstream has proposed some patches to uranium that fix cura for me. The following amended PKGBUILD works for me.

# Maintainer: Jelle van der Waa <jelle@vdwaa.nl>
# Contributor: Grey Christoforo <first name [at] last name [dot] net>

pkgname=uranium
pkgver=4.1.0
pkgrel=2
pkgdesc="A Python framework for building Desktop applications."
url="https://github.com/Ultimaker/Uranium"
arch=('any')
license=('LGPL')
depends=('python' 'qt5-quickcontrols' 'qt5-quickcontrols2' 'pyqt5-common' 'python-pyqt5' 'python-numpy' 'arcus' 'python-shapely')
makedepends=('cmake')
source=("$pkgname-$pkgver.tar.gz::https://github.com/Ultimaker/${pkgname}/archive/${pkgver}.tar.gz"
'https://patch-diff.githubusercontent.com/raw/Ultimaker/Uranium/pull/500.patch'
'https://patch-diff.githubusercontent.com/raw/Ultimaker/Uranium/pull/499.patch')

sha256sums=('72245dba1fb74236144ffbe59497ef495b87bb3bb2b1d7ffcadebe138824eed4'
'd2d8c9acccfc59f906bfefe07d1683d363c65ac162a60c494acdebea121d9527'
'77cebd3742276ef585c8f93e7b942478e22abe1622ad6c1f0d1bd17d439fa3a5')

prepare() {
cd Uranium-${pkgver}
sed -i 's,/dist-packages,.${PYTHON_VERSION_MINOR}/site-packages,g' CMakeLists.txt
patch -p1 <"$srcdir/499.patch"
patch -p1 <"$srcdir/500.patch"
}

build() {
cd Uranium-${pkgver}
mkdir -p build && cd build

cmake .. \
-DCMAKE_INSTALL_PREFIX=/usr \
-DCMAKE_BUILD_TYPE=Release
make
}

package() {
cd Uranium-${pkgver}/build
make DESTDIR="${pkgdir}" install
}

# vim:set ts=2 sw=2 et:

Confirmed Moabit's comment fixed the same issue for me.

Applied and a new uranium is now in the repos

I can confirm that the problem is gone when using new uranium from the repo.

Thanks @jelly