← Back to team overview

desktop-packages team mailing list archive

[Bug 1381721] Re: unity8 crashed with SIGSEGV in intelClear()

 

I wouldn't expect this crash on i915 but we are aware that GL clients
like Unity8 will be all-black right now. That's bug 1275398.

Once bug 1275398 is solved then this bug might go away. Last I heard, we should expect that to get fixed when Mesa 10.3.1 enters utopic:
https://launchpad.net/ubuntu/+source/mesa

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1381721

Title:
  unity8 crashed with SIGSEGV in intelClear()

Status in Mir:
  New
Status in “mesa” package in Ubuntu:
  New
Status in “mir” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  New

Bug description:
  I tied the daliy image on my eeepc t91mt but it looks like it crashed on startup.
  I just see a black screen and the cursor.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: unity8 8.00+14.10.20141013.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4
  Uname: Linux 3.16.0-22-generic i686
  ApportVersion: 2.14.7-0ubuntu6
  Architecture: i386
  CasperVersion: 1.345
  Date: Wed Oct 15 19:38:11 2014
  ExecutablePath: /usr/bin/unity8
  ExecutableTimestamp: 1413216480
  LiveMediaBuild: Ubuntu-Desktop-Next 14.10 "Utopic Unicorn" - Alpha i386 (20141015)
  ProcCmdline: unity8
  ProcCwd: /home/ubuntu-desktop-next
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0xb15f9921:	cmpl   $0x2,0x18(%eax)
   PC (0xb15f9921) ok
   source "$0x2" ok
   destination "0x18(%eax)" (0x00000018) not located in a known VMA region (needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: unity8
  StacktraceTop:
   ?? () from /usr/lib/i386-linux-gnu/dri/i915_dri.so
   ?? () from /usr/lib/i386-linux-gnu/dri/i915_dri.so
   QSGBindable::clear(QFlags<QSGRenderer::ClearModeBit>) const () from /usr/lib/i386-linux-gnu/libQt5Quick.so.5
   QSGBatchRenderer::Renderer::renderBatches() () from /usr/lib/i386-linux-gnu/libQt5Quick.so.5
   QSGBatchRenderer::Renderer::render() () from /usr/lib/i386-linux-gnu/libQt5Quick.so.5
  SystemImageInfo:
   current build number: 0
   device name:
   channel: daily
   last update: Unknown
  Title: unity8 crashed with SIGSEGV in QSGBindable::clear()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  upstart.unity8-dash.log:
   UbuntuClientIntegration: connection to Mir server failed. Check that a Mir server is
   running, and the correct socket is being used and is accessible. The shell may have
   rejected the incoming connection, so check its log file

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1381721/+subscriptions