Hello, There are no Linux builds for Slicer preview and no extensions since a few days. Slicer clean-built today (e1881207) on Arch runs (--ignore-slicerrc) suspiciously with the following in stdout: QFont::fromString: Invalid description 'Noto Sans,11,-1,5,400,0,0,0,0,0,0,0,0,0,0,1' Traceback (m…

See the following details below. It appears there may be an issue specific to Linux builds that is not being observed for Windows or macOS builds. BUG: Revert Python initialization change that breaks PythonQt integration main ← j…

Thanks for the link. After reverting the referenced commit, Slicer builds and runs fine. (There’s a new issue regarding VMTK and ITK, that’s another headache.)

Thanks for your patience :folded_hands: A pull request fixing the python initialization has just been published :rocket: See PR#8582 Fixes regression introduced in: 7a26aa1 (“ENH: Update Python initialization for compatibility with isolated mode”) 3bace0b (“ENH: Update Python initialization to…

[image] chir.set: There’s a new issue regarding VMTK and ITK, that’s another headache. Do you have more details about this ? Also, I suggest you base your build on the linked pull request that should be integrated into main shortly.

For reference, here is the corresponding VMTK issue: VMTK libs build failure · Issue #162 · vmtk/SlicerExtension-VMTK · GitHub

[image] jcfr: I suggest you base your build on the linked pull request that should be integrated into main shortly. Thank you for considering both issues. My last build at 407906c367 does not yet include PR 8582 . I’ll keep you updated tomorrow. Regards.

[image] chir.set: I’ll keep you updated tomorrow. Unfortunately, Slicer does not start with a usable result when built at 533859698. The VMTK issue (related or not) persists. Here is a trimmed stdout (too long for the editor) with --ignore-slicerrc from the build tree: QFont::fromString: In…

Here is the output when starting in C.UTF-8 locale: QT_QPA_PLATFORM="xcb" LANG=C.UTF-8 LC_ALL=C.UTF-8 src/Slicer-SuperBuild9/Slicer-build/Slicer QFont::fromString: Invalid description 'Noto Sans,11,-1,5,400,0,0,0,0,0,0,0,0,0,0,1' Switch to module: "Volumes" Loading Slicer RC file [/home/user/.slic…

Further tests: The default locale of the environment is fr_FR.UTF-8, which is the only locale active in /etc/locale.gen. The bunch of decode errors before loading .slicerrc.py occur with the default locale in the environment or on the command line. They do not appear with anything else : {C,en_US…

[image] chir.set: (I don’t know yet if Slicer is usable since I’m currently doing that remotely.) @jcfr It’s usable, but like a disabled person. It must be started with a locale that has not been generated for glibc. Modules are functional, even Python modules, but the rc file fails to load…

Is there an issue with Linux builds currently?

Support

jcfr (Jean Christophe Fillion Robin) July 22, 2025, 5:31am 12

Following the upgrade of the Linux build environment, the Preview build should be available for download tomorrow:

Slicer Build Environment Upgraded to `qt5-almalinux8-gcc14`

Topic		Replies	Views
Crash when initializing app built and run from Ubuntu 20.04 Development build	29	2225	January 17, 2021
Can't start Slicer on Linux on one machine Support	57	3555	January 21, 2020
Slicer crash on fresh build Development	7	1217	May 23, 2017
SlicerRT built from source cannot start Support build	42	392	August 7, 2025
Build Slicer on Windows 10 Failed Support qt	49	5028	September 17, 2021

Is there an issue with Linux builds currently?

Related topics