totem crashed with SIGSEGV in _cogl_check_extension()

Bug #1681210 reported by howefield
76
This bug affects 9 people
Affects Status Importance Assigned to Milestone
totem (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

https://errors.ubuntu.com/problem/f29dd1e48e0d4c79dde7164f395c849006dcb066

---

totem crashed with SIGSEGV in cogl_renderer_connect()

ProblemType: Crash
DistroRelease: Ubuntu 17.04
Package: totem 3.24.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun Apr 9 12:31:17 2017
ExecutablePath: /usr/bin/totem
InstallationDate: Installed on 2017-04-09 (0 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170408)
ProcCmdline: /usr/bin/totem --gapplication-service
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANGUAGE=en_GB:en
 LANG=en_GB.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7ff19da4db59: mov (%rsi),%rsi
 PC (0x7ff19da4db59) ok
 source "(%rsi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rsi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: totem
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
 ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
 ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
 cogl_renderer_connect () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
 ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
Title: totem crashed with SIGSEGV in cogl_renderer_connect()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

Revision history for this message
howefield (howefield) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 _cogl_check_extension (name=0x562119985d90 "GLX_EXT_texture_from_pixmap", ext=ext@entry=0x0) at cogl.c:75
 _cogl_feature_check (renderer=renderer@entry=0x562119a08450, driver_prefix=driver_prefix@entry=0x7ff19daaec1b "GLX", data=data@entry=0x7ff19dcd0d18 <winsys_feature_data+56>, gl_major=<optimized out>, gl_minor=<optimized out>, driver=driver@entry=COGL_DRIVER_GL, extensions=0x0, function_table=0x562119afe000) at cogl-feature-private.c:128
 update_base_winsys_features (renderer=0x562119a08450) at winsys/cogl-winsys-glx.c:692
 _cogl_winsys_renderer_connect (renderer=0x562119a08450, error=<optimized out>) at winsys/cogl-winsys-glx.c:794
 cogl_renderer_connect (renderer=0x562119a08450, error=0x7ffffcbb1430) at cogl-renderer.c:687

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in totem (Ubuntu):
importance: Undecided → Medium
summary: - totem crashed with SIGSEGV in cogl_renderer_connect()
+ totem crashed with SIGSEGV in _cogl_check_extension()
tags: removed: need-amd64-retrace
tags: added: artful
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in totem (Ubuntu):
status: New → Confirmed
information type: Private → Public
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :
description: updated
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.