When using vaapi in a wayland session a gl renderer launch icon appears

[Doug McMahon]

Test case:
install gstreamer1.0-vaapi
log into wayland session
play a video in totem

What happens: A non usable icon appears in launcher
Basically harmless but would be better if it didn't show

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: totem 3.25.90.1-0ubuntu3
ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
Uname: Linux 4.12.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 12 21:34:06 2017
InstallationDate: Installed on 2017-09-10 (2 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170908)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: totem
UpgradeStatus: No upgrade log present (probably fresh install)
XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

[Launchpad Janitor (janitor)]

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

[Daniel van Vugt (vanvugt)]

Confirmed, but I wonder if this is a dock/shell bug. If that OpenGL window is actually the video sub-surface then the shell or dock should ideally recognise it's a child and not list it as an application window.

[Doug McMahon (mc3man)]

I wouldn't have the tech know-how to explore if it's a 'dock/shell bug', I do see 2 things
1. happens with gnome-shell's default dock also (gnome-session
2. See this line which doesn't occur without vaapi
totem[2604]: Native Windows taller than 65535 pixels are not supported

[Ryan (baronhk)]

It does this with GNOME Web too, it seems (even still in Ubuntu 18.04).

It's not _too_ annoying if you're just watching Youtube or something, but if you scroll down a Facebook tab it gets pretty obnoxious, because it creates a new "OpenGL Renderer" entry on the dock each time you scroll past a video of something, and doesn't go away until you close the tab.

[Daniel van Vugt (vanvugt)]

The problem seems to be fixed in 20.10. Not sure exactly when it got fixed.