I have a sense of deja vu about this but I am not sure if the problem is the same as I had in 2016. A lot has changed since then. Rather than try and explain I am showing the result of running kodi in the cli:-
alastair@localhost:~> kodi --debug
libva info: VA-API version 1.9.0
libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so
libva info: va_openDriver() returns -1
libva info: Trying to open /usr/lib64/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_8
failed to open /usr/lib64/dri/hybrid_drv_video.so
Not using hybrid_drv_video.so
libva info: va_openDriver() returns 0
failed to open /usr/lib64/dri/hybrid_drv_video.so
Not using hybrid_drv_video.so
Could not find platform independent libraries <prefix>
Could not find platform dependent libraries <exec_prefix>
Consider setting $PYTHONHOME to <prefix>:<exec_prefix>]
ImportError: No module named site
/usr/bin/kodi: line 219: 2682 Segmentation fault (core dumped) ${KODI_BINARY} $SAVED_ARGS
find: ‘/home/alastair/pCloudDrive/Crypto Folder’: Permission denied
Crash report available at /home/alastair/kodi_crashlog-20201205_231417.log
alastair@localhost:~>
I am showing this as there seems much missing in my setup including a possible problem with video drivers. Here is the installed setup:-
The obvious cause is your instance of kodi trying to open a file which does not exist. Output of kodi on my machine is:
karl@3400G:~> kodi
libva info: VA-API version 1.9.0
libva info: Trying to open /usr/lib64/dri/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_1_9
libva info: va_openDriver() returns 0
karl@3400G:~>
Make sure you are using a proper video driver. your inxi -G output suggests you need to install intel:
**3400G:~ #** zypper se -is intel
Loading repository data...
Reading installed packages...
S | Name | Type | Version | Arch | Repository
---+-----------------------+---------+--------------------------------+--------+-------------------------------------------
i | intel-vaapi-driver | package | 2.4.1-2.1 | x86_64 | Haupt-Repository (OSS)
i | kernel-firmware-intel | package | 20201120-343.1 | noarch | Kernel builds for branch master (standard)
i | libdrm_intel1 | package | 2.4.102-2.1 | x86_64 | Haupt-Repository (OSS)
i | libvulkan_intel | package | 20.2.3-268.1 | x86_64 | Haupt-Repository (OSS)
i | ucode-intel | package | 20201118-1.1 | x86_64 | Haupt-Repository (OSS)
i+ | xf86-video-intel | package | 2.99.917+git8674.25c9a2fcc-5.4 | x86_64 | Haupt-Repository (OSS)
**3400G:~ # **
Hi Karl,
Many thanks for your reply. Out of my depth as usual. I understand what you suggest but do not understand how I can have worked on this laptop for so long without this driver. Here is what I found from your command:-
alastair@localhost:~> sudo zypper se -is intel
[sudo] password for root:
Loading repository data...
Reading installed packages...
S | Name | Type | Version | Arch | Repository
--+-----------------------+---------+--------------+--------+----------------------
i | intel-vaapi-driver | package | 2.4.1-2.1 | x86_64 | Main Repository (OSS)
i | intel-vaapi-driver | package | 2.4.1-2.1 | x86_64 | openSUSE-20200502-0
i | kernel-firmware-intel | package | 20201120-1.1 | noarch | Main Repository (OSS)
i | kernel-firmware-intel | package | 20201120-1.1 | noarch | openSUSE-20200502-0
i | libdrm_intel1 | package | 2.4.102-2.1 | x86_64 | Main Repository (OSS)
i | libdrm_intel1 | package | 2.4.102-2.1 | x86_64 | openSUSE-20200502-0
i | ucode-intel | package | 20201118-1.1 | x86_64 | Main Repository (OSS)
i | ucode-intel | package | 20201118-1.1 | x86_64 | openSUSE-20200502-0
alastair@localhost:~>
What driver am I missing and will it mess up my existing drivers. I seem to recall some messages about the proprietary drivers which I accept when I update. Please could you elaborate when you have time.
Regards,
Budge
We definitely use the same Mesa-libva. But my kodi is asking for existing libraries while yours asks for non existing ones. This could be a configuration problem. To find out create a new user, login and invoke kodi.
What about : intel-hybrid-driver-1.0.2-5.3.x86_64 ?
Hi Karl, other than a senior moment when I forgot I was working from workstation on earlier post and not on the problem laptop, I had also forgotten what a pain it is setting up user so that I can actually use it. I now have a new user established and logged in and installed kodi. Running it from terminal I thought we had a solution but after a pause the application crashed again. I shall try and get it to you.
While looking at the Mesa driver installation I noted that I am using a possibly problematic driver. The message I get when I update is as follows:-
Mesa-dri-nouveau - Mesa DRI plug-in for 3D acceleration via Nouveau
WARNING: Nouveau DRI/3D driver selected.
This driver is considered experimental and is known to have issues with applications that use certain 3D acceleration features of modern NVIDIA hardware.
Symptoms include application crashes or lockups & crashes of your system’s graphical environment. Older Hardware and less demanding applications may work just fine and do benefit from the Hardware acceleration features this driver offers over software emulation.
Use of this driver is especially not recommended for use with the KDE Desktop Environment or Qt-based Applications.
The hardware vendor potentially offers alternative drivers.
Please click “Accept” if you accept the risks that may come with the installation of this driver. Choose “Cancel” to prevent installation of the driver and use software emulation instead.
I have always accepted this driver even though it has a health warning for KDE Desktop because I am using an old machine. Is it possible this is the cause?
Also should I try and install the missing intel driver?
Script /usr/bin/kodi invokes /usr/lib64/kodi/kodi-x11, which opens more than 300 files, many of them libraries. Thus any dubious package may crash the application. Removing all unneeded packages may fix the issue. From past experience I learned to search for unneeded packages and their remnants and expunging them reliably.
Basically the procedure consists of the following steps:
Minimize the lists of repos, clear all caches and dup until done.
Search for explicitly installed packages labelled with i+ by ‘zypper search’ and remove them when unneeded.
Check for unneeded and obsolete packages founnd by ‘zypper packages’ and remove them unless you know you need them
When installing new packages try --no-recommends. Installed recommended packages only if you definitely want to have them