From: anarchomoh <anarchomoh@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Kodi Crash - Segmentation fault (core dumped)
Date: Thu, 14 Apr 2022 12:38:02 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36688@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1238 bytes --]
New issue by anarchomoh on void-packages repository
https://github.com/void-linux/void-packages/issues/36688
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname:
Void 5.15.32_1 x86_64 GenuineIntel uptodate rrrrrmmdnFFFFFFF
* package:
kodi-19.4_1
### Expected behavior
Play media content normally
### Actual behavior
Crashes with below error:
libva info: VA-API version 1.14.0
libva info: Trying to open /usr/lib64/dri/r600_drv_video.so
libva info: Found init function __vaDriverInit_1_13
libva info: va_openDriver() returns 0
Segmentation fault (core dumped)
### Steps to reproduce the behavior
Enter any installed Addonn of Kodi
Flatpak Kodi works with the below output on the same system:
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/r600_drv_video.so
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/intel-vaapi-driver/r600_drv_video.so
libva info: Trying to open /usr/lib/x86_64-linux-gnu/GL/lib/dri/r600_drv_video.so
libva info: Found init function __vaDriverInit_1_12
libva info: va_openDriver() returns 0
next reply other threads:[~2022-04-14 10:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-14 10:38 anarchomoh [this message]
2022-04-14 10:52 ` wael444
2022-04-14 10:52 ` wael444
2022-04-14 10:57 ` anarchomoh
2022-05-01 20:02 ` Anachron
2022-05-06 4:13 ` anarchomoh
2022-08-07 2:14 ` github-actions
2022-08-21 2:16 ` [ISSUE] [CLOSED] " github-actions
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36688@inbox.vuxu.org \
--to=anarchomoh@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).