totem crashed with SIGSEGV in wl_proxy_add_listener()

Bug #1729071 reported by Fabio Randon
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gstreamer1.0 (Ubuntu)
New
Undecided
Unassigned

Bug Description

can't see an "avi" video

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: libgstreamer1.0-0 1.12.3-1
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: Tue Oct 31 20:59:03 2017
ExecutablePath: /usr/bin/totem
InstallationDate: Installed on 2017-01-03 (301 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
ProcCmdline: /usr/bin/totem --gapplication-service
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, user)
 LANG=it_IT.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f14f601477c <wl_proxy_add_listener+12>: testb $0x4,0x28(%rdi)
 PC (0x7f14f601477c) ok
 source "$0x4" ok
 destination "0x28(%rdi)" (0x00000028) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: gstreamer1.0
StacktraceTop:
 wl_proxy_add_listener () from /usr/lib/x86_64-linux-gnu/libwayland-client.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
 eglSwapBuffers () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
 ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
 cogl_onscreen_swap_buffers_with_damage () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
Title: totem crashed with SIGSEGV in wl_proxy_add_listener()
UpgradeStatus: Upgraded to artful on 2017-10-22 (9 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Fabio Randon (campasi69) 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 #1723130, 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.