kodi segmentation fault [solved]

alexela · 2022-04-05 19:31:26

Hi,

since i upgraded, kodi does not launch anymore, and downgrading the package itself does not solve the issue (so other packages may be involved…).
In the console, i do have a «/usr/bin/kodi : line 186: xxxx segmentation fault: (core dumped) s{KODI_BINARY} sSAVED_ARGS» message where xxxx is a changing number.
I can give the crash_log if wanted.
I tried to remove the binary and reinstall the package without any success.
My system is up-to-date (kodi-19.4-2).

OS: Arch Linux x86_64
Host: XS35V4 V1.0
Kernel: 5.17.1-arch1-1
CPU: Intel Celeron J1900 (4) @ 2.415GHz
GPU: Intel Atom Processor Z36xxx/Z37xxx Series Graphics & Display

Thanks,
Alex

Last edited by alexela (2022-04-10 22:30:06)

alexela · 2022-04-05 19:44:23

I've just tried to downgrade mesa package or install libva-mesa-driver or mesa-vdpau or remove my user profile.xml file, but it has no effect…

seth · 2022-04-05 22:32:37

segmentation fault: (core dumped)

https://wiki.archlinux.org/title/Core_d … _core_dump

alexela · 2022-04-06 07:27:18

Ok, then i watch the info for one of these core dump, but cant tell nothing of it. Do you want me to paste it somewhere ?

Thanks,
Alex

seth · 2022-04-06 07:30:26

If you want a comment on it, that's certainly a necessary precursor.

alexela · 2022-04-06 11:31:19

Here it is : https://pastebin.com/9H7R4PRY

Thanks for watching,
Alex

zaxdan69 · 2022-04-06 11:51:57

I have the same problem and is caused by python upgrade. The latest version in which kodi works fine is 3.10.2. It crashes with mentioned error with python 3.10.3 and 3.10.4.

alexela · 2022-04-06 12:07:12

I downgraded to python-3.10.2-1 and still have the issue.

zaxdan69 · 2022-04-06 12:23:40

You have right. I also had it after downgrade to 3.10.2, and I found that I needed to delete everything inside ~/.kodi/temp/archive_cache directory also.

MCMic · 2022-04-06 12:27:27

Downgrading python and/or kodi does not seem to fix the crash for me. And ~/.kodi/temp/archive_cache is empty.

seth · 2022-04-06 12:29:46

                #2  0x000055ab327d7301 _Z15LogGraphicsInfov (kodi.bin + 0xdfd301)
                #3  0x000055ab324031ba _ZN15CRenderSystemGL16InitRenderSystemEv (kodi.bin + 0xa291ba)

glxinfo -B
vulkaninfo
eglinfo

TheSgtBilko · 2022-04-06 13:06:55

Seems like there are several not related issues (at least for me):
- Kodi crashes randomly using youtube addon after upgrade from python 3.10.1
- Kodi crashes immediately on startup with mesa (and lib32-mesa) v22.0.0-1 and above, works fine downgrading to v21.3.7-2

Maybe we need a rebuild of kodi?

V1del · 2022-04-06 13:27:51

You need to switch to mesa-amber if you have a old GPU that isn't supported anymore by the current iris or crocus drivers.

alexela · 2022-04-06 15:51:54

So i downgraded python, and tried both mesa-amber and mesa 21.3.7-2, but it still doesnot work. If i downgrade kodi to 19.3-2 then it complains that libnfs.so.13 doesnot exist and for newer version it is always the same crash involving some core dump…

V1del · 2022-04-06 15:53:29

Please post the requested output in #11 and information on whether the coredump changed.

MCMic · 2022-04-06 15:57:08

For me downgrading mesa to v21.3.7-2 and rebooting fixes the problem.
Switching to mesa-amber does not work, after reboot kwin fails to start, I have some windows appearing over my terminal the desktop does not load correctly.

alexela · 2022-04-06 16:27:00

I have right now only partial info cause i'm logged in ssh. Here is the result of eglinfo :

EGL client extensions string:
EGL_EXT_device_base EGL_EXT_device_enumeration EGL_EXT_device_query
EGL_EXT_platform_base EGL_KHR_client_get_all_proc_addresses
EGL_EXT_client_extensions EGL_KHR_debug EGL_EXT_platform_device
EGL_EXT_platform_wayland EGL_KHR_platform_wayland
EGL_EXT_platform_x11 EGL_KHR_platform_x11 EGL_MESA_platform_xcb
EGL_MESA_platform_gbm EGL_KHR_platform_gbm
EGL_MESA_platform_surfaceless

