[Ubuntu-x-swat] [Bug 1837081] Re: xorg crashes on virgl with 3d enabled (Haswell on the host), ms_dri2_schedule_wait_msc
I have tried to follow the instructions, but not sure if I did it correctly. Does this link help? https://errors.ubuntu.com/oops/d2e06dde- a9d9-11e9-a2e9-fa163e6cac46 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1837081 Title: xorg crashes on virgl with 3d enabled (Haswell on the host), ms_dri2_schedule_wait_msc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1837081/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1835863] Re: Screens do not stay off when blanking
-- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1835863 Title: Screens do not stay off when blanking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1835863/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1837170] [NEW] Kodi package crash after the update of libdrm-amdgpu1
Public bug reported: Greetings, The last update of libdrm-amdgpu1 caused a bug on Kodi package, making it to crash after loading any video or reproduce a black image. Version: 2.4.97-1ubuntu1~18.04.12019-07-03 15:07:54 UTC libdrm (2.4.97-1ubuntu1~18.04.1) bionic; urgency=medium * Backport to bionic for 18.04.3 HWE stack update. (LP: #1824111) -- Timo Aaltonen Wed, 10 Apr 2019 13:54:06 +0300 Kodi gives this error: #3 0x7f47676c60aa in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f47676c5dd7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so Repeated several times #3 0x7f475ce2c5a6 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 #4 0x7f475ce2c425 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 Team-Kodi stated these errors are in relation to 'Not supported GPU drivers', when Kodi can't find these files. I've found the cause, and a temporary solution: This bug was caused after an update for the latest version of libdrm- amdgpu1 2.4.97-1ubuntu1~18.04.1 So I grabbed the previous version from https://mirror.transip.net/ubuntu/ubuntu/pool/main/libd/libdrm/ installed libdrm-amdgpu1_2.4.95-1~18.04.1_amd64.deb and now Kodi returns. I created a bug report, the problem affects multiple users. https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/1836828 We have a PointRelease coming soon, would we have time to fix this package? Thank you for your assistance. ** Affects: libdrm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1837170 Title: Kodi package crash after the update of libdrm-amdgpu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1837170/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1835863] Re: Screens do not stay off when blanking
** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1835863 Title: Screens do not stay off when blanking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1835863/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1835863] Re: Screens do not stay off when blanking
Why is this still marked incomplete? What other info is necessary? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1835863 Title: Screens do not stay off when blanking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1835863/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1837081] Re: xorg crashes on virgl with 3d enabled (Haswell on the host), ms_dri2_schedule_wait_msc
To confirm we have the right stack trace, please follow these instructions: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1837081 Title: xorg crashes on virgl with 3d enabled (Haswell on the host), ms_dri2_schedule_wait_msc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1837081/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1836772] Re: Xorg crash on 3d-enabled virgl (Haswell host)
** Changed in: mesa (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1836772 Title: Xorg crash on 3d-enabled virgl (Haswell host) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836772/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1836805] Re: screen frozen after reboot
Please go to step 2 in: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1836805 Title: screen frozen after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1836805/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1837087] Re: gnome-shell crashed with assertion failure ../src/gallium/drivers/radeonsi/si_state_viewport.c:239: si_emit_guardband: Assertion `left <= -1 && top <= -1 && right >=
** Summary changed: - /usr/bin/gnome-shell:gnome-shell: ../src/gallium/drivers/radeonsi/si_state_viewport.c:239: si_emit_guardband: Assertion `left <= -1 && top <= -1 && right >= 1 && bottom >= 1' failed. + gnome-shell crashed with assertion failure ../src/gallium/drivers/radeonsi/si_state_viewport.c:239: si_emit_guardband: Assertion `left <= -1 && top <= -1 && right >= 1 && bottom >= 1' failed. ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags added: radeon -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1837087 Title: gnome-shell crashed with assertion failure ../src/gallium/drivers/radeonsi/si_state_viewport.c:239: si_emit_guardband: Assertion `left <= -1 && top <= -1 && right >= 1 && bottom >= 1' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1837087/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [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-X, 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” To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836979/+subscriptions ___ Mailing list:
[Ubuntu-x-swat] [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-X, 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” To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836979/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [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-X, 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” To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836979/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1836805] Re: screen frozen after reboot
Generated the prevboot.txt (see attached). I did not find any file related to wayland crash in /var/crash. I did find though an xorg crash file dated from this morning. I sent it through ubuntu-bug though I was not asked a bug number (I am not sure it worked). I do not really understand what happened this morning as the xorg config ended up working. I don't know if this new fact may help solving the issue or is rather disturbing... ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1836805/+attachment/5277936/+files/prevboot.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1836805 Title: screen frozen after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1836805/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1837081] Re: xorg crashes on virgl with 3d enabled (Haswell on the host), ms_dri2_schedule_wait_msc
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1837081 Title: xorg crashes on virgl with 3d enabled (Haswell on the host), ms_dri2_schedule_wait_msc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1837081/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1825499] Re: Touchpad vertical sensitivity is much higher than horizontal sensitivity [HP Pavilion g6]
# 20: Yes, that's it. Thank you! The touchpad works perfectly again. I have changed the following lines in the file /lib/udev/hwdb.d/60-evdev.hwdb: # HP Pavilion g6 evdev: name: SynPS / 2 Synaptics TouchPad: dmi: * svnHewlett-Packard: pnHPPaviliong6 * EVDEV_ABS_00 = 1284: 5696: 88 EVDEV_ABS_01 = 1287: 4838: 39 EVDEV_ABS_35 = 1284: 5696: 88 EVDEV_ABS_36 = 1287: 4838: 39 With the following: # HP Pavilion g6 #evdev: name: SynPS / 2 Synaptics TouchPad: dmi: * svnHewlett-Packard: pnHPPaviliong6 * # EVDEV_ABS_00 = 1284: 5696: 88 # EVDEV_ABS_01 = 1287: 4838: 39 # EVDEV_ABS_35 = 1284: 5696: 88 # EVDEV_ABS_36 = 1287: 4838: 39 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1825499 Title: Touchpad vertical sensitivity is much higher than horizontal sensitivity [HP Pavilion g6] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1825499/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1835922] Re: missing gl* symbols in version 19.0.2
Tested 19.0.8 from ppa:ubuntu-x-swat/updates locally and the fix works. Any idea when the fix will be available in the ubuntu repo for Bionic release? I haven't found any way to install from ppa on Heroku. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1835922 Title: missing gl* symbols in version 19.0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1835922/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1837081] Re: xorg crashes on virgl with 3d enabled (Haswell on the host), ms_dri2_schedule_wait_msc
https://bugzilla.redhat.com/show_bug.cgi?id=1652274 is a duplicate ** Bug watch added: Red Hat Bugzilla #1652274 https://bugzilla.redhat.com/show_bug.cgi?id=1652274 ** Also affects: xorg (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=1652274 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1837081 Title: xorg crashes on virgl with 3d enabled (Haswell on the host), ms_dri2_schedule_wait_msc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1837081/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1837081] [NEW] xorg crashes on virgl with 3d enabled (Haswell on the host), ms_dri2_schedule_wait_msc
Public bug reported: I have recently files this bug: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836772 and decided to test if it affects Ubuntu 19.04. Just to remind you, this was about xorg crashing in a virtual machine that uses virtio VGA with virgl enabled. The host is Arch Linux, the CPU is Intel Core i7 4770S (Haswell). Well, xorg crashes on 19.04, too, but with a different backtrace, and adding ppa:ubuntu-x-swat/updates does not help. So I believe this is a separate bug. Disabling virgl on qemu command line helps, but I would rather have it enabled. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' Date: Thu Jul 18 21:09:46 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Red Hat, Inc. Virtio GPU [1af4:1050] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. Virtio GPU [1af4:1100] Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic root=UUID=0617cd90-66d8-4848-8ef8-fdf7fc919a93 ro splash quiet vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-20181126_142135-anatol dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.0 dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-20181126_142135-anatol:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.0:cvnQEMU:ct1:cvrpc-i440fx-4.0: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.0 dmi.sys.vendor: QEMU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~19.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco third-party-packages ubuntu -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1837081 Title: xorg crashes on virgl with 3d enabled (Haswell on the host), ms_dri2_schedule_wait_msc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1837081/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1825499] Re: Touchpad vertical sensitivity is much higher than horizontal sensitivity [HP Pavilion g6]
Maybe this? https://github.com/systemd/systemd/pull/10008 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1825499 Title: Touchpad vertical sensitivity is much higher than horizontal sensitivity [HP Pavilion g6] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1825499/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1836721] Re: Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04
** Changed in: mesa (Ubuntu Bionic) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1836721 Title: Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836721/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1835622] Re: Cannot start desktop session with compositor enabled
** Changed in: xfwm4 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1835622 Title: Cannot start desktop session with compositor enabled To manage notifications about this bug go to: https://bugs.launchpad.net/xfwm4/+bug/1835622/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1835622] Re: Cannot start desktop session with compositor enabled
well, perhaps not a dupe but would be nice to know if the new upstream bugfix version helps -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1835622 Title: Cannot start desktop session with compositor enabled To manage notifications about this bug go to: https://bugs.launchpad.net/xfwm4/+bug/1835622/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1835622] Re: Cannot start desktop session with compositor enabled
please test ppa:ubuntu-x-swat/updates seems to be a duplicate of bug 1836721 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1835622 Title: Cannot start desktop session with compositor enabled To manage notifications about this bug go to: https://bugs.launchpad.net/xfwm4/+bug/1835622/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1836630] Re: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend
Actually, the calls are not exposed, so, maybe we should rely on the kernel version instead. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1836630 Title: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1836630/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1836630] Re: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend
I can apply the change depending on the availability of the new nvme_* functions, so that kernels which don't include the two commits will not be affected. I am going to notify NVIDIA too. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1836630 Title: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1836630/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1836721] Re: Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04
cool, the fix is on the SRU queue now, waiting for review -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1836721 Title: Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836721/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1836721] Re: Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04
I have just updated from ppa:ubuntu-x-swat/updates, now everything is fine on i386 Ubuntu 18.04 ~# apt-cache policy libgl1-mesa-glx libgl1-mesa-glx: Installed: 19.0.8-0ubuntu0~18.04.1 Candidate: 19.0.8-0ubuntu0~18.04.1 Version table: *** 19.0.8-0ubuntu0~18.04.1 500 500 http://ppa.launchpad.net/ubuntu-x-swat/updates/ubuntu bionic/main i386 Packages 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1836721 Title: Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836721/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1836772] Re: Xorg crash on 3d-enabled virgl (Haswell host)
excellent, that version is on the SRU queue already, waiting for review ** Changed in: xorg-server (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1836772 Title: Xorg crash on 3d-enabled virgl (Haswell host) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836772/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1836772] Re: Xorg crash on 3d-enabled virgl (Haswell host)
It works. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1836772 Title: Xorg crash on 3d-enabled virgl (Haswell host) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836772/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1835922] Re: missing gl* symbols in version 19.0.2
please test 19.0.8 from ppa:ubuntu-x-swat/updates once it has built -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1835922 Title: missing gl* symbols in version 19.0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1835922/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1836721] Re: Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04
please test 19.0.8 from ppa:ubuntu-x-swat/updates once it has built -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1836721 Title: Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836721/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1836772] Re: Xorg crash on 3d-enabled virgl (Haswell host)
please test 19.0.8 from ppa:ubuntu-x-swat/updates ** Changed in: mesa (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1836772 Title: Xorg crash on 3d-enabled virgl (Haswell host) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836772/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1815172] Re: Black screen on skylake after 18.0 => 18.2 update
** Changed in: linux (Ubuntu Cosmic) Status: New => Won't Fix ** Summary changed: - Black screen on skylake after 18.0 => 18.2 update + [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1815172 Title: [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815172/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1836721] Re: Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04
okay, adding the revert again.. this should've been fixed in the kernel after 18.04.2 but that didn't happen since we don't support 32bit installs in newer releases, bionic is the only one that will get this ** Also affects: mesa (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: mesa (Ubuntu Bionic) Status: New => In Progress ** Changed in: mesa (Ubuntu Bionic) Assignee: (unassigned) => Timo Aaltonen (tjaalton) ** Changed in: mesa (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1836721 Title: Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836721/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1835922] Re: missing gl* symbols in version 19.0.2
fixed upstream in 19.0.5 ** Bug watch added: freedesktop.org Bugzilla #109659 https://bugs.freedesktop.org/show_bug.cgi?id=109659 ** Also affects: mesa via https://bugs.freedesktop.org/show_bug.cgi?id=109659 Importance: Unknown Status: Unknown ** Also affects: mesa (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: mesa (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1835922 Title: missing gl* symbols in version 19.0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1835922/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1836805] Re: screen frozen after reboot
Thanks. We will need to see more of the problem than the short extract provided so far: ==journalctl_extract.txt juil. 16 21:47:45 portable-ldlc gnome-shell[1165]: Failed to apply DRM plane transform 0: Permission non accordée juil. 16 21:47:47 portable-ldlc gnome-shell[1165]: WL: error in client communication (pid 1165) juil. 16 21:47:47 portable-ldlc org.gnome.Shell.desktop[1165]: (EE) juil. 16 21:47:47 portable-ldlc org.gnome.Shell.desktop[1165]: Fatal server error: juil. 16 21:47:47 portable-ldlc org.gnome.Shell.desktop[1165]: (EE) wl_drm@4: error 0: authenicate failed juil. 16 21:47:47 portable-ldlc org.gnome.Shell.desktop[1165]: (EE) juil. 16 21:47:48 portable-ldlc systemd[1]: systemd-hostnamed.service: Succeeded. juil. 16 21:47:50 portable-ldlc gnome-shell[1165]: X Wayland crashed; exiting ... Please reintroduce the bug and then collect the whole log from journalctl. If the bug has occurred during the current boot then run: journalctl -b0 > curboot.txt Or if the problem occurred during the previous boot then run: journalctl -b-1 > prevboot.txt and attach the resulting file. Also, since "X Wayland crashed", please follow these instructions to help us track that down: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete ** No longer affects: gdm3 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1836805 Title: screen frozen after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1836805/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
