totem crashed with SIGSEGV in wl_proxy_add_listener() from wl_buffer_add_listener() from dri2_wl_swap_buffers_with_damage() from eglSwapBuffers() from _cogl_winsys_onscreen_swap_buffers_with_damage()

[José Vidal]

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

---

I just opened the video from nautilus with double click

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: totem 3.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
Uname: Linux 4.12.0-13-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 12 16:06:22 2017
ExecutablePath: /usr/bin/totem
InstallationDate: Installed on 2017-09-17 (24 days ago)
InstallationMedia: It
ProcCmdline: /usr/bin/totem --gapplication-service
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANG=es_ES.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f368b77c77c <wl_proxy_add_listener+12>: testb $0x4,0x28(%rdi)
 PC (0x7f368b77c77c) 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: totem
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: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
XorgLog: Error: [Errno 2] No existe el archivo o el directorio: '/var/log/Xorg.0.log'

[Apport retracing service (apport)]

StacktraceTop:
 wl_proxy_add_listener (proxy=0x0, implementation=implementation@entry=0x7f368a4aae08 <wl_buffer_listener>, data=data@entry=0x56261fb10000) at ../src/wayland-client.c:469
 wl_buffer_add_listener (data=0x56261fb10000, listener=0x7f368a4aae08 <wl_buffer_listener>, wl_buffer=<optimized out>) at /usr/include/wayland-client-protocol.h:1709
 dri2_wl_swap_buffers_with_damage (drv=<optimized out>, disp=0x56261e0baad0, draw=0x56261fb10000, rects=0x0, n_rects=0) at ../../../src/egl/drivers/dri2/platform_wayland.c:872
 eglSwapBuffers (dpy=0x56261e0baad0, surface=<optimized out>) at ../../../src/egl/main/eglapi.c:1243
 _cogl_winsys_onscreen_swap_buffers_with_damage (onscreen=0x56261fb9f570, rectangles=0x7ffc260aefe0, n_rectangles=0) at winsys/cogl-winsys-egl.c:848

[Doug McMahon (mc3man)]

Seems to happen with any number of preceding actions, those seeing should note if gst-vappi is installed. If so does removing the plugin clear up this issue?

[José Vidal (josevidal)]

How can I see if gst-vappi is installed without opening totem? I can not open totem. I have removed Totem and then reinstalled it. It continues with the same problem.

[Doug McMahon (mc3man)]

On 10/14/2017 10:16 AM, José Vidal wrote:
> How can I see if gst-vappi is installed without opening totem? I can not
> open totem. I have removed Totem and then reinstalled it. It continues
> with the same problem.
>
In a terminal go
apt-cache policy gstreamer1.0-vaapi

[José Vidal (josevidal)]

Was installed
Instalados: 1.12.3-1ubuntu1
I've removed it but it still does not work

[Sebastien Bacher (seb128)]

Is that happening on any video or specific to one/some?

[José Vidal (josevidal)]

Now totem does not open. Not open with videos or without videos

[José Vidal (josevidal)]

Just before the bug message I was recording the desktop according to the help guide, pressing ctrl + alt + shift + R
That video on the desktop was the first one I had problems.

[Launchpad Janitor (janitor)]

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

[Daniel van Vugt (vanvugt)]

Tracking also in:
https://errors.ubuntu.com/problem/bc6e28a2367ba53b9714f5982d0034dbd45a1fd7

[Daniel van Vugt (vanvugt)]

No crashes reported after 18.04 so consider it fixed.