smartavionics
commented
5 years ago Hi. I assume you are running from source. Please update your Uranium to the master branch as we have just fixed a crash there. Thanks.
Closed jeroenrnl closed 6 days ago
smartavionics
commented
5 years ago Hi. I assume you are running from source. Please update your Uranium to the master branch as we have just fixed a crash there. Thanks.
Ghostkeeper
commented
5 years ago Are you using the AppImage distribution of Cura? It doesn't look like it, because it uses Python 3.7 libraries.
If you're using the PPA or Arch packages, I think you're using the wrong version of Qt. If you're developing, it's wise to use the same version as what will be in the final build: 5.10. This way you won't accidentally use a feature that wouldn't run with the mainline builds. It also prevents crashes like this that were introduced in more recent versions of Qt, though we do have a workaround for one of those in 5.13 now in Uranium.
jeroenrnl
commented
5 years ago Hi, I'm running the Arch package version and the Qt version is just the default Arch package too, I'm not developing.
smartavionics
commented
5 years ago There is a known regression with Qt 5.13 which is what is now being used on Arch. The Uranium fix works around that issue.
jeroenrnl
commented
5 years ago I've done
pip install uranium
as root but this did not fix it, I'm looking into this deeper now
smartavionics
commented
5 years ago It provides the application framework that cura is based on.
jeroenrnl
commented
5 years ago ok, this is what I did:
git clone https://github.com/Ultimaker/Uranium
cd Uranium
mkdir build
cd build
cmake ..
make
sudo make install... but this doesn't fix it.
I checked, Uranium was installed in the same directories as where make install put them
smartavionics
commented
5 years ago Then it must be something else, perhaps there's something in the recently closed issue that can help you. Take a look at https://github.com/Ultimaker/Cura/issues/6008.
jeroenrnl
commented
5 years ago Ok, turned out I hadn't checked all files. The Python site-packages files were installed in /usr/local/lib instead of /usr/lib where my system keeps them. I moved them there and now it no longer crashes, but I did lose the preview of the print. I tried changing "Force layer view compatibilty modus", but that didn't help.
GregValiant
commented
6 days ago I'm cleaning house. Is this still a problem with current Cura versions (5.8.0 and up)? Can I close this?
jeroenrnl
commented
6 days ago I didn't even know this bug was still open. I'm no longer using Cura, but have used it successfully many times after the last comment. I think I switched to a different Arch package to fix it.
Application version 4.1.0
Platform Linux 5.2.1
Printer JGAurora A5
Reproduction steps Startup cura
Actual results Cura starts, the splash screen shows, going through all the normal steps, then the application screen shows and after ~2 seconds, it closes
Expected results It doesn't close
Additional information Running cura from a terminal: