Houdini 19 doesn't load AT ALL on Ubuntu 21.10

Forums Houdini Lounge Houdini 19 doesn't load AT ALL on Ubuntu 21.10

50235 120 17


Mirko Jankovic: Member; 164 posts; Joined: 8月 2015; Offline

2021年12月31日 1:36

I'm on Fedora 35 here, propreitery drivers only nvidia, same thing happening still. .477 daily build also same situation.


Hampus Hedberg2: Member; 13 posts; Joined: 5月 2015; Offline

2021年12月31日 6:31

alunablue
Do not try to overwrite your nvidia driver.

You must completely remove everything to do with nvidia:
sudo apt-get remove --purge '^nvidia-.*'

Then reinstall the desktop:
sudo apt-get install ubuntu-desktop

You can then install nvidea-driver-470 (proprietary, tested)

Hope that helps.

Thanks for taking the time, but I'm already running 470, never ran a newer version.
It definitely happened between 21.04 and 21.10 as it worked flawlessly before.
Everything except Houdini also works as intended.
Also, since the same thing happens in 18.5 I'm guessing it's some library in the system that has changed functionality somehow.

Edited by Hampus Hedberg2 - 2021年12月31日 06:34:02


ajz3d: Member; 570 posts; Joined: 8月 2014; Offline

2021年12月31日 13:48

For what it's worth, I haven't experienced any of those problems on current Debian Testing (Bookworm).
- kernel: 5.15.0-2-amd64, #1 SMP Debian 5.15.5-2 (2021-12-18)
- nvidia-driver: 470.86-1
- libopengl0: 1.3.4-2+b1
- freeglut3: 2.8.1-6
- freeglut3-dev: not installed

libxcb:

libpthread-stubs0-dev/testing,now 0.4-1 amd64 [installed,automatic]
libxcb-composite0/testing,now 1.14-3 amd64 [installed,automatic]
libxcb-cursor0/testing,now 0.1.1-4 amd64 [installed,automatic]
libxcb-damage0/testing,now 1.14-3 amd64 [installed,automatic]
libxcb-dri2-0/testing,now 1.14-3 amd64 [installed,automatic]
libxcb-dri3-0/testing,now 1.14-3 amd64 [installed,automatic]
libxcb-ewmh2/testing,now 0.4.1-1.1 amd64 [installed,automatic]
libxcb-glx0/testing,now 1.14-3 amd64 [installed,automatic]
libxcb-icccm4/testing,now 0.4.1-1.1 amd64 [installed,automatic]
libxcb-image0/testing,now 0.4.0-1+b3 amd64 [installed,automatic]
libxcb-keysyms1/testing,now 0.4.0-1+b2 amd64 [installed,automatic]
libxcb-present0/testing,now 1.14-3 amd64 [installed,automatic]
libxcb-randr0/testing,now 1.14-3 amd64 [installed,automatic]
libxcb-render-util0/testing,now 0.3.9-1+b1 amd64 [installed,automatic]
libxcb-render0/testing,now 1.14-3 amd64 [installed,automatic]
libxcb-render0-dev/testing,now 1.14-3 amd64 [installed,automatic]
libxcb-res0/testing,now 1.14-3 amd64 [installed,automatic]
libxcb-shape0/testing,now 1.14-3 amd64 [installed,automatic]
libxcb-shm0/testing,now 1.14-3 amd64 [installed,automatic]
libxcb-shm0-dev/testing,now 1.14-3 amd64 [installed,automatic]
libxcb-sync1/testing,now 1.14-3 amd64 [installed,automatic]
libxcb-util1/testing,now 0.4.0-1+b1 amd64 [installed,automatic]
libxcb-xfixes0/testing,now 1.14-3 amd64 [installed,automatic]
libxcb-xinerama0/testing,now 1.14-3 amd64 [installed,automatic]
libxcb-xinput0/testing,now 1.14-3 amd64 [installed,automatic]
libxcb-xkb1/testing,now 1.14-3 amd64 [installed,automatic]
libxcb-xv0/testing,now 1.14-3 amd64 [installed,automatic]
libxcb1/testing,now 1.14-3 amd64 [installed,automatic]
libxcb1-dev/testing,now 1.14-3 amd64 [installed,automatic]

I don't use any extraordinary envvars in houdini.envnor in Houdini launcher. Just some variables related to 3rd party stuff. I'm not LD_PRELOAD-ing any libraries.

Version 19.0 does come with its own share of brand new annoying problems, when compared to 18.5 (I think something in Qt has changed for the worse), but fortunately for me, none of them are what you guys have described here. Nothing that prevents Houdini from running on Debian Bookworm.

I tested Karma XPU, and so far it didn't segfault on me.

While my post might not be very helpful, I think it at least proves that freeglut3-devpackage is not mandatory for launching Houdini 19. If you have any questions about specific packages and their versions that I have installed, don't hesitate to ask.

Edited by ajz3d - 2021年12月31日 13:50:14


mzigaib: Member; 975 posts; Joined: 4月 2008; Offline

2022年1月17日 2:25

I am still having the same issue but worse now on Fedora 35 with build 495.

Anyone else?

https://vimeo.com/user2163076 [vimeo.com]


mzigaib: Member; 975 posts; Joined: 4月 2008; Offline

2022年1月18日 0:23

I know it is a little off topic but I would like also to see if anyone else using Fedora 35 has the same issue, maybe it is related?
Help doesn't open up on my end, anyone else have this issue?

Edited by mzigaib - 2022年1月18日 00:24:13

https://vimeo.com/user2163076 [vimeo.com]


Aietes: Member; 13 posts; Joined: 12月 2019; Offline

2022年1月18日 12:06

Same issue here on Fedora 35.


Mirko Jankovic: Member; 164 posts; Joined: 8月 2015; Offline

2022年1月19日 8:12

also Fedora 35, same problem... And there i was praising sidefx for having Houdini install and work perfectly fine on all distros, unlike maya that needs ton of libs and presets to even start

((


Hampus Hedberg2: Member; 13 posts; Joined: 5月 2015; Offline

2022年1月19日 8:16

On my System I experience the same issue with 18.5 so can't blame Houdini here.
I went back to an older OS version.


chrism: スタッフ; 2540 posts; Joined: 9月 2007; Offline

2022年1月21日 9:59

Remember you can contact support@sidefx.com if you're having problems installing or running Houdini.

The requirements have changed between 18.5 and 19.0, and some of the OS's have changed what they install by default in their more recent versions.
Check our system requirements page: https://sidefx.com/sysreq [sidefx.com]
Chances are you're missing some libraries that Houdini needs.

For example, many of our users have found that one or both of these commands sort things out for them:
sudo apt install libopengl0 freeglut3 freeglut3-dev
sudo apt-get install --reinstall libxcb-xinerama0

At any rate, support can help you if you can't get up and running. Please contact them.

Chris McSpurren
Senior Quality Assurance Specialist
SideFX


edward: Member; 7871 posts; Joined: 7月 2005; Offline

2022年2月25日 9:24

FWIW, I think the best workaround for now on glibc 2.34 distro's (anything ubuntu related 21.10+ or Fedora 35+) is to do the following that permanently disables use of jemalloc. Make sure to NOT set LD_LIBRARY_PATH nor LD_PRELOAD after doing this:

cd $HFS/dsolib
cp libjemalloc.so.1 empty_jemalloc/libjemalloc.so.1.orig
cp empty_jemalloc/libjemalloc.so.1 .

This of course will make Houdini run slow as molasses so the best solution is still to downgrade your distro unfortunately. Or if someone is a super Linux user, figure out a way to preload an older glibc version when running Houdini. For background, glibc maintainers pretty much said that they intended to break backwards compatibility and will never add it back: https://sourceware.org/bugzilla/show_bug.cgi?id=16939 [sourceware.org]

Edited by edward - 2022年2月25日 09:29:45


tas3d: Member; 120 posts; Joined: 1月 2012; Offline

2022年3月4日 13:09

Hi,

Im on Ubuntu 20.04.4 LTS, H19.0.531, AMD Ryzen 9 and Nvidia 2070 GPU.
Getting this crash on houdini startup

Houdini FX Version 19.0.531 [linux-x86_64-gcc9.3]
Uptime 1 seconds
Fri Mar  4 09:37:44 2022
Caught signal 11

Traceback from 2951 ThreadId=0x7f1b4aa7fe00
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>
__funlockfile <libpthread.so.0>

I tried few suggested fixes mentioned above:
sudo apt install libopengl0 freeglut3 freeglut3-dev
sudo apt-get install --reinstall libxcb-xinerama0

But still no love.

Running export LD_PRELOAD="/lib/x86_64-linux-gnu/libc_malloc_debug.so.0 doesn't work, it seems like this file does not exist on my system. I have already libc6 installed, perhaps I need something else?

I contaced SESI support, but they have no solution. Any ideas?
Thanks!

Edited by tas3d - 2022年3月4日 13:43:08

Michal Tas Maciejewski @ www.vfxtricks.com


edward: Member; 7871 posts; Joined: 7月 2005; Offline

2022年3月4日 15:17

tas3d
Im on Ubuntu 20.04.4 LTS, H19.0.531, AMD Ryzen 9 and Nvidia 2070 GPU.
Getting this crash on houdini startup

Probably something related to your set up since other people seem to work fine? eg. https://www.sidefx.com/forum/topic/81386/?page=3#post-353732 [www.sidefx.com]

To first see if it's video driver related, run these commands (after sourcing houdini_setup)

$ lsb_release -a
$ hgpuinfo


tas3d: Member; 120 posts; Joined: 1月 2012; Offline

2022年3月4日 15:47

thanks for helping edward!

notice seg fault at the end of hgpuinfo

hgpuinfo 
OpenGL Vendor:            NVIDIA Corporation
OpenGL Renderer:          NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2
OpenGL Version:           4.6.0 NVIDIA 470.103.01
OpenGL Shading Language:  4.60 NVIDIA
Detected:                 NVidia Consumer
                          8192 MB
                          470.103.1.0

Supported Extensions not in OpenGL 3.3 (Version):
    GLX_SGI_swap_control                   
    GL_ARB_base_instance                    (4.2)
    GL_ARB_bindless_texture                
    GL_ARB_bindless_texture                
    GL_ARB_buffer_storage                   (4.4)
    GL_ARB_clear_buffer                     (4.3)
    GL_ARB_compatibility                   
    GL_ARB_compute_shader                   (4.3)
    GL_ARB_copy_texture                     (4.3)
    GL_ARB_debug_output                    
    GL_ARB_draw_indirect                    (4.0)
    GL_ARB_gpu_shader5                      (4.0)
    GL_ARB_gpu_shader_fp64                  (4.0)
    GL_ARB_multi_bind                       (4.4)
    GL_ARB_program_interface_query          (4.3)
    GL_ARB_robustness                      
    GL_ARB_sample_shading                   (4.0)
    GL_ARB_separate_shader_objects          (4.1)
    GL_ARB_shader_atomic_counters           (4.2)
    GL_ARB_shader_image_load_store          (4.2)
    GL_ARB_shader_storage_buffer_object     (4.3)
    GL_ARB_shading_language_packing         (4.2)
    GL_ARB_tessellation_shader              (4.0)
    GL_ARB_texture_buffer_object_rgb32      (4.0)
    GL_ARB_texture_buffer_range             (4.3)
    GL_ARB_texture_cube_map_array           (4.0)
    GL_ARB_texture_filter_anisotropic       (4.6)
    GL_ARB_transform_feedback3              (4.0)
    GL_ARB_vertex_attrib_64bit              (4.1)
    GL_EXT_abgr                            
    GL_EXT_blend_minmax                    
    GL_EXT_direct_state_access             
    GL_KHR_debug                            (4.3)
    GL_NVX_gpu_memory_info                 
    GL_NV_depth_buffer_float               
    GL_NV_gpu_shader5                      

Unsupported OpenGL Extensions used by Houdini:
    EXT_extensions_string                  
    GL_ATI_meminfo                         
 
OpenGL Limits:
   ELEMENTS_VERTICES                        1048576
   ELEMENTS_INDICES                         1048576
   VERTEX_UNITS                             32
   TESS_CONTROL_TEXTURE_IMAGE_UNITS         32
   TESS_EVALUATION_TEXTURE_IMAGE_UNITS      32
   GEOMETRY_UNITS                           32
   FRAGMENT_IMAGE_UNITS                     32
   COMBINED_UNITS                           192
   TEXTURE_SIZE                             32768
   3D_TEXTURE_SIZE                          16384
   CUBE_MAP_TEXTURE_SIZE                    32768
   RECTANGLE_TEXTURE_SIZE                   32768
   TEXTURE_ARRAY_LAYERS                     2048
   MAX_COLOR_TEXTURE_SAMPLES                32
   MAX_DEPTH_TEXTURE_SAMPLES                32
   FBO_ATTACHMENTS                          8
   DRAW_BUFFERS                             8
   VIEWPORT_DIMS                            32768x32768
   VERTEX_UNIFORMS                          4096
   FRAGMENT_UNIFORMS                        4096
   VERTEX_ATTRIBS                           16
   VERTEX_OUTPUT_COMPONENTS                 128
   MAX_CLIP_DISTANCES                       8
   PATCH_VERTICES                           32
   TESS_GEN_LEVEL                           64
   TESS_PATCH_COMPONENTS                    120
   TESS_CONTROL_OUTPUT_COMPONENTS           128
   TESS_CONTROL_TOTAL_OUTPUT_COMPONENTS     4216
   TESS_EVALUATION_OUTPUT_COMPONENTS        128
   GEOMETRY_UNIFORM_COMPONENTS              2048
   GEOMETRY_INPUT_COMPONENTS                128
   GEOMETRY_OUTPUT_COMPONENTS               128
   GEOMETRY_TOTAL_OUTPUT_COMPONENTS         1024
   GEOMETRY_OUTPUT_VERTICES                 1024
   UNIFORM_BLOCKS                           84
   UNIFORM_BLOCK_SIZE                       65536
   UNIFORM_BUFFER_BINDINGS                  84
   COMBINED_VERT_UNIFORM_BLOCKS             14
   COMBINED_VERT_UNIFORM_COMPS              233472
   TESS_CONTROL_UNIFORM_BLOCKS              14
   TESS_CONTROL_UNIFORM_COMPONENTS          2048
   TESS_EVALUATION_UNIFORM_BLOCKS           14
   TESS_EVALUATION_UNIFORM_COMPONENTS       2048
   COMBINED_GEO_UNIFORM_BLOCKS              14
   COMBINED_GEO_UNIFORM_COMPS               231424
   COMBINED_FRAG_UNIFORM_BLOCKS             14
   COMBINED_FRAG_UNIFORM_COMPS              233472
   MAX_FRAGMENT_STORAGE_BLOCKS              16
   MAX_STORAGE_BLOCK_BINDINGS               96
   TRANSFORM_FEEDBACK_INT_COMPS             128
   TRANSFORM_FEEDBACK_SEP_COMPS             4
   TRANSFORM_FEEDBACK_SEP_ATTRIBS           4
   LINE_WIDTH_RANGE                         0.5 - 10
   LINE_WIDTH_GRANULARITY                   0.125
   POINT_SIZE_RANGE                         1 - 189.875
   POINT_SIZE_GRANULARITY                   0.125
Segmentation fault (core dumped)

lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 20.04.4 LTS
Release:	20.04
Codename:	focal

Michal Tas Maciejewski @ www.vfxtricks.com


tas3d: Member; 120 posts; Joined: 1月 2012; Offline

2022年3月4日 15:53

I got it, I installed lsb-core package.

sudo apt-get install lsb-core

H19 starts up!

thanks a million

Edited by tas3d - 2022年3月4日 15:53:55

Michal Tas Maciejewski @ www.vfxtricks.com


edward: Member; 7871 posts; Joined: 7月 2005; Offline

2022年3月4日 19:45

tas3d
I got it, I installed lsb-core package.

H19 starts up!

thanks a million

Ok, that does not make any sense.

Does running hgpuinfostill crash?


tas3d: Member; 120 posts; Joined: 1月 2012; Offline

2022年3月4日 20:03

haha, im happy it runs

yes, now hgpuinfo finishes.
Seems like it was crashing on querying OpenCl Platform info block.

Edited by tas3d - 2022年3月4日 22:13:54

Michal Tas Maciejewski @ www.vfxtricks.com


edward: Member; 7871 posts; Joined: 7月 2005; Offline

2022年3月4日 21:35

Weirdest thing, maybe there was some OpenCL driver dependency that somehow got installed. Or maybe a reboot happened in between that suddenly fixed things? Glad you've got it running!


rasmus.ronnqvist: Member; 1 posts; Joined: 3月 2022; Offline

2022年3月27日 9:52

I managed to get Houdini 19 to load on Fedora 35.
Graphics: Nvidia Proprietary Drivers. 510.47.03
Kernel: 5.16.16-200.fc35.x86_64
WM: awesome (x11)

I had the same issue posted in this thread. The launcher installed like normal but I could not start any Houdini version. I was only met with the Error:

munmap_chunk(): invalid pointer
Aborted (core dumped)

Using the Information posted in this thread I managed to get Houdini 19 running.
This is what i did.

First I installed all the dependencies. I do not know if this is necessary but a previous user recommended this.

sudo dnf install libxcb libxcb-devel xcb-util xcb-util-devel xcb-util-*-devel libX11-devel libXrender-devel libxkbcommon-devel libxkbcommon-x11-devel libXi-devel libdrm-devel libXcursor-devel libXcomposite-devel

Then I sourced the houdini_setup_bash and preloaded libc_malloc_debug.so.0. Ubuntu users apparently have to do something similar but this file is located in /lib64/ on Fedora 35.

cd /opt/hfs19.0/
source houdini_setup_bash
export LD_PRELOAD="/lib64/libc_malloc_debug.so.0"
houdini &

Now after doing all this and executing "houdini &" in "/opt/hfs19.0/" Houdini 19 starts like normal.

Edited by rasmus.ronnqvist - 2022年4月7日 13:50:39


nickfr: Member; 26 posts; Joined: 3月 2021; Offline

2022年4月3日 4:55

So is Houdini 19 compatible with Wayland? Or only x11? Fedora 35 runs Wayland right


edward: Member; 7871 posts; Joined: 7月 2005; Offline

2022年4月3日 13:03

Wayland is not currently supported AFAIK, nor have I heard of anyone using Houdini on Wayland. Fedora 35 is a non-starter because it uses glibc 2.34, wayland or no wayland.

Again, please see https://www.sidefx.com/forum/topic/81386/?page=4#post-357435 [www.sidefx.com] where I think disabling jemalloc is probably a better workaround than preloading the DEBUG glibc allocator. Using Houdini on Fedora 35 with these workarounds will be slower than running Houdini on a distro still running on glibc 2.33 or below.

Edited by edward - 2022年4月3日 13:07:22

Quick Links

                    
                        Search links
                        Show recent posts
                        Show unanswered posts