There was an update to Mesa over in the Ubuntu-X-Swat PPA today (by
which I mean the “Updates” one), from 19.0.2-1ubuntu1.1~18.04.1 to
19.0.8-0ubuntu0~18.04.1. …Sadly, as I discovered—after installing the
updates, then restarting and trying Kodi again—this bug is still present
and still works exactly the same.
(While I’m here, does anyone know how I would file a bug with the
nvidia-340 package? I mean, I don’t know how much we can do about that
driver, given its proprietary nature, but I want to try, at least. I
just want one of my graphics drivers working so I can use my media
player again… (sigh))
** Also affects: mesa (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/1836979
Title:
Kodi crashes with “nouveau_vp3_video_buffer_create: Assertion
`templat->interlaced' failed”
Status in mesa package in Ubuntu:
New
Status in xserver-xorg-video-nouveau package in Ubuntu:
New
Bug description:
I’m not exactly sure if this belongs here, libva, mesa, or upstream
somewhere. But, it doesn’t seem to be a Kodi bug, buggy is that
program is.
Kodi has worked just fine on my system, as recently as July 6th of
this year, but yesterday (July 16) I tried Kodi again: I got a blank
screen and a pause for a few moments, followed by an unceremonious
crash-to-desktop. This happens every time I start Kodi, now.
If I run it through the command-line, I get this:
libva info: VA-API version 1.1.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/nouveau_drv_video.so
libva info: Found init function __vaDriverInit_1_1
libva info: va_openDriver() returns 0
kodi-x11: ../src/gallium/drivers/nouveau/nouveau_vp3_video.c:91:
nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed.
Aborted (core dumped)
I’ve been using the same version of Kodi (“18.3 Git:20190621-89472b7”,
package version 2:18.3+git20190621.1610-final-0bionic, from the Team-
XBMC PPA) since its release in June, but in between July 7th and 16th,
I did upgrade Nouveau:
2019-07-07 06:50:36 upgrade libdrm-nouveau2:amd64 2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1
2019-07-07 06:50:36 status half-configured libdrm-nouveau2:amd64
2.4.95-1~18.04.1
2019-07-07 06:50:36 status unpacked libdrm-nouveau2:amd64 2.4.95-1~18.04.1
2019-07-07 06:50:36 status half-configured libdrm-nouveau2:i386
2.4.95-1~18.04.1
2019-07-07 06:50:36 status half-installed libdrm-nouveau2:amd64
2.4.95-1~18.04.1
2019-07-07 06:50:37 status half-installed libdrm-nouveau2:amd64
2.4.95-1~18.04.1
2019-07-07 06:50:37 status unpacked libdrm-nouveau2:amd64
2.4.97-1ubuntu1~18.04.1
2019-07-07 06:50:37 status unpacked libdrm-nouveau2:amd64
2.4.97-1ubuntu1~18.04.1
2019-07-07 06:50:37 upgrade libdrm-nouveau2:i386 2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1
2019-07-07 06:50:37 status half-configured libdrm-nouveau2:i386
2.4.95-1~18.04.1
2019-07-07 06:50:37 status unpacked libdrm-nouveau2:i386 2.4.95-1~18.04.1
2019-07-07 06:50:37 status half-installed libdrm-nouveau2:i386
2.4.95-1~18.04.1
2019-07-07 06:50:38 status half-installed libdrm-nouveau2:i386
2.4.95-1~18.04.1
2019-07-07 06:50:38 status unpacked libdrm-nouveau2:i386
2.4.97-1ubuntu1~18.04.1
2019-07-07 06:50:38 status unpacked libdrm-nouveau2:i386
2.4.97-1ubuntu1~18.04.1
2019-07-07 06:51:44 configure libdrm-nouveau2:amd64 2.4.97-ubuntu1~18.04.1
<none>
2019-07-07 06:51:44 status unpacked libdrm-nouveau2:amd64
2.4.97-1ubuntu1~18.04.1
2019-07-07 06:51:44 status half-configured libdrm-nouveau2:amd64
2.4.97-1ubuntu1~18.04.1
2019-07-07 06:51:44 status installed libdrm-nouveau2:amd64
2.4.97-1ubuntu1~18.04.1
2019-07-07 06:51:44 configure libdrm-nouveau2:i386 2.4.97-1ubuntu1~18.04.1
<none>
2019-07-07 06:51:44 status unpacked libdrm-nouveau2:i386
2.4.97-1ubuntu1~18.04.1
2019-07-07 06:51:44 status half-configured libdrm-nouveau2:i386
2.4.97-1ubuntu1~18.04.1
2019-07-07 06:51:44 status installed libdrm-nouveau2:i386
2.4.97-1ubuntu1~18.04.1
(Another reason I’m guessing this is a Nouveau problem is because I
later tried switching to the official NVidia drivers, didn’t get this
bug, and then later encountered a distinct yet worse bug that locks up
the whole system. So, now I’m back to using Nouveau.)
I tried looking in Xorg.0.log:
[ 17185.557] (II) NOUVEAU(0): EDID vendor "SEC", prod id 12620
[ 17185.557] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[ 17185.558] (II) NOUVEAU(0): Modeline "1366x768"x0.0 72.33 1366 1414 1446
1526 768 770 775 790 -hsync -vsync (47.4 kHz eP)
…that’s all that appears in the log when I try to load Kodi and a
crash happens.
I’m using Ubuntu MATE 18.04.2 LTS 64-bit on a Compaq Presario CQ60; if
you need more information, I’ve attached a hardinfo report, too. I
hope this bug can get fixed, soon. Thanks!
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836979/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
