[Touch-packages] [Bug 1836979] Re: Kodi crashes with “nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed”
** Description changed: - 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. + Buggy as Kodi is, this seems to be a problem specifically with mesa-va- + drivers. 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 - 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 - 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.) + XBMC PPA) since its release in June, but in between July 6th and 16th, I + did upgrade the Mesa packages, from 18.2.8-0ubuntu0~18.04.2 + 19.0.2-1ubuntu1.1~18.04.1. If I downgrade the “mesa-va-drivers” package + to 18.0.0~rc5-1ubuntu1 (the version in the base, non-updates Bionic + repository), however, Kodi works again, without even requiring me to + restart my machine. So, this is likely a problem with “mesa-va-drivers”. 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! ** No longer affects: xserver-xorg-video-nouveau (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa 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 Bug description: Buggy as Kodi is, this seems to be a problem specifically with mesa- va-drivers. Kodi has worked just
[Touch-packages] [Bug 1836979] Re: Kodi crashes with “nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed”
Sweet mother of the Muses, I just downgraded the mesa-va-drivers package to 18.0.0~rc5-1ubuntu1 (since that’s the one from the non-updates Bionic repository) and Kodi works again! Then, this is a problem specifically with the mesa-va-drivers package. I’ll have to update the description accordingly. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa 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 Bug description: Buggy as Kodi is, this seems to be a problem specifically with mesa- va-drivers. 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 6th and 16th, I did upgrade the Mesa packages, from 18.2.8-0ubuntu0~18.04.2 19.0.2-1ubuntu1.1~18.04.1. If I downgrade the “mesa-va-drivers” package to 18.0.0~rc5-1ubuntu1 (the version in the base, non-updates Bionic repository), however, Kodi works again, without even requiring me to restart my machine. So, this is likely a problem with “mesa-va- drivers”. 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836979] Re: Kodi crashes with “nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed”
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 Ubuntu Touch seeded packages, which is subscribed to mesa 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 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 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,
[Touch-packages] [Bug 187963] Re: pulseaudio[...]: sap.c: sendmsg() failed: Invalid argument
I am getting this bug with PulseAudio 11.1 in Ubuntu 18.04 LTS. ** Changed in: pulseaudio (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/187963 Title: pulseaudio[...]: sap.c: sendmsg() failed: Invalid argument Status in pulseaudio package in Ubuntu: Confirmed Bug description: Binary package hint: pulseaudio DISTRIB_RELEASE=8.04 DISTRIB_CODENAME=hardy DISTRIB_DESCRIPTION="Ubuntu hardy (development branch)" pulseaudio0.9.9-1ubuntu1 logcheck message up to 400kB every hour: ... Jan 31 09:12:38 bronto pulseaudio[19393]: sap.c: sendmsg() failed: Invalid argument Jan 31 09:12:43 bronto pulseaudio[19393]: sap.c: sendmsg() failed: Invalid argument Jan 31 09:12:48 bronto pulseaudio[19393]: sap.c: sendmsg() failed: Invalid argument Jan 31 09:12:53 bronto pulseaudio[19393]: sap.c: sendmsg() failed: Invalid argument Jan 31 09:12:59 bronto pulseaudio[19393]: sap.c: sendmsg() failed: Invalid argument Jan 31 09:13:04 bronto pulseaudio[19393]: sap.c: sendmsg() failed: Invalid argument Jan 31 09:13:09 bronto pulseaudio[19393]: sap.c: sendmsg() failed: Invalid argument Jan 31 09:13:14 bronto pulseaudio[19393]: sap.c: sendmsg() failed: Invalid argument Jan 31 09:13:19 bronto pulseaudio[19393]: sap.c: sendmsg() failed: Invalid argument Jan 31 09:13:24 bronto pulseaudio[19393]: sap.c: sendmsg() failed: Invalid argument Jan 31 09:13:29 bronto pulseaudio[19393]: sap.c: sendmsg() failed: Invalid argument Jan 31 09:13:34 bronto pulseaudio[19393]: sap.c: sendmsg() failed: Invalid argument ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/187963/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1721955] Re: Human, Human-Clearlooks and other themes have incorrect gray window title color
My hunch is that this has to do with how the Human themes have theme definitions for GTK2 but not GTK3—other themes like this seem to be having similar problems, now. The best workaround I’ve found is this one: https://www.opendesktop.org/s/mate/p/1013593/ It took a little bit of fidgeting for me to get this to work correctly, and there are still some bugs, but someone has created workable new versions of the Human themes. Personally, I used the “Human Quarny Clearlooks” theme, by copying its folder (renaming it “Human-Quarny-Clearlooks”) into “~/.themes”, then copying the “metacity-1” folder from “Human Quarny” into “Human-Quarny- Clearlooks”, and updating the index.theme file to rename the theme “Human Quarny Clearlooks” and then specify the sub-themes (except for icon theme, which stays “Humanity”) as “Human-Quarny-Clearlooks” instead of just “Human”). …That was way too complicated, but just copying the theme folders into “~.themes” created four or so different “Human” themes in the “Appearance” theme selector, and I had a feeling that madness lied that way. Oh, and the most obvious bug I’ve found is that some applications (like Emacs and Geany) have a weird scrollbar issue where the scrollbar slider is drawn but never un-drawn, so if you slide it around pretty soon your whole scrollbar is orange. (I note this here as a precaution and to see if anyone else has the same problem—after all, I did install the theme in a rather wacky fashion) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1721955 Title: Human, Human-Clearlooks and other themes have incorrect gray window title color Status in community-themes package in Ubuntu: New Status in compiz package in Ubuntu: Confirmed Status in gtk+2.0 package in Ubuntu: New Status in gtk+3.0 package in Ubuntu: New Status in human-theme package in Ubuntu: Confirmed Status in marco package in Ubuntu: New Status in mate-themes package in Ubuntu: New Bug description: Steps to reproduce: 1. Install Ubuntu 17.10 MATE or 18.04 LTS MATE 2. Install Human theme from `human-theme` package 3. Select Human theme from `mate-control-center` Appearance Expected results: window title color is set to Ubuntu's orange (#FFBE6B) Actual results: window title color is set to different gray/silver color (#a5a5a2) Note: other themes are affected too. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: human-theme 0.39.2 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic i686 ApportVersion: 2.20.7-0ubuntu2 Architecture: i386 CurrentDesktop: MATE Date: Sat Oct 7 15:43:03 2017 InstallationDate: Installed on 2017-10-07 (0 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha i386 (20170925.1) PackageArchitecture: all SourcePackage: human-theme UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/community-themes/+bug/1721955/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
