totem crashed with SIGSEGV in cogl_pixel_buffer_new()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
totem (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
$ totem movie.mkv
(totem:19054): Clutter-CRITICAL **: Unable to initialize Clutter: Unable to initialize the Clutter backend: no available drivers found.
(totem:19054): Totem-WARNING **: gtk-clutter failed to initialise, expect problems from here on.
(totem:19054): Clutter-CRITICAL **: Unable to initialize Clutter: Unable to initialize the Clutter backend: no available drivers found.
(totem:19054): Clutter-WARNING **: Missing Cogl context: was Clutter correctly initialized?
Segmentation fault (core dumped)
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: totem 3.26.0-0ubuntu1
ProcVersionSign
Uname: Linux 4.13.0-12-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 20 19:11:32 2017
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/totem
InstallationDate: Installed on 2016-09-01 (413 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160111)
ProcCmdline: /usr/bin/totem --gapplication-
SegvAnalysis:
Segfault happened at: 0x7febc7858c60: testb $0x10,0xc0(%rsi)
PC (0x7febc7858c60) 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/
cogl_pixel_
cogl_bitmap_
?? () from /usr/lib/
clutter_
Title: totem crashed with SIGSEGV in cogl_pixel_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo
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.