GBM platform:
EGL API version: 1.4
EGL vendor string: Mesa Project
EGL version string: 1.4
EGL client APIs: OpenGL OpenGL_ES
EGL extensions string:
EGL_ANDROID_blob_cache EGL_ANDROID_native_fence_sync
EGL_EXT_buffer_age EGL_EXT_create_context_robustness
EGL_EXT_image_dma_buf_import EGL_EXT_image_dma_buf_import_modifiers
EGL_KHR_config_attribs EGL_KHR_create_context
EGL_KHR_create_context_no_error EGL_KHR_fence_sync
EGL_KHR_get_all_proc_addresses EGL_KHR_gl_colorspace
EGL_KHR_gl_renderbuffer_image EGL_KHR_gl_texture_2D_image
EGL_KHR_gl_texture_3D_image EGL_KHR_gl_texture_cubemap_image
EGL_KHR_image EGL_KHR_image_base EGL_KHR_image_pixmap
EGL_KHR_no_config_context EGL_KHR_reusable_sync
EGL_KHR_surfaceless_context EGL_EXT_pixel_format_float
EGL_KHR_wait_sync EGL_MESA_configless_context EGL_MESA_drm_image
EGL_MESA_image_dma_buf_export EGL_MESA_query_driver
EGL_WL_bind_wayland_display
Configurations:
bf lv colorbuffer dp st ms vis cav bi renderable supported
id sz l r g b a th cl ns b id eat nd gl es es2 vg surfaces
---------------------------------------------------------------------
0x01 16 0 5 6 5 0 0 0 0 0 0x36314752-- y y y win
0x02 16 0 5 6 5 0 24 8 0 0 0x36314752-- y y y win
0x03 32 0 8 8 8 8 0 0 0 0 0x34325241-- y y y win
0x04 32 0 8 8 8 8 24 8 0 0 0x34325241-- y y y win
0x05 24 0 8 8 8 0 0 0 0 0 0x34325258-- y y y win
0x06 24 0 8 8 8 0 24 8 0 0 0x34325258-- y y y win
0x07 64 0 16 16 16 16 0 0 0 0 0x48344241-- y y y win
0x08 64 0 16 16 16 16 24 8 0 0 0x48344241-- y y y win
0x09 48 0 16 16 16 0 0 0 0 0 0x48344258-- y y y win
0x0a 48 0 16 16 16 0 24 8 0 0 0x48344258-- y y y win
0x0b 16 0 5 6 5 0 0 0 4 1 0x36314752-- y y y win
0x0c 16 0 5 6 5 0 0 0 8 1 0x36314752-- y y y win
0x0d 16 0 5 6 5 0 24 8 4 1 0x36314752-- y y y win
0x0e 16 0 5 6 5 0 24 8 8 1 0x36314752-- y y y win
0x0f 32 0 8 8 8 8 0 0 4 1 0x34325241-- y y y win
0x10 32 0 8 8 8 8 0 0 8 1 0x34325241-- y y y win
0x11 32 0 8 8 8 8 24 8 4 1 0x34325241-- y y y win
0x12 32 0 8 8 8 8 24 8 8 1 0x34325241-- y y y win
0x13 24 0 8 8 8 0 0 0 4 1 0x34325258-- y y y win
0x14 24 0 8 8 8 0 0 0 8 1 0x34325258-- y y y win
0x15 24 0 8 8 8 0 24 8 4 1 0x34325258-- y y y win
0x16 24 0 8 8 8 0 24 8 8 1 0x34325258-- y y y win
0x17 64 0 16 16 16 16 0 0 4 1 0x48344241-- y y y win
0x18 64 0 16 16 16 16 0 0 8 1 0x48344241-- y y y win
0x19 64 0 16 16 16 16 24 8 4 1 0x48344241-- y y y win
0x1a 64 0 16 16 16 16 24 8 8 1 0x48344241-- y y y win
0x1b 48 0 16 16 16 0 0 0 4 1 0x48344258-- y y y win
0x1c 48 0 16 16 16 0 0 0 8 1 0x48344258-- y y y win
0x1d 48 0 16 16 16 0 24 8 4 1 0x48344258-- y y y win
0x1e 48 0 16 16 16 0 24 8 8 1 0x48344258-- y y y win

Wayland platform:
eglinfo: eglInitialize failed

X11 platform:
eglinfo: eglInitialize failed

Device platform:
eglinfo: eglInitialize failed

seth · 2022-04-06 20:08:58

Please use code tags, https://bbs.archlinux.org/help.php#bbcode - and we'll need the info from the actual environment where you launch kodi.

kevku · 2022-04-07 18:41:19

I needed compile with vdpau=OFF and python 3.8 to make kodi work.

TheSgtBilko · 2022-04-08 12:42:48

V1del wrote:

You need to switch to mesa-amber if you have a old GPU that isn't supported anymore by the current iris or crocus drivers.

Replacing mesa with mesa-amber worked fine for fixing instant crash when starting kodi, thx V1del!
(gen7: Haswell - Core i5-4250U - HD Graphics 5000)

Last edited by TheSgtBilko (2022-04-08 12:43:40)

