https://bugs.kde.org/show_bug.cgi?id=522600
--- Comment #30 from Furgo <[email protected]> --- Thanks. This has been fixed now. For future reference, these two commits I believe fixed the original issue (libxcb binaries being unintendedly pruned): 1. https://invent.kde.org/neon/snap-packaging/kf6-core/-/commit/89a1bec0650a255ba43a4496bd4aaeac4a90e566 2. https://invent.kde.org/neon/snap-packaging/kf6-core/-/commit/1b0f9952461f2af52150e2da769dd944cf092eaa FreeCAD then still would not start. But this time due to an unrelated bug on the FreeCAD snap itself. This was in turn fixed by: - https://github.com/FreeCAD/FreeCAD-snap/pull/312 The current `edge` snap available from the store (rev. 2738) now contains this fix and runs without crashing. However, there is still an issue with the FreeCAD `stable` snap. At the time, it was built against the Qt 6.10 binaries provided by the KDE snaps before the 6.11 bump. With the new 6.11 snaps, the FreeCAD `stable` snap crashes on a version mismatch. I believe a rebuild will fix it, but it would be great if the KDE packages would adhere to a release policy that would allow stable snaps that depend on the kde-neon6 extension to pin onto a channel that contains the version they were released with. This would prevent third party apps such as FreeCAD stable releases to crash whenever new KDE packages are published. -- You are receiving this mail because: You are watching all bug changes.
