Some recent update has completely messed up video playback on my system. I believe mplayer uses the 'xv' output by default and it now looks like it only manages to update a band here and there on each frame. The picture looks like it was run through a shredder and pasted back together with the wrong strips :-).
If I play with the 'gl_nosw' output driver, there are no problems (so that's the obvious work around).
The only X related update I notice recently was a bunch of mesa libraries on April 30th.
But I have all the same mesa libs on my system at work and it has no problems. At work I have the radeon driver, at home I have the intel driver, so maybe it is an intel driver problem (but the intel driver hasn't been updated recently).
Any idea what component I should report this against?
Anyone else see the same thing? (It isn't isolated to mplayer - I get the same corruption in vlc, etc).
On 05/05/14 19:57, Tom Horsley wrote:
Some recent update has completely messed up video playback on my system. I believe mplayer uses the 'xv' output by default and it now looks like it only manages to update a band here and there on each frame. The picture looks like it was run through a shredder and pasted back together with the wrong strips :-).
If I play with the 'gl_nosw' output driver, there are no problems (so that's the obvious work around).
The only X related update I notice recently was a bunch of mesa libraries on April 30th.
But I have all the same mesa libs on my system at work and it has no problems. At work I have the radeon driver, at home I have the intel driver, so maybe it is an intel driver problem (but the intel driver hasn't been updated recently).
Any idea what component I should report this against?
Anyone else see the same thing? (It isn't isolated to mplayer - I get the same corruption in vlc, etc).
It may still be the mesa issues....
I say this because I am having no problems with nVidia HW and the nVidia drivers from rpmfusion while others are having problems. There are also others having problems with one type of Intel graphics card, but not another type.
So, the bug needs a specific situation to become apparent. This is probably why it wasn't discovered initially.
On 05/05/14 22:05, Tom Horsley wrote:
On Mon, 05 May 2014 21:33:05 +0800 Ed Greshko wrote:
There are also others having problems with one type of Intel graphics card, but not another type.
Is there an existing bug report somewhere I could chime in on and add my video info?
https://bugs.freedesktop.org/show_bug.cgi?id=75723
https://bugzilla.redhat.com/show_bug.cgi?id=1093940
Are the 2 I know of....
https://bugs.freedesktop.org/show_bug.cgi?id=75723
https://bugzilla.redhat.com/show_bug.cgi?id=1093940
Are the 2 I know of....
Hmmm... Maybe they are the same problem, but the descriptions are so different I decided to make a new bug and let someone who might understand this stuff decide if they are the same :-).
https://bugzilla.redhat.com/show_bug.cgi?id=1094519
I did discover that if I boot the previous kernel the problem goes away, so I'm calling it a kernel problem for now.
-
Ed Greshko -
Tom Horsley