You are not logged in.
I have multiple machines running Arch. On each machine the moment I try to slice a model with any complexity, the slicer crashes. While I was an able to find error logs, both strace and the console output the following:
[2025-02-20 08:12:07.639283] [0x00007c66a3ada080] [error] UserAccount: Failed to read token - no datafile found.
08:12:09 AM: Debug: window wxTreeCtrl@0x5a211fb7ccb0 ("treeCtrl") lost focus even though it didn't have it
08:12:09 AM: Debug: window wxTreeCtrl@0x5a211fb7ccb0 ("treeCtrl") lost focus even though it didn't have it
08:12:09 AM: Debug: window wxTreeCtrl@0x5a211fb7ccb0 ("treeCtrl") lost focus even though it didn't have it
08:12:09 AM: Debug: window wxTreeCtrl@0x5a211fb7ccb0 ("treeCtrl") lost focus even though it didn't have it
08:12:09 AM: Debug: window wxTreeCtrl@0x5a211fb7ccb0 ("treeCtrl") lost focus even though it didn't have it
08:12:09 AM: Debug: window wxTreeCtrl@0x5a211fb7ccb0 ("treeCtrl") lost focus even though it didn't have it
08:12:09 AM: Debug: window wxTreeCtrl@0x5a211fb7ccb0 ("treeCtrl") lost focus even though it didn't have it
08:12:09 AM: Debug: window wxTreeCtrl@0x5a211fb7ccb0 ("treeCtrl") lost focus even though it didn't have it
08:12:09 AM: Debug: window wxTreeCtrl@0x5a211fb7ccb0 ("treeCtrl") lost focus even though it didn't have it
08:12:09 AM: Debug: window wxTreeCtrl@0x5a211fb7ccb0 ("treeCtrl") lost focus even though it didn't have it
08:12:09 AM: Debug: window wxTreeCtrl@0x5a211fb7ccb0 ("treeCtrl") lost focus even though it didn't have it
08:12:09 AM: Debug: window wxTreeCtrl@0x5a211fb7ccb0 ("treeCtrl") lost focus even though it didn't have it
08:12:09 AM: Debug: window wxTreeCtrl@0x5a211fb7ccb0 ("treeCtrl") lost focus even though it didn't have it
08:12:09 AM: Debug: window wxTreeCtrl@0x5a211fb7ccb0 ("treeCtrl") lost focus even though it didn't have it
08:12:09 AM: Debug: window wxTreeCtrl@0x5a211fb7ccb0 ("treeCtrl") lost focus even though it didn't have it
/usr/include/c++/14.2.1/bits/stl_vector.h:1213: std::vector<_Tp, _Alloc>::reference std::vector<_Tp, _Alloc>::front() [with _Tp = unsigned char; _Alloc = std::allocator<unsigned char>; reference = unsigned char&]: Assertion '!this->empty()' failed.
fish: Job 1, 'prusa-slicer' terminated by signal SIGABRT (Abort)If I submit the same job to prusa-slicer running in a windows vm, everything works as expected. The error /usr/include/c++/14.2.1/bits/stl_vector.h occurs as soon as I click slice.
EDIT:
Looks like its fixed in 2.9.1 alpha build https://github.com/prusa3d/PrusaSlicer/issues/13859
Last edited by piratebill (2025-02-20 16:37:49)
Offline
I am not experiencing any issues with 2.9.0-2. Hyperland / Wayland / Intel Isis graphics. Prusa-slicer is using Xwayland.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
I've tried it on wayland and x11 (three different boxes. Each fully up to date). Some models, like this one https://www.printables.com/model/113958 … -airbender crash it everytime. Currently using a flatpak install of it now, no issues when I do that. Glad to know it isn't hitting others at least
Offline
I notice that with the 2.9.1 release Prusa is using Flatpak, below is from their site.
We have decided to move to Flatpak and use Flathub as the official means of distributing our application on Linux. The Flathub package here is now officially endorsed. You can follow the steps provided on the Flathub page.
Here is a quick guide on how to use flatpak from the terminal. This is required to try out the alpha, beta and rc releases.
First, make sure you have flatpak installed and Flathub correctly set up. You can follow the steps at https://flatpak.org/setup/.
If you want to try out the alpha (such as this one), beta and rc versions you must add the flathub-beta repository (you only need to do this once):I assume you used flatpak to try the alpha release. That tells me there may be something in your setup that is not up to date and the new flatpak contains all the dependencies it requires. I assume you are using the Prusa Slicer from extra and your system is fully up to date?
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
Systems are fully up to date (I update them daily). Flatpak installed v2.9.0. The pacman installed version is indeed from extra (prusa-slicer)
Offline