PrusaSlicer crashes when initializing Physical Printer
In Debian Trixie with the Debian Build of PrusaSlicer 2.9.2, and a Sovol SV06Ace/Klipper, PrusaSlicer crashes shortly after the initialization progress bar starts.
I've assigned a static IP to the printer which I can ping. I can also open klipper in Firefox-esr at static-ip:80 and in webkitbased vimb. I've tried both Octoprint and Klipper via moonraker in PrusaSlicer Physical printer and both crash. The printer verifies in the PrusaSlicer interface (?successful ping).
Is this a known issue and are there any configuration options I can set as a workaround?
Thanks
RE: PrusaSlicer crashes when initializing Physical Printer
Did you try to start PrusaSlicer via a terminal to see the error messages? Perhaps you can then google for those?
RE: PrusaSlicer crashes when initializing Physical Printer
You should check the PS github for issues. For example https://github.com/prusa3d/PrusaSlicer/issues/13835 may have some things you could try. There are several issues if you care to use search (remember to look at both Open and closed ones).
RE:
[2025-12-25 10:00:53.027513] [0x00007efcc01e04c0] [error] UserAccount: Failed to read token - no datafile found.
(prusa-slicer:28566): Gtk-CRITICAL **: 10:00:53.216: gtk_distribute_natural_allocation: assertion 'extra_space >= 0' failed
10:00:53 AM: Debug: window wxTreeCtrl@0x560b59434c10 ("treeCtrl") lost focus even though it didn't have it
10:00:53 AM: Debug: window wxTreeCtrl@0x560b59434c10 ("treeCtrl") lost focus even though it didn't have it
10:00:53 AM: Debug: window wxTreeCtrl@0x560b59434c10 ("treeCtrl") lost focus even though it didn't have it
10:00:53 AM: Debug: window wxTreeCtrl@0x560b59434c10 ("treeCtrl") lost focus even though it didn't have it
10:00:53 AM: Debug: window wxTreeCtrl@0x560b59434c10 ("treeCtrl") lost focus even though it didn't have it
I did not set up a Local CA file - I had the impression it was an option. I have no idea what the Gtk-CRITICAL error is that follows the "read token" warning.
There is an open issue on github:
https://github.com/prusa3d/PrusaSlicer/issues/14999