unity8 crashed with SIGSEGV

Bug #1623508 reported by Pablo Caviglia on 2016-09-14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mir (Ubuntu)
unity8 (Ubuntu)
xserver-xorg-video-nouveau (Ubuntu)

Bug Description

16.10 first unity 8 run16.10 first unity 8 run

ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: unity8 8.14+16.10.20160831.3-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
Uname: Linux 4.4.0-9136-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
Date: Wed Sep 14 10:32:07 2016
ExecutablePath: /usr/bin/unity8
InstallationDate: Installed on 2016-09-14 (0 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160913)
ProcCmdline: unity8 --mode=full-shell
Signal: 11
SourcePackage: unity8
 ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
 ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
 ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
 ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
 ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
Title: unity8 crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Pablo Caviglia (pablo-caviglia) wrote :

 pushbuf_kref () from /tmp/apport_sandbox_eG50i_/usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
 pushbuf_validate () from /tmp/apport_sandbox_eG50i_/usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
 PUSH_KICK (push=<optimized out>) at ../../../../../src/gallium/drivers/nouveau/nouveau_winsys.h:59
 nv50_flush (pipe=0x7ff89807e5a0, fence=<optimized out>, flags=<optimized out>) at ../../../../../src/gallium/drivers/nouveau/nv50/nv50_context.c:40
 st_glFlush (ctx=<optimized out>) at ../../../src/mesa/state_tracker/st_cb_flush.c:121

Changed in unity8 (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
information type: Private → Public
Daniel van Vugt (vanvugt) wrote :

Thanks for your bug report.

Unfortunately we already know that the nouveau driver is unstable particularly with multi-threaded (multi-headed) rendering. The best suggestion right now is to either only use a single monitor or to use intel or radeon graphics.

Duplicate of bug 1553328.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers