Xwayland/Xorg crashed with SIGSEGV in st_renderbuffer_delete() from _mesa_reference_renderbuffer_() [often when running Skype or Slack snaps]

Bug #1754693 reported by Nathaniel W. Turner on 2018-03-09
196
This bug affects 49 people
Affects Status Importance Assigned to Milestone
mesa (Ubuntu)
Status tracked in Disco
Bionic
Undecided
Timo Aaltonen
Cosmic
Undecided
Timo Aaltonen
Disco
High
Timo Aaltonen
xorg-server (Ubuntu)
Status tracked in Disco
Bionic
Undecided
Timo Aaltonen
Cosmic
Undecided
Timo Aaltonen
Disco
High
Timo Aaltonen

Bug Description

https://errors.ubuntu.com/problem/01a80d2110a46f6b6d857ce814079646e695f4ca
https://errors.ubuntu.com/problem/a1e7fe67e388164abd73462b322cb79ac2773fae

---

Steps to reproduce:
Install 'slack' snap:

   sudo snap install slack --classic

Run slack:

   slack

Instacrash.

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: xwayland 2:1.19.6-1ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
.tmp.unity_support_test.0:

ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CompizPlugins: [core,composite,opengl,decor,mousepoll,grid,vpswitch,compiztoolbox,imgpng,gnomecompat,regex,move,place,resize,snap,unitymtgrabhandles,wall,animation,session,expo,workarounds,fade,ezoom,scale,unityshell]
CompositorRunning: None
CurrentDesktop: GNOME
Date: Fri Mar 9 10:31:06 2018
DistUpgraded: 2018-03-06 13:58:47,853 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py'
DistroCodename: bionic
DistroVariant: ubuntu
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/Xwayland
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534]
MachineType: ASUS All Series
ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 4 -listen 5 -displayfd 6
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=cd444f9d-672e-4d7b-aea8-657fff0ea1f4 ro quiet splash crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=1
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
 ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
 ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
 ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
 ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
Title: Xwayland crashed with SIGABRT
UpgradeStatus: Upgraded to bionic on 2018-03-06 (2 days ago)
UserGroups: adm admin audio cdrom chroot-admin dialout dip egbuild fax floppy fuse libvirt libvirtd lpadmin lxd plugdev sambashare sudo tape video wireshark
dmi.bios.date: 10/27/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2702
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z97-PRO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2702:bd10/27/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: ASUS MB
dmi.product.name: All Series
dmi.product.version: System Version
dmi.sys.vendor: ASUS
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.90-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Mon Oct 16 18:18:18 2017
xserver.configfile: default
xserver.devices:

xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:

xserver.version: 2:1.19.3-1ubuntu1.2

Nathaniel W. Turner (nturner) wrote :

StacktraceTop:
 st_renderbuffer_delete (ctx=0x7fa39154b040, rb=0x5599442b15f0) at ../../../src/mesa/state_tracker/st_cb_fbo.c:238
 _mesa_reference_renderbuffer_ (ptr=ptr@entry=0x5599442b12a8, rb=rb@entry=0x0) at ../../../src/mesa/main/renderbuffer.c:212
 _mesa_reference_renderbuffer (rb=0x0, ptr=0x5599442b12a8) at ../../../src/mesa/main/renderbuffer.h:72
 _mesa_free_framebuffer_data (fb=fb@entry=0x5599442b1160) at ../../../src/mesa/main/framebuffer.c:223
 _mesa_destroy_framebuffer (fb=0x5599442b1160) at ../../../src/mesa/main/framebuffer.c:199

