-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Application segfaults on start on piOS Bookworm ARM64 #29
Comments
I was not able to reproduce a core with Bookworm on an RPi 4. Could you provide more details of the core and any other errors you may have received, as I do not have a RPi 5. On the distribution side, Bookworm appears to be setting the initial locale on some installs to non-UTF8, which may result in it exiting early. The workaround for this is to enter and set PrusaSlicer itself should probably not hard exit when encountering such a situation, but it looks like issue 11009 is open upstream for this. |
I reported it upstream to PiOS and they fixed their piwiz GUI now raspberrypi-ui/piwiz@4a801cb . Should be fixed when the next image release gets made. For users now, they will have to use rpiconfig as you mention.
I get that popup and then it coredumps. Sorry I should have written that in the initial post. Will try with the locale corrected later. |
Sorry it took me so long to test. |
Description of the issue
Core dumps immediately on running the appimage.
Hardware environment and OS that is being used to run PrusaSlicer-ARM.AppImage
The text was updated successfully, but these errors were encountered: