weston crashed with SIGSEGV in eglGetDisplay()

Bug #1235929 reported by Dennj Osele
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu GNOME
New
Undecided
Unassigned

Bug Description

it's crashed alone on startup pc

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: weston 1.2.0-0ubuntu1~13.10~ricotz0 [origin: LP-PPA-gnome3-team-gnome3-staging]
ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
Uname: Linux 3.11.0-11-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
Date: Sat Oct 5 14:29:41 2013
Disassembly: => 0x0: Cannot access memory at address 0x0
ExecutablePath: /usr/bin/weston
InstallationDate: Installed on 2012-10-23 (347 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MarkForUpload: True
ProcCmdline: /usr/bin/weston
SegvAnalysis:
 Segfault happened at: 0x0: Cannot access memory at address 0x0
 PC (0x00000000) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: weston
StacktraceTop:
 ?? ()
 eglGetDisplay () from /usr/lib/x86_64-linux-gnu/libhybris-egl/libEGL.so.1
 gl_renderer_create ()
 backend_init () from /usr/lib/x86_64-linux-gnu/weston/drm-backend.so
 ?? ()
Title: weston crashed with SIGSEGV in eglGetDisplay()
UpgradeStatus: Upgraded to saucy on 2013-10-05 (1 days ago)
UserGroups:

Revision history for this message
Dennj Osele (dennj-osele) wrote :
information type: Private → Public
Revision history for this message
Ubuntu GNOME (ug-bot) wrote :

StacktraceTop:
 ?? ()
 eglGetDisplay (display_id=0x1cd0080) at egl.c:177
 gl_renderer_create ()
 backend_init () from /home/darkxst/gnome3-amd64/usr/lib/x86_64-linux-gnu/weston/drm-backend.so
 ?? ()

Revision history for this message
Ubuntu GNOME (ug-bot) wrote : Stacktrace.txt
Revision history for this message
Ubuntu GNOME (ug-bot) wrote : StacktraceSource.txt
Revision history for this message
Ubuntu GNOME (ug-bot) wrote : ThreadStacktrace.txt
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.