Can't install Houdini. Exit code 127.

Forums Technical Discussion Can't install Houdini. Exit code 127.

3814 4 1


Bugg: Member; 11 posts; Joined: 11月 2016; オフライン

2022年8月18日 19:01

Hi, I'm trying to install Houdini through the launcher but it's failing. The launcher works but when I try to install Houdini I get an error message that says 'Worker process terminated unexpectedly. Exit code 127.' That's all I have sadly. Any suggestions? I'm on Gentoo but with fairly common setup ( systemd with KDE ).

Attachments:
working_launcher.png (158.3 KB)
install_error.png (55.8 KB)


Bugg: Member; 11 posts; Joined: 11月 2016; オフライン

2022年8月18日 19:55

With the help of strace I figured out it was a problem with polkit ( pkexec to be exact ). Now I have the Houdini installed but it doesn't run. There are two problems.

First, when running houdini I'm getting
/opt/sidefx/Houdini19.5.303/bin/../dsolib/libHoudiniOPZ.so: undefined symbol: _ZN11x175973926021theHasDeterminedTaintE
This one I have no idea how to approach.

Second, Labs package failed to install with error
'Checksum did not match', am I missing some kind of dependency? Hard to tell.

Again, any suggestions are appreciated.


Bugg: Member; 11 posts; Joined: 11月 2016; オフライン

2022年8月19日 14:11

It's not perfect but I managed to make it work. I'm going to leave some info below in case someone needs it.

First, both issues I mentioned in the previous post were solved by installing latest daily build.