Changed in xorg-server (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in xorg-server (Ubuntu):
status: New → Confirmed
information type: Private → Public
summary: - Xwayland crashed with SIGABRT
+ Xwayland crashed with SIGABRT in st_renderbuffer_delete()
Changed in xorg-server (Ubuntu):
importance: Medium → High
Timo Aaltonen (tjaalton) on 2018-04-16
affects: xorg-server (Ubuntu) → mesa (Ubuntu)
Will Cooke (willcooke) wrote :

On an up-to-date 18.04 machine today I can no longer reproduce this crash. Could someone else confirm the same?

Caleb Lloyd (caleblloyd) wrote :

I just ran updates on my 18.04 machine today also and can confirm Slack is working under Wayland

Here is my Slack Snap Version:

commands:
  - slack
snap-id: JUJH91Ved74jd4ZgJCpzMBtYbPOzTlsD
tracking: stable
refreshed: 2018-03-30T18:45:51-04:00
installed: 3.1.1 (6) 98MB classic

If someone can tell me how to print out the affected Wayland component version I can post that also.

Zygmunt Krynicki (zyga) wrote :
Download full text (3.5 KiB)

I can still reproduce this now on my T470 with fully up-to-date bionic (also tried the https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging PPA)

kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE)
kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) Backtrace:
kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 0: /usr/bin/Xwayland (xorg_backtrace+0x4d) [0x561ba663e6bd]
kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 1: /usr/bin/Xwayland (0x561ba6496000+0x1ac459) [0x561ba6642459]
kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7ff68662b000+0x12890) [0x7ff68663d890]
kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 3: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (0x7ff67fed8000+0x24e9e3) [0x7ff6801269e3]
kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (0x7ff67fed8000+0x1b3ed4) [0x7ff68008bed4]
kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (0x7ff67fed8000+0x144c6a) [0x7ff68001cc6a]
kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (0x7ff67fed8000+0x144cae) [0x7ff68001ccae]
kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 7: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (0x7ff67fed8000+0x144d1c) [0x7ff68001cd1c]
kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 8: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (0x7ff67fed8000+0xad4b2) [0x7ff67ff854b2]
kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 9: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (0x7ff67fed8000+0x25b6db) [0x7ff6801336db]
kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 10: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (0x7ff67fed8000+0x3e2ae5) [0x7ff6802baae5]
kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 11: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (0x7ff67fed8000+0x3e1a13) [0x7ff6802b9a13]
kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 12: /usr/bin/Xwayland (0x561ba6496000+0xc8989) [0x561ba655e989]
kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 13: /usr/bin/Xwayland (0x561ba6496000+0xc7975) [0x561ba655d975]
kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 14: /usr/bin/Xwayland (0x561ba6496000+0x1969f2) [0x561ba662c9f2]
kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 15: /usr/bin/Xwayland (0x561ba6496000+0xcc5f7) [0x561ba65625f7]
kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 16: /usr/bin/Xwayland (0x561ba6496000+0xc7c3c) [0x561ba655dc3c]
kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 17: /usr/bin/Xwayland (0x561ba6496000+0x171ec8) [0x561ba6607ec8]
kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 18: /usr/bin/Xwayland (0x561ba6496000+0x175f10) [0x561ba660bf10]
kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 19: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xe7) [0x7ff68625bb97]
kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 20: /usr/bin/Xwayland (_start+0x2a) [0x561ba64d0ada]
kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE)
kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) Segmentati...

Read more...

Daniel van Vugt (vanvugt) wrote :

Also tracking xorg-server, so people can find this bug more easily, and in case a fix is required in Xwayland directly.

Changed in xorg-server (Ubuntu):
status: New → Confirmed
importance: Undecided → High
Daniel van Vugt (vanvugt) wrote :

I've just done a little tidy up of some of the hottest xorg-server crashes. This one is presently #64 of the xorg-server crashes affecting bionic. There have been 7 reports of it on errors.ubuntu.com in the past year.

summary: - Xwayland crashed with SIGABRT in st_renderbuffer_delete()
+ Xwayland crashed with SIGABRT in st_renderbuffer_delete() [often when
+ running Skype or Slack snaps]
Daniel van Vugt (vanvugt) wrote :

Now affecting cosmic too, only just:

bionic: 156
cosmic: 1

tags: added: cosmic
Jacob D'Onofrio (jdonofrio728) wrote :

I'm on cosmic, upgraded from bionic, and I have the same issue. I had to revert to an X11 session in order to launch slack.

Jacob D'Onofrio (jdonofrio728) wrote :
Download full text (3.9 KiB)