renegat · 2022-04-09 13:02:55

I'am struggeling with the same issue:

Since update mesa 22 kodi does not start (don't know if related but vainfo also crashes with 'unknown error' when mesa 22 is installed.)
glxgears works fine.

Downgrading mesa to 21.3.7 makes everything work again, using mesa-amber causes weird graphics issues with LXQt (like shadows, artifacts, relicts of closed windows...)

As far as I understood the Intel 4.Gen (Hasswell) should still be supported by mesa 22 and users of this should not have to use tmesa-amber stub.

Edit: Info about graphics-card

00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 09)
Intel HD4000 on NUC D34010WYK

The same issue occurs also with Gen 7. KabyLake HD610 and there is a bug report about this issue:

FS#74276

Last edited by renegat (2022-04-09 13:09:49)

seth · 2022-04-09 13:16:19

1. it's not a "stub"
2. there's a guy w/ a gen7 chip right above you …
3. "HD4000" is not an "Iris Graphics" chip, https://en.wikipedia.org/wiki/Intel_Gra … gy#Haswell
4. check your xorg log, there's likely an error about a missing /usr/lib/dri/i965_dri.so

=> you need mesa-amber and yeah, vainfo *likely* fails because of that as well. glxgears *probably* runs on the software rasterizer and glxinfo would reveal that.

MCMic · 2022-04-09 14:10:19

I have:
produit: 4th Gen Core Processor Integrated Graphics Controller

Is there any documentation about this mesa-amber? I see nothing in archwiki or blog explaining the change in newer mesa versions.
If I install mesa-amber graphics fails at boot.

seth · 2022-04-09 14:19:07

https://lists.freedesktop.org/archives/ … 24984.html
https://www.phoronix.com/scan.php?page= … assic-Main
https://www.phoronix.com/scan.php?page= … ic-Retired

As for "graphics fails at boot", you'll have to elaborate on this or produce a system journal covering the failure.

Edit: most peoples problem will be that the crocus driver is a relatively new effort to backport iris to i965.
https://gitlab.freedesktop.org/mesa/mesa/-/issues/6229 has an interesting finding in https://gitlab.freedesktop.org/mesa/mes … te_1328555

a less-bad workaround: export LD_PRELOAD=/usr/lib/dri/crocus_dri.so. then glibc will use static TLS, bypassing the issue.

Last edited by seth (2022-04-09 14:35:16)

alexela · 2022-04-09 18:53:45

Sorry for the delay. Here are the requested output :

eglinfo : https://pastebin.com/J2QJXNyK
glxinfo : https://pastebin.com/06B1ru5y
vulkaninfo : https://pastebin.com/4swRSvJp

I did un upgrade and install vulkan-tools and reboot just before. I checked that kodi still did not work.

Thanks for your help,
Alex

Arch Linux

#1 2022-04-05 19:31:26

kodi segmentation fault [solved]

#2 2022-04-05 19:44:23

Re: kodi segmentation fault [solved]

#3 2022-04-05 22:32:37

Re: kodi segmentation fault [solved]

#4 2022-04-06 07:27:18

Re: kodi segmentation fault [solved]

#5 2022-04-06 07:30:26

Re: kodi segmentation fault [solved]

#6 2022-04-06 11:31:19

Re: kodi segmentation fault [solved]

#7 2022-04-06 11:51:57

Re: kodi segmentation fault [solved]

#8 2022-04-06 12:07:12

Re: kodi segmentation fault [solved]

#9 2022-04-06 12:23:40

Re: kodi segmentation fault [solved]

#10 2022-04-06 12:27:27

Re: kodi segmentation fault [solved]

#11 2022-04-06 12:29:46

Re: kodi segmentation fault [solved]

#12 2022-04-06 13:06:55

Re: kodi segmentation fault [solved]

#13 2022-04-06 13:27:51

Re: kodi segmentation fault [solved]

#14 2022-04-06 15:51:54

Re: kodi segmentation fault [solved]

#15 2022-04-06 15:53:29

Re: kodi segmentation fault [solved]

#16 2022-04-06 15:57:08

Re: kodi segmentation fault [solved]

#17 2022-04-06 16:27:00

Re: kodi segmentation fault [solved]

#18 2022-04-06 20:08:58

Re: kodi segmentation fault [solved]

#19 2022-04-07 18:41:19

Re: kodi segmentation fault [solved]

#20 2022-04-08 12:42:48

Re: kodi segmentation fault [solved]

#21 2022-04-09 13:02:55

Re: kodi segmentation fault [solved]

#22 2022-04-09 13:16:19

Re: kodi segmentation fault [solved]

#23 2022-04-09 14:10:19

Re: kodi segmentation fault [solved]

#24 2022-04-09 14:19:07

Re: kodi segmentation fault [solved]

#25 2022-04-09 18:53:45

Re: kodi segmentation fault [solved]

Board footer