Totem changes system video hardware.
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| totem (Ubuntu) |
Confirmed
|
Low
|
Unassigned | ||
Bug Description
Binary package hint: totem
A few people have encountered totem suddenly (after an upgrade) displaying weird colors or just a black window.
This was caused by a "contrast" preference setting in totem changing to "0" after the upgrade (instead of the default "midscale").
The issue here is not that the contrast setting suddenly changed, but that totem seems to leave its contrast settings somewhere in the hardware resulting in other players like mplayer and vlc also displaying weird colors (with the open source driver) or a black window (with the proprietary video driver).
My analysis is that totem sets up some sort of pixel-processing pipeline, that includes its contrast pipeline. You could accuse mplayer and vlc of not properly initializing that pipeline because they seem to use totem's. But I think they simply don't use that feature, so they may not know about it. I think that totem should leave the hardware as it found it, and properly set the pipeline back to its original state.
This was a friends system. I think it has an NVIDIA video card (onboard, AMD X3 processor).
| rew (r-e-wolff) wrote | #1 |
| Pedro Villavicencio (pedro) wrote | #2 |
| Changed in totem (Ubuntu): | |
| importance: | Undecided → Low |
| status: | New → Incomplete |
| rew (r-e-wolff) wrote | #3 |
| Changed in totem (Ubuntu): | |
| status: | Incomplete → Confirmed |
The bug was observed on a friends system that suffered the "inadvertent contrast-
mplayer -vo x11 <filename> will display correctly, while mplayer -vo xv <filename> does not.