Conn > I was experiencing exactly what you described in comment 84. But I confirm that now, it works ! (with totem-gstreamer). In fact, now matter how hard I try, I cannot reproduce this bug at all ! (maybe with totem-xine ?)
FuturePast > can you try what is described in comment 84 ? (with xv_attr).
I think that the "parameter is set to a bad default" is fixed now in totem but that bad default is not set to a sane value if it was already broken by previous version of totem.
Conn > I was experiencing exactly what you described in comment 84. But I confirm that now, it works ! (with totem-gstreamer). In fact, now matter how hard I try, I cannot reproduce this bug at all ! (maybe with totem-xine ?)
FuturePast > can you try what is described in comment 84 ? (with xv_attr).
I think that the "parameter is set to a bad default" is fixed now in totem but that bad default is not set to a sane value if it was already broken by previous version of totem.