[Bug 1004686] New: In the presence of gstreamer-plugins-vaapi, totem is not able to play videos
http://bugzilla.suse.com/show_bug.cgi?id=1004686 Bug ID: 1004686 Summary: In the presence of gstreamer-plugins-vaapi, totem is not able to play videos Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: xorg-maintainer-bugs@forge.provo.novell.com Reporter: gp@suse.com QA Contact: xorg-maintainer-bugs@forge.provo.novell.com Found By: --- Blocker: --- This is consistently reproducible on my system (current Tumbleweed, Lneovo T450 with Broadwell-U Integrated Graphics, see below). When gstreamer-plugins-vaapi is installed, totem plays the sound, but no video output for MP4s, FLVs,... Once gstreamer/VAAPI is removed, everything is back to normal. This feels similar to bug #951150 from a year ago. # hwinfo --gfx 08: PCI 02.0: 0300 VGA compatible controller (VGA) [Created at pci.374] Unique ID: _Znp.FN2jBW+YDR6 SysFS ID: /devices/pci0000:00/0000:00:02.0 SysFS BusID: 0000:00:02.0 Hardware Class: graphics card Model: "Intel Broadwell-U Integrated Graphics" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x1616 "Broadwell-U Integrated Graphics" SubVendor: pci 0x17aa "Lenovo" SubDevice: pci 0x5034 Revision: 0x09 Driver: "i915" Driver Modules: "drm" Memory Range: 0xe0000000-0xe0ffffff (rw,non-prefetchable) Memory Range: 0xd0000000-0xdfffffff (ro,non-prefetchable) I/O Ports: 0x3000-0x303f (rw) Memory Range: 0x000c0000-0x000dffff (rw,non-prefetchable,disabled) IRQ: 43 (1042676 events) I/O Ports: 0x3c0-0x3df (rw) Module Alias: "pci:v00008086d00001616sv000017AAsd00005034bc03sc00i00" Driver Info #0: Driver Status: i915 is active Driver Activation Cmd: "modprobe i915" Config Status: cfg=new, avail=yes, need=no, active=unknown -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1004686 http://bugzilla.suse.com/show_bug.cgi?id=1004686#c1 --- Comment #1 from Gerald Pfeifer <gp@suse.com> --- https://bugzilla.redhat.com/show_bug.cgi?id=1123536 also seems related (if not the same). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1004686 http://bugzilla.suse.com/show_bug.cgi?id=1004686#c2 Dominique Leuenberger <dimstar@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dimstar@opensuse.org --- Comment #2 from Dominique Leuenberger <dimstar@opensuse.org> --- Very likely the same as redhat - as in TW with GNOME 3.22, the session switched to be a wayland session too. You can verify this as cause by logging in explicitly to a Xorg session (chose the session at the gdm login screen) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1004686 http://bugzilla.suse.com/show_bug.cgi?id=1004686#c3 Gerald Pfeifer <gp@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED --- Comment #3 from Gerald Pfeifer <gp@suse.com> --- (In reply to Dominique Leuenberger from comment #2)
Very likely the same as redhat - as in TW with GNOME 3.22, the session switched to be a wayland session too.
You can verify this as cause by logging in explicitly to a Xorg session (chose the session at the gdm login screen)
Yes, verified switching between two different account and installing/ deinstalling this package. As long as this is broken, should we really default to Wayland? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1004686 http://bugzilla.suse.com/show_bug.cgi?id=1004686#c4 --- Comment #4 from Dominique Leuenberger <dimstar@opensuse.org> --- (In reply to Gerald Pfeifer from comment #3)
Yes, verified switching between two different account and installing/ deinstalling this package.
As long as this is broken, should we really default to Wayland?
I'd argue that for TW - where we target tech enthusiast, this default is fine (unless we find worse issues that can't be worked around) - somehow we have to get the experience with this after all. For Leap, of course, this would be out of place (and is also not the case) -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com