Intermittent Video Playback Issue in Gutsy with NVIDIA restricted driver
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux-restricted-modules-2.6.24 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Intermittently, upon play back of videos, the player will show green and scrambled graphics instead of the regular video. This is monitor specific, with dual monitors, based on which monitor the video window originates. Upon moving the video back and forth between the two monitors, the video goes from good to bad to good again. Sometimes, one monitor will show a still image of the video, while the other shows the scrambled green. Sometimes, one monitor will consistently fail to show a video, while the other monitor will consistently succeed in showing the video. Sometimes, both monitors will consistently fail.
When the video player is dragged to a second monitor, the video freezes or goes scrambled green. When the video is dragged back to the original monitor, the video plays normally. The video can be between the two screens and only the part of the video on the original monitor will play.
I am using the new Gutsy (AMD64), with the Ubuntu-supplied restricted NVIDIA driver 100.14.19, I configured my two Dell 2005WP / 2007WP monitors with the Screen and Graphics tool, and I am having the problem with both Totem, Xine, and Firefox embedded video. This happens with all codecs, including OGG theora.
This problem only started occurring after upgrading to Gutsy.
I tried switching out gstreamer, codecs, and the totem player. None of these made a difference. So, I have concluded it must be the new Ubuntu NVIDIA driver, by process of elimination.
A work around is restarting the X display.
Someone else noted this same issue on the Forums: http://
I am seeing videos with dodgy color maps too in Gutsy AMD64, but I have an Intel G965 graphics chipset. My videos come out mostly green and black, with patches of purple. Restarting the PC seems to fix the problem (but I need to verify this properly). I am wondering if the bug is triggered by X resuming from Suspend-to-RAM? I'll try to test this too ...