Opened 6 years ago

Closed 15 months ago

#12326 closed Bug Report - General (Fixed)

Black screen after exiting playback with nouveau/VDPAU on Ubuntu 14.10

Reported by: dave@… Owned by:
Priority: minor Milestone: 31.0
Component: MythTV - General Version: 0.27.4
Severity: medium Keywords:
Cc: Ticket locked: no


When using the nouveau driver on an ION2 (NVA8 chipset), I get a black screen after exiting playback of recordings. The system is responsive -- if I hit <ENTER>, playback will start again without issue. The menu simply does not redraw.

I originally saw this issue in a custom initramfs I have built for my frontends, using mythtv 0.27.4/libdrm2 2.4.58/mesa2-10.3.4. Using mesa2-10.1.3 did not show the issue. I then reproduced it in Ubuntu (using the distro-provided libraries and Myth frontend) to ensure it was reproducible by other builds.

I have bisected the change in Mesa that leads to the issue -- is the bad commit. This changes from independent DRM screens for VDPAU and OpenGL to having them share a single screen. The change is to resolve which references gstreamer2 and the use of GL_NV_vdpau_interop, which leaves me hope that there is an example of how things should be working after the change.

I'm also hopeful that its simply a Z-order issue and easily correctable in Myth -- I suspect it is more than just calling draw() on the main window, as using the arrows to change the selected recording does not result in the UI showing up.

It should not be terribly difficult for me to test patches or gather debugging information, though it may have to wait until the weekends due to time constraints.

Change History (2)

comment:1 Changed 6 years ago by David Dillow <dave@…>

I should note that this only occurs when using the OpenGL painter; the Qt painter does not suffer from this issue.

comment:2 Changed 15 months ago by Mark Kendall

Milestone: unknown31.0
Resolution: Fixed
Status: newclosed

VDPAU support has been entirely re-written in master and 0.31. It does indeed now use GL_NV_vdpau_interop so this should be fixed. Please open a new ticket if the issue persists.

Note: See TracTickets for help on using tickets.