totem crashed with SIGSEGV in cogl_pixel_buffer_new()

Bug #1725794 reported by ivo válek
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
totem (Ubuntu)
New
Undecided
Unassigned

Bug Description

no reaction after double clicking on any video or after Totem initilization...

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: totem 3.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 21 20:39:11 2017
ExecutablePath: /usr/bin/totem
InstallationDate: Installed on 2017-10-20 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcCmdline: /usr/bin/totem --gapplication-service
SegvAnalysis:
 Segfault happened at: 0x7f518df8cc60: testb $0x10,0xc0(%rsi)
 PC (0x7f518df8cc60) ok
 source "$0x10" ok
 destination "0xc0(%rsi)" (0x000000c0) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: totem
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
 cogl_pixel_buffer_new () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
 cogl_bitmap_new_with_size () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
 ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
 clutter_content_invalidate () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
Title: totem crashed with SIGSEGV in cogl_pixel_buffer_new()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
XorgLog: Error: [Errno 2] Adresář nebo soubor neexistuje: '/var/log/Xorg.0.log'

Revision history for this message
ivo válek (ivo.valek) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1724255, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

information type: Private → Public
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.