Oct 22 09:01:41 NOV13FG5Q2 dbus-daemon[2934]: [session uid=1000 pid=2934] Activating service name='org.gnome.GConf' requested by ':1.84' (uid=1000 pid=5586 comm="/snap/slack/9/usr/lib/slack/slack --executed-from
=" label="snap.slack.slack (complain)")
Oct 22 09:01:41 NOV13FG5Q2 dbus-daemon[2934]: [session uid=1000 pid=2934] Successfully activated service 'org.gnome.GConf'
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE)
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) Backtrace:
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 0: /usr/bin/Xwayland (OsLookupColor+0x139) [0x55bab3776c39]
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) [0x7f18b4fcae1f]
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 2: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (__driDriverGetExtensions_virtio_gpu+0x1d7940) [0x7f18b1449760]
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 3: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (__driDriverGetExtensions_virtio_gpu+0x13a021) [0x7f18b130e4b1]
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (__driDriverGetExtensions_virtio_gpu+0xc882a) [0x7f18b122b52a]
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (__driDriverGetExtensions_virtio_gpu+0xc887e) [0x7f18b122b5ee]
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (__driDriverGetExtensions_virtio_gpu+0xc8929) [0x7f18b122b6c9]
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 7: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (__driDriverGetExtensions_virtio_gpu+0x2e7d2) [0x7f18b10f7432]
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 8: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (__driDriverGetExtensions_virtio_gpu+0x1e481d) [0x7f18b146335d]
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 9: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (__driDriverGetExtensions_virtio_gpu+0x3c6ce9) [0x7f18b1827e89]
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 10: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (__driDriverGetExtensions_virtio_gpu+0x3c5bd3) [0x7f18b1825c93]
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 11: /usr/bin/Xwayland (ht_dump_contents+0x79a9) [0x55bab36a3c69]
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 12: /usr/bin/Xwayland (ht_dump_contents+0x66fb) [0x55bab36a168b]
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 13: /usr/bin/Xwayland (RegisterResourceName+0x22d) [0x55bab376561d]
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 14: /usr/bin/Xwayland (ht_dump_contents+0xb9a9) [0x55bab36abbd9]
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 15: /usr/bin/Xwayland (glvndGetExports+0xde5) [0x55bab3785f35]
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 16: /usr/bin/Xwayland (SendErrorToClient+0x35e) [0x55bab3740bae]
Oct 22 09:01:42 NOV13FG5Q2 org.gnome.Shell.desktop[3043]: (EE) 17: /usr/bin/Xwayland (InitFon...

Read more...

HankB (hbarta) wrote :

I'm seeing what I believe to be the same issue with Visual Studio Code. If I try to start it after logging in using Gnome on Wayland, I find myself looking at a login screen. (If I login to Gnome on Xorg this does not happen.)

There is a core file in my home directory

There is also a file in /var/crashes
hbarta@karakum:~$ ls /var/crash
_usr_bin_pulseaudio.1000.crash _usr_bin_Xwayland.1000.crash
hbarta@karakum:~$

hbarta@karakum:~$ file core
core: ELF 64-bit LSB core file x86-64, version 1 (SYSV), SVR4-style, from '/usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 4 -listen 5 -d', real uid: 1000, effective uid: 1000, real gid: 1000, effective gid: 1000, execfn: '/usr/bin/Xwayland', platform: 'x86_64'
hbarta@karakum:~$

I tried to install debug symbols for Xwayland but cannot.

hbarta@karakum:~$ sudo apt install xwayland-dbgsym
[sudo] password for hbarta:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 xwayland-dbgsym : Depends: xwayland (= 2:1.19.6-1ubuntu4.1) but 2:1.19.6-1ubuntu4 is to be installed
E: Unable to correct problems, you have held broken packages.
hbarta@karakum:~$

I have the same problem on Debian Testing but not Fedora 28. (On Debian testing I am not running vs code as a snap.)

I would like to use Wayland for the improved monitor scaling so I can use a 1600x1200 eternal monitor with a QHD laptop.

If there is any further information I could provide (and I'm sure I'm light in this regard) please let me know.

Matt Johnson (matt9j) wrote :

I recently switched back to Ubuntu, only to find that Slack in a snap is still crashing on Wayland! I previously reported what seems like a related bug on snapcraft-- here's the link to the related bug with logs and some details from experiences on Fedora28 and Arch. https://forum.snapcraft.io/t/slack-for-linux-crash-on-wayland/5909

Currently still experiencing the issue with Ubuntu 18.10:

```
$ snap info slack
name: slack
summary: Team communication for the 21st century.
publisher: Slack✓
contact: https://get.slack.help/hc/en-us
license: Proprietary
description: |
  Caution: Slack for Linux is in beta. We’re still busy adding features and ironing out potential
  issues.

  Slack brings team communication and collaboration into one place so you can get more work done,
  whether you belong to a large enterprise or a small business. Check off your to-do list and move
  your projects forward by bringing the right people, conversations, tools, and information you need
  together. Slack is available on any device, so you can find and access your team and your work,
  whether you’re at your desk or on the go.

  Scientifically proven (or at least rumored) to make your working life simpler, more pleasant, and
  more productive. We hope you’ll give Slack a try.

  Stop by and learn more at: https://slack.com/
snap-id: JUJH91Ved74jd4ZgJCpzMBtYbPOzTlsD
channels:
  stable: 3.3.3 (9) 148MB classic
  candidate: ↑
  beta: ↑
  edge: 3.3.1 (8) 148MB classic
```

```
$ snap --version
snap 2.35.5+18.10
snapd 2.35.5+18.10
series 16
ubuntu 18.10
kernel 4.18.0-10-generic
```

I'm happy to provide any testing or log resources-- let me know if there's anything I can help out with!

I have the same issue on 18.04, Wayland:
```
$ snap list skype
Name Version Rev Tracking Publisher Notes
skype 8.33.0.41 63 stable skype✓ classic
```

Daniel van Vugt (vanvugt) wrote :
description: updated
summary: - Xwayland crashed with SIGABRT in st_renderbuffer_delete() [often when
- running Skype or Slack snaps]
+ Xwayland/Xorg crashed with SIGABRT in st_renderbuffer_delete() [often
+ when running Skype or Slack snaps]
summary: - Xwayland/Xorg crashed with SIGABRT in st_renderbuffer_delete() [often
- when running Skype or Slack snaps]
+ Xwayland/Xorg crashed with SIGABRT in st_renderbuffer_delete() from
+ _mesa_reference_renderbuffer_() [often when running Skype or Slack
+ snaps]
Daniel van Vugt (vanvugt) wrote :

Also, this is a SIGSEGV...

 OsSigHandler (signo=11

summary: - Xwayland/Xorg crashed with SIGABRT in st_renderbuffer_delete() from
+ Xwayland/Xorg crashed with SIGSEGV in st_renderbuffer_delete() from
_mesa_reference_renderbuffer_() [often when running Skype or Slack
snaps]
Iain Lane (laney) on 2018-11-15
tags: added: rls-cc-incoming
Will Cooke (willcooke) on 2018-11-20
Changed in xorg-server (Ubuntu):
assignee: nobody → Timo Aaltonen (tjaalton)
Iain Lane (laney) on 2018-11-20
Changed in mesa (Ubuntu Bionic):
assignee: nobody → Timo Aaltonen (tjaalton)
Changed in mesa (Ubuntu Cosmic):
assignee: nobody → Timo Aaltonen (tjaalton)
Changed in mesa (Ubuntu Disco):
assignee: nobody → Timo Aaltonen (tjaalton)
Changed in xorg-server (Ubuntu Bionic):
assignee: nobody → Timo Aaltonen (tjaalton)
Changed in xorg-server (Ubuntu Cosmic):
assignee: nobody → Timo Aaltonen (tjaalton)
Timo Aaltonen (tjaalton) wrote :

please test new xserver from https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging

only for cosmic at this point

Changed in xorg-server (Ubuntu Disco):
status: Confirmed → Incomplete
Timo Aaltonen (tjaalton) on 2018-11-27
Changed in xorg-server (Ubuntu Cosmic):
status: New → Incomplete
Iain Lane (laney) on 2018-11-27
tags: removed: rls-cc-incoming
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in mesa (Ubuntu Bionic):
status: New → Confirmed
Changed in mesa (Ubuntu Cosmic):
status: New → Confirmed
Changed in xorg-server (Ubuntu Bionic):
status: New → Confirmed
Ken VanDine (ken-vandine) wrote :

I can confirm with the PPA enabled I no longer see classic snaps crash when running wayland on cosmic. I tested vscode and slack.

Timo Aaltonen (tjaalton) wrote :

excellent, I'll prepare the sru for cosmic

bionic will get 1.20.3 as part of 18.04.2 HWE stack

Changed in mesa (Ubuntu Bionic):
status: Confirmed → Invalid
Changed in mesa (Ubuntu Cosmic):
status: Confirmed → Invalid
Changed in mesa (Ubuntu Disco):
status: Confirmed → Invalid
Changed in xorg-server (Ubuntu Disco):
status: Incomplete → Fix Released
Changed in xorg-server (Ubuntu Cosmic):
status: Incomplete → Triaged
To post a comment you must log in.