This is the official release of OrcaSlicer V2.1.0
This update includes minor fixes and new translations.
For a detailed list of all the new features, please refer to the release notes for v2.1.0 Be...
Appimage doesn’t start because it relies on a system package that does exist anymore, dialogs with grey text on grey backgrounds in dark mode, stl repair not included…
Flatpak is in the works but honestly and hope that helps bit I get better prints out of prusaslicer for some reason so not holding my breath or anything.
The image just isn’t being built correctly which is more a problem with appimages but the fact it’s still broken… Linux is clearly a neglected platform for them.
All the problems I listed have bug reports just nothings happening to fix them.
Libwebkit isn’t actually chromium, it uses blink which is a fork of part of webkit. Understandable confusion though because webkit was part of kde, forked by safari, and then used by through chrome variants for a long time.
The rest of this comment is going to necessarily be nerdy Linux internals. sorry.
Unfortunately, I’m pretty sure chromium includes it inside it’s binary and does provide or use any webkit libraries.
Orca uses it internally for it’s browser so it won’t start unless it has access to the library. When you build a Linux app it includes the name of the library which includes the ABI (basically the version). Newer Linux release include a different version.
Appimage is one of the ways you get around this distro problem by including the versions of libraries. That’s why they’re so big. There are problems with that like how big the apps are stale bundled libraries with security issues but I digress.
Orca hasn’t bundled webkit in the appimage and because of another problem/feature of appimage it falls back on the os library. Since new distros have dropped the older obsolete library version orca can’t start.
That’s a lot but I hope it explains the problem better.
I would like to help but my personal computer doesn’t currently have enough memory to compile orca so back to just watching warning people it’s a coming problem for them too.
Appimage doesn’t start because it relies on a system package that does exist anymore, dialogs with grey text on grey backgrounds in dark mode, stl repair not included…
Flatpak is in the works but honestly and hope that helps bit I get better prints out of prusaslicer for some reason so not holding my breath or anything.
Weird, I’m using the appimage and it starts just fine…what distro are you using?
Ubuntu but it also affects fedora https://github.com/SoftFever/OrcaSlicer/issues/185
The image just isn’t being built correctly which is more a problem with appimages but the fact it’s still broken… Linux is clearly a neglected platform for them.
All the problems I listed have bug reports just nothings happening to fix them.
I run it on Nobara and Fedora, and I only have occasional graphic glitches with the windows
That’s good. I assume you’ve got the old libwebkit installed somehow. There are a dozen reports around this though so it’s a pretty real problem. https://github.com/SoftFever/OrcaSlicer/issues?q=libwebkit2gtk-4.0.so.37
Well I have chromium installed, I use it to segregate Google services to a dedicated browser
Libwebkit isn’t actually chromium, it uses blink which is a fork of part of webkit. Understandable confusion though because webkit was part of kde, forked by safari, and then used by through chrome variants for a long time.
The rest of this comment is going to necessarily be nerdy Linux internals. sorry.
Unfortunately, I’m pretty sure chromium includes it inside it’s binary and does provide or use any webkit libraries.
Orca uses it internally for it’s browser so it won’t start unless it has access to the library. When you build a Linux app it includes the name of the library which includes the ABI (basically the version). Newer Linux release include a different version.
You can see how that specific library stops appearing in Ubuntu releases https://packages.ubuntu.com/search?keywords=libwebkit2gtk-4.0-37
The new version is 6.0 I believe.
Appimage is one of the ways you get around this distro problem by including the versions of libraries. That’s why they’re so big. There are problems with that like how big the apps are stale bundled libraries with security issues but I digress.
Orca hasn’t bundled webkit in the appimage and because of another problem/feature of appimage it falls back on the os library. Since new distros have dropped the older obsolete library version orca can’t start.
That’s a lot but I hope it explains the problem better.
I would like to help but my personal computer doesn’t currently have enough memory to compile orca so back to just watching warning people it’s a coming problem for them too.