PrusaSlicer 2.9.0 Debian/Linux does no
Dear All,
the new PrusaSclicer 2.9.0 does not start after installation with flatpak.
flatpak run com.prusa3d.PrusaSlicer
--------------------------------------------------------------------------
Message: 17:03:00: Starting PrusaSlicer flatpak with entrypoint script
--------------------------------------------------------------------------
WARN: detected locale error, trying to use fallback 1localelocale:
Cannot set LC_CTYPE to default locale: No such file or directorylocale: Cannot set LC_MESSAGES to default locale:
No such file or directorylocale: Cannot set LC_COLLATE to default locale:
No such file or directoryWARN: de_DE.UTF-8 is not available in locale -a. Setting LC_ALL to en_US.UTF-8.
----------------------------------------------------------------------------
locale -a
shows i have on my system
de_DE.utf8
(so UTF8 not in upper case). Is this a bug or can I fix this somehow?
Thanks and best regards
Stephan
RE: PrusaSlicer 2.9.0 Debian/Linux does no
Did you run the two commands mentioned in the dialog box from the screenshot? This would set up the environment variables that are necessary.
If you do not want to start PrusaSlicer from the command line every time, you could copy the file
/var/lib/flatpak/app/com.prusa3d.PrusaSlicer/x86_64/stable/active/export/share/applications/com.prusa3d.PrusaSlicer.desktop
into the directory ~/.local/share/applications/, then log out from your desktop and log in again. After that PrusaSlicer should be integrated into your application menu, probably under "Graphics".
RE: PrusaSlicer 2.9.0 Debian/Linux does no
Yes off course I did, but without success.
I created every locale possible...even this did not help. Could it be a problem with uppercase/lowercase?
The debian system created ????.utf8 with no dash "-" and the PrusaSlicer expects ???.UTF-8 in uppercase with a "-" dash.
RE: PrusaSlicer 2.9.0 Debian/Linux does no
The output of "locale -a" gives me:
C C.utf8 de_DE.utf8 en_GB.utf8 POSIX
The content of the file /etc/default/locale on my system is:
LANG=de_DE.UTF-8
The former are locale files (all are listed in /usr/share/i18n/SUPPORTED) and the latter is an environment variable. That accounts for the difference in upper/lower case.
The command "flatpak run com.prusa3d.PrusaSlicer" starts the slicer without problems on my system (debian unstable).
RE: PrusaSlicer 2.9.0 Debian/Linux does no
Exactly the same here.
I am using "Linux debian 6.1.0-28-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.119-1 (2024-11-22) x86_64 GNU/Linux"
RE: PrusaSlicer 2.9.0 Debian/Linux does no
I don't think that the kernel version has an impact on this.
You could try to set the environment variable first with this:
export LC_ALL="de_DE.UTF-8" && flatpak run com.prusa3d.PrusaSlicer
RE: PrusaSlicer 2.9.0 Debian/Linux does no
You can also set environment variables for specific flatpak apps with Flatseal:
RE: PrusaSlicer 2.9.0 Debian/Linux does no
sudo dpkg-reconfigure locales
and then ensure to select en_US.UTF-8
also please run
cat /etc/os-release
so it shows more details about the operating system.
See my GitHub and printables.com for some 3d stuff that you may like.
RE: PrusaSlicer 2.9.0 Debian/Linux does no
As a follow-up to the flatpak PrusaSlicer on debian: I had a few crashes of the app when opening an existing project and the app opening showing just an empty space on the plater tab. I then managed to get the source compiled on my system, so no need for the flatpak package anymore for me. If anyone should run into similar problems with the flatpak package, I can provide more details.
RE: PrusaSlicer 2.9.0 Debian/Linux does no
For anyone wanting to try I got it compiling on my Debian stable install - just following the instructions at (though it took a while)
https://github.com/prusa3d/PrusaSlicer/blob/master/doc/How%20to%20build%20-%20Linux%20et%20al.md
I didn't bother trying Flatpack
RE: PrusaSlicer 2.9.0 Debian/Linux does no
On my system the compile ran into the error described in this github issue: https://github.com/prusa3d/PrusaSlicer/issues/13560
The solution for me was following the instructions in the second post there.