Prusa Slicer File Browser - On Manjaro - It's 2025 not 1990...
 
Avisos
Vaciar todo

Prusa Slicer File Browser - On Manjaro - It's 2025 not 1990...  

  RSS
Steve
(@steve-39)
Eminent Member
Prusa Slicer File Browser - On Manjaro - It's 2025 not 1990...

Hi!

Is this how a file browser should look like in 2025? 

Not showing any mounted network drives, not able to type in the address field and a side bar that is absolut useless. 

I know that on Linux (Manjaro in this case) there are limitation on the used UI-Toolkit but this is just not usable at all. 
Any plan to change this to something more usable? 

 

Respondido : 21/01/2025 6:14 pm
Steve
(@steve-39)
Eminent Member
Topic starter answered:
RE: Prusa Slicer File Browser - On Manjaro - It's 2025 not 1990...

BTW: the AppImage versions had no problem showing mounted network drives. So this might be a problem of Flatpak. 
And if you want to see how a proper file browser nowadays looks like, take a look at Blender's very convenient browser:

Respondido : 21/01/2025 6:43 pm
Neophyl
(@neophyl)
Illustrious Member
RE: Prusa Slicer File Browser - On Manjaro - It's 2025 not 1990...

It is a limitation of flatpack.  There's several threads on here about it as well as multiple posts on the Prusa Slicer github.  So much so they had to sticky a post about it. 

Common fix is to use something called Flatseal.  https://github.com/prusa3d/PrusaSlicer/issues/13820   

Respondido : 21/01/2025 7:00 pm
Steve
(@steve-39)
Eminent Member
Topic starter answered:
RE: Prusa Slicer File Browser - On Manjaro - It's 2025 not 1990...

Thanks for the workaround! 👍 
Great to hear that I'm not the only one... But the missing network links are just the tip of the iceberg. 
How hard can it be to program a proper file browser? (I guess programming such a slicer like this is MUCH harder...)

Respondido : 21/01/2025 7:07 pm
Diem
 Diem
(@diem)
Illustrious Member

How hard can it be to program a proper file browser?

The file browser and net connectivity issues are due to using a packaging system (Flatpak) designed to compartmentalise software with maximum security.  This was needed because AppImages couldn't easily handle the complexities of WebKit and its dependencies.  Webkit was needed because Prusa had decided to integrate Printables downloads into the slicer in a manner hard to generalise in C.  They are using C because they decided to get rid of all perl scripts.  They decided to get rid of perl because - actually I have no idea why they decided to get rid of perl.  Perl, of course, has libraries (Cpan) containing everything needed for high security, file browsing and integrating file downloads...

Cheerio,

Respondido : 22/01/2025 4:06 am
Compartir: