Arch Linux

Neoblink

Member

Registered: 2023-04-20

Posts: 4

[SOLVED]Sidefx Houdini --- Stuck on Splash Screen

Hello,
i have a strange issue(apperently with no solution) that suddenly appeared, all my installed versions of Sidefx houdini wont open anymore. all of them stuck on splash screen, 19.5 - 435/493/534/569, using arch linux and just 1 month ago everything was working perfectly. I think it could be some update from Arch, but i could'nd track. I Deleted houdini home folder, and noticed that the new home folder was not fully populated and the houdini-bin process is running but is stucked.

I downgraded the nvidia driver to the 525xx version, still no success. maybe ill try another versions too....or another kernel version....
no crashlogs, just stuck on splash screen.

if you have any more ideas, let me know please....

Last edited by Neoblink (2023-04-21 19:37:28)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 21,750

Re: [SOLVED]Sidefx Houdini --- Stuck on Splash Screen

Run it in a terminal post the output.

Neoblink

Member

Registered: 2023-04-20

Posts: 4

Re: [SOLVED]Sidefx Houdini --- Stuck on Splash Screen

This is the default operation for me. Always run from terminal. This is the problem, not even a tip, not a single line with an error, no crashlogs either.
there is another person with the same problem with 19.5 with no solution on houdini forum a month ago.
He tells me that he restored old versions of system, so i think theres is some update that broke something for me too.

I found some other old post with a python PATH problem with houdini + Arch Linux. Ill try something with this too.
If anyone have some idea....

Thanks for the attention

mokchira

Member

Registered: 2022-01-19

Posts: 13

Re: [SOLVED]Sidefx Houdini --- Stuck on Splash Screen

Could you try attaching gdb to the houdini process after about a minute in (wait long enough that it is past the normal start up time) and then post the backtrace from that? That might give a clue as to where its getting stuck.

I ran into a similar issue recently after a system update and it ended up being that it was getting stuck in an OpenCL driver.

Neoblink

Member

Registered: 2023-04-20

Posts: 4

Re: [SOLVED]Sidefx Houdini --- Stuck on Splash Screen

Hello!!

I never used gdp before but i think i was able to attach process in it.... and i am getting this:

(gdb) attach 1099
Attaching to process 1099
[New LWP 1100]
[New LWP 1101]
[New LWP 1103]
[New LWP 1104]
[New LWP 1105]
[New LWP 1106]
[New LWP 1107]
[New LWP 1108]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
0x00007f997d6a3ab1 in ?? () from /usr/lib/libc.so.6

Let me know if iam doing this right

This issue with OpenCL, how do you fixed it ?

Thanks for the help

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 21,750

Re: [SOLVED]Sidefx Houdini --- Stuck on Splash Screen

doesn't really help at that point, what do you get from executing bt full there?

Regarding the OpenCL issue, if you have blender installed there was one version that hard required the intel opencl stack but that has since been remedied you could try removing those, if installed: https://bbs.archlinux.org/viewtopic.php … 6#p2091676

mokchira

Member

Registered: 2022-01-19

Posts: 13

Re: [SOLVED]Sidefx Houdini --- Stuck on Splash Screen

The backtrace would show where the process is stuck. For instance, if there was a OpenCL driver in the backtrace, well then its pretty obvious that is the issue.

Neoblink, you would just need to type "bt" at the gdb prompt at that point.

In this case though it seems likely that it is the intel opencl driver that is causing this, probably brought in by Blender as V1del suggests.

Last edited by mokchira (2023-04-21 14:32:31)

Neoblink

Member

Registered: 2023-04-20

Posts: 4

Re: [SOLVED]Sidefx Houdini --- Stuck on Splash Screen

Yes!!

Thank you very much mokchira and V1del for the help. Its solved!

The backtrace:

(gdb) bt
#0  0x00007f178e2a3ab1 in ?? () from /usr/lib/libc.so.6
#1  0x00007f17578cd4a3 in clGetExtensionFunctionAddress () from /opt/intel/oneapi/compiler/2023.0.0/linux/lib/libOpenCL.so
#2  0x00007f17578cc6e7 in ?? () from /opt/intel/oneapi/compiler/2023.0.0/linux/lib/libOpenCL.so
#3  0x00007f17578d0bd9 in ?? () from /opt/intel/oneapi/compiler/2023.0.0/linux/lib/libOpenCL.so
#4  0x00007f178e2a3b17 in ?? () from /usr/lib/libc.so.6
#5  0x00007f17578cd4a3 in clGetExtensionFunctionAddress () from /opt/intel/oneapi/compiler/2023.0.0/linux/lib/libOpenCL.so
#6  0x00007f17bf2bb2fa in khrIcdVendorAdd () from /opt/hfs19.5.569/bin/../dsolib/libOpenCL.so.1
#7  0x00007f17bf2bd0f0 in khrIcdOsVendorsEnumerate () from /opt/hfs19.5.569/bin/../dsolib/libOpenCL.so.1
#8  0x00007f178e2a3b17 in ?? () from /usr/lib/libc.so.6
#9  0x00007f17bf2bb7d1 in clGetPlatformIDs () from /opt/hfs19.5.569/bin/../dsolib/libOpenCL.so.1
#10 0x00007f17931c3913 in cl::Platform::get(std::vector<cl::Platform, std::allocator<cl::Platform> >*) () from /opt/hfs19.5.569/bin/../dsolib/libHoudiniUT.so
#11 0x00007f17931bca4b in CE_Context::getDevices(UT_Array<CE_Context::DeviceDescriptor>&, unsigned long) () from /opt/hfs19.5.569/bin/../dsolib/libHoudiniUT.so
#12 0x00007f17c26ffd56 in FUSE_App::initApplication(UI_Manager*, int, char const**) () from /opt/hfs19.5.569/bin/../dsolib/libHoudiniAPPS3.so
#13 0x00007f17c0c15cd7 in OPUI_MainApp::initApplication(UI_Manager*, int, char const**) () from /opt/hfs19.5.569/bin/../dsolib/libHoudiniAPPS2.so
#14 0x00007f17c2775a78 in FUSE_HoudiniBinariesApp::initApplication(UI_Manager*, int, char const**) () from /opt/hfs19.5.569/bin/../dsolib/libHoudiniAPPS3.so
#15 0x00007f17bfcec8a6 in main () from /opt/hfs19.5.569/bin/../dsolib/libHoudiniUI.so
#16 0x00007f178e23c790 in ?? () from /usr/lib/libc.so.6
#17 0x00007f178e23c84a in __libc_start_main () from /usr/lib/libc.so.6
#18 0x00000000004047d4 in ?? ()

https://bbs.archlinux.org/viewtopic.php … 6#p2091676

# pacman -Rs intel-oneapi-compiler-shared-opencl-cpu

Now everything is working again!