Second, I had OpenCL provided by ROCm ( https://github.com/RadeonOpenCompute/ROCm-OpenCL-Runtime [github.com] ) and Houdini was just crashing on startup with it, not sure exactly why. I tried using mesa for OpenCL but it reports OpenCL 1.1 only ( ROCm was giving me 2.x ). At least Houdini starts now.

I read somewhere that you can fake OpenCL 1.2 support by defining:
CLOVER_PLATFORM_VERSION_OVERRIDE=1.2
CLOVER_DEVICE_VERSION_OVERRIDE=1.2
CLOVER_DEVICE_CLC_VERSION_OVERRIDE=1.2

Depending on the hardware you have and the programs you run it may work. Use at your own risk.


dpeter99: Member; 3 posts; Joined: 8月 2017; オフライン

2025年1月16日 16:47

Hi!
I'm having this exact same issue when trying to install inside a distrobox container.
I'm getting the "Worker process terminated unexpectedly. Exit code 127". can you explain what you did to fix it?

I'm running the following commands:

> distrobox create houdini
> distrobox enter

//inside the box
> sudo dnf group install base-graphical core fonts multimedia
> sudo dnf install kate strace
// this is the installer form the website
// I let it install to where it wants
> ~/Downloads/_Installs/install_houdini_launcher.sh 
> /opt/sidefx/launcher/bin/houdini_launcher

I'm on Fedora 41 Kinoite (Atomic distro, KDE)

Any help would be apreciated

EDIT:
When I try to install the non launcher version, it finishes fine and i can launch the editor.
However it crashes instantly with the following crash log:

Crash report from bb67b288; Houdini FX Version 20.5.445 [linux-x86_64-gcc11.2]
Uptime 1 seconds
Fri Jan 17 10:50:47 2025
Caught signal 11

Traceback from 92382 ThreadId=0x7fbccfe35300
AP_Interface::coreDumpChaser(UTsignalHandlerArg) <libHoudiniUI.so>
AP_Interface::si_CrashHandler::chaser(UTsignalHandlerArg) <libHoudiniUI.so>
signalCallback(UTsignalHandlerArg) <libHoudiniUT.so>
UT_Signal::UT_ComboSignalHandler::operator()(int, siginfo_t*, void*) const <libHoudiniUT.so>
UT_Signal::processSignal(int, siginfo_t*, void*) <libHoudiniUT.so>
__sigaction <libc.so.6>

EDIT2:
When I create the distrobox with ``--nvidia`` and install using the non-launcher installer.
It does start up but crashed when I try to open the add node dropdown and searching around.

No OpenCL platform has the specified device type (HOUDINI_OCL_DEVICETYPE): .
  Falling back to built-in CPU OpenCL driver (see HOUDINI_USE_HFS_OCL)
No OpenCL platform has the specified device type (HOUDINI_OCL_DEVICETYPE): .
  Falling back to built-in CPU OpenCL driver (see HOUDINI_USE_HFS_OCL)
ERROR: Could not find usable Vulkan Device:
Available Physical Devices:
  SwiftShader Device (LLVM 10.0.0)
  Api Version  1.3.0
Spawn Error: : No such file or directory
Error running xmessage
Argument list:
   0: xmessage
   1: Vulkan could not be initialized. Falling back to OpenGL.
Generating new icons...
Done generating new icons.
107542: Fatal error: Segmentation fault (sent by pid 8)
Crash log saved to /tmp/houdini_temp/crash.untitled.dpeter99_107542_log.txt

Crash report from bb67b288; Houdini FX Version 20.5.445 [linux-x86_64-gcc11.2]
Uptime 28 seconds
Fri Jan 17 11:11:07 2025
Caught signal 11

Traceback from 107542 ThreadId=0x7f8073b76300
AP_Interface::coreDumpChaser(UTsignalHandlerArg) <libHoudiniUI.so>
AP_Interface::si_CrashHandler::chaser(UTsignalHandlerArg) <libHoudiniUI.so>
signalCallback(UTsignalHandlerArg) <libHoudiniUT.so>
UT_Signal::UT_ComboSignalHandler::operator()(int, siginfo_t*, void*) const <libHoudiniUT.so>
UT_Signal::processSignal(int, siginfo_t*, void*) <libHoudiniUT.so>
__sigaction <libc.so.6>
glXCreateGLXPixmap <libGLX_nvidia.so.0>
_nv006glcore <libnvidia-glcore.so.565.77>
vk_icdNegotiateLoaderICDInterfaceVersion <libGLX_nvidia.so.0>
[0x7248e] <libGLX_nvidia.so.0>
qt_plugin_instance <libqxcb-glx-integration.so>
RE_Server::GLSwapBuffers(RE_Window*) <libHoudiniUI.so>
UI_Window::swapBuffers() <libHoudiniUI.so>
UI_Window::clearWindow(UT_Color const&) <libHoudiniUI.so>
UI_Window::doRedrawSubclass() <libHoudiniUI.so>
UI_Window::doRedraw() <libHoudiniUI.so>
UI_Queue::doWindowRedraws() <libHoudiniUI.so>
UI_Queue::drain() <libHoudiniUI.so>
UI_Queue::eventLoop() <libHoudiniUI.so>
main <libHoudiniUI.so>
__libc_init_first <libc.so.6>
__libc_start_main <libc.so.6>
[0x40365c] <houdini-bin>

Edited by dpeter99 - 2025年1月17日 05:13:53


charlesjm: Member; 1 posts; Joined: 7月 2026; オフライン

2026年7月5日 10:50

Title: Fix for Houdini Launcher “Worker process terminated unexpectedly — Exit code 127” on Arch/Sway

I was trying to install Houdini through the SideFX Launcher on Arch Linux with SwayFX. The download started, but the installer failed
with:

> Worker process terminated unexpectedly. Exit code 127.

The issue wasn’t Houdini itself. The Launcher uses pkexec to request administrator privileges, but my Sway session had no graphical polkit
authentication agent. Having the base polkit package installed wasn’t enough.

The fix was:

sudo pacman -S polkit-gnome

Then I added this to ~/.config/sway/config:

exec /usr/lib/polkit-gnome/polkit-gnome-authentication-agent-1

To start it immediately without logging out:

swaymsg exec /usr/lib/polkit-gnome/polkit-gnome-authentication-agent-1

I verified it with:

pkexec /usr/bin/true

A graphical password prompt appeared and the command completed successfully. After retrying the Houdini installation, it worked.

So if you’re getting exit code 127 from the Houdini Launcher on Sway or another minimal Wayland compositor, check whether a polkit
authentication agent is installed and running.

Quick Links

                    
                        Search links
                        Show recent posts
                        Show unanswered posts