buggy display of video in totem

Bug #41148 reported by capnemo on 2006-04-24
28
Affects Status Importance Assigned to Milestone
X.Org X server
Invalid
Medium
xserver-xorg-video-savage (Ubuntu)
Medium
Unassigned

Bug Description

I have display several videos (mov and wmv) with totem on a savage xorg driver and saw lots of problem of display :
an example can be found here : http://www.flickr.com/photos/57244393@N00/134263889/

I have replay those video thru the vesa driver, and no problem appear.

Im on a Dapper and savage driver version is 2.0.2.3-0ubuntu1.

So right now, I fall back on vesa.

Here's a copy of my xdpyinfo output:

name of display: :0.0
version number: 11.0
vendor string: The X.Org Foundation
vendor release number: 70000000
X.Org version: 7.0.0
maximum request size: 16777212 bytes
motion buffer size: 256
bitmap unit, bit order, padding: 32, LSBFirst, 32
image byte order: LSBFirst
number of supported pixmap formats: 7
supported pixmap formats:
    depth 1, bits_per_pixel 1, scanline_pad 32
    depth 4, bits_per_pixel 8, scanline_pad 32
    depth 8, bits_per_pixel 8, scanline_pad 32
    depth 15, bits_per_pixel 16, scanline_pad 32
    depth 16, bits_per_pixel 16, scanline_pad 32
    depth 24, bits_per_pixel 32, scanline_pad 32
    depth 32, bits_per_pixel 32, scanline_pad 32
keycode range: minimum 8, maximum 255
focus: window 0x1e00007, revert to PointerRoot
number of extensions: 28
    BIG-REQUESTS
    DAMAGE
    DOUBLE-BUFFER
    DPMS
    Extended-Visual-Information
    GLX
    LBX
    MIT-SCREEN-SAVER
    MIT-SHM
    MIT-SUNDRY-NONSTANDARD
    RANDR
    RENDER
    SECURITY
    SGI-GLX
    SHAPE
    SYNC
    TOG-CUP
    X-Resource
    XC-APPGROUP
    XC-MISC
    XFIXES
    XFree86-Bigfont
    XFree86-Misc
    XFree86-VidModeExtension
    XInputExtension
    XKEYBOARD
    XTEST
    XVideo
default screen number: 0
number of screens: 1

screen #0:
  print screen: no
  dimensions: 1400x1050 pixels (474x356 millimeters)
  resolution: 75x75 dots per inch
  depths (7): 16, 1, 4, 8, 15, 24, 32
  root window id: 0x3f
  depth of root window: 16 planes
  number of colormaps: minimum 1, maximum 1
  default colormap: 0x20
  default number of colormap cells: 64
  preallocated pixels: black 0, white 65535
  options: backing-store NO, save-unders NO
  largest cursor: 64x64
  current input event mask: 0xfa4031
    KeyPressMask EnterWindowMask LeaveWindowMask
    KeymapStateMask StructureNotifyMask SubstructureNotifyMask
    SubstructureRedirectMask FocusChangeMask PropertyChangeMask
    ColormapChangeMask
  number of visuals: 4
  default visual id: 0x22
  visual:
    visual id: 0x22
    class: TrueColor
    depth: 16 planes
    available colormap entries: 64 per subfield
    red, green, blue masks: 0xf800, 0x7e0, 0x1f
    significant bits in color specification: 6 bits
  visual:
    visual id: 0x23
    class: TrueColor
    depth: 16 planes
    available colormap entries: 64 per subfield
    red, green, blue masks: 0xf800, 0x7e0, 0x1f
    significant bits in color specification: 6 bits
  visual:
    visual id: 0x24
    class: TrueColor
    depth: 16 planes
    available colormap entries: 64 per subfield
    red, green, blue masks: 0xf800, 0x7e0, 0x1f
    significant bits in color specification: 6 bits
  visual:
    visual id: 0x25
    class: TrueColor
    depth: 16 planes
    available colormap entries: 64 per subfield
    red, green, blue masks: 0xf800, 0x7e0, 0x1f
    significant bits in color specification: 6 bits

Created an attachment (id=4897)
a screen capture showing the corruption pattern

And here's a screenshot showing an example of the corruption: the blue area on
the right is my desktop background, and it should be solid blue. The width of
the artefacts varies from case to case, but they generally have that sort of
pattern.

Is the dri enabled? does it help if you disable it? Also does it help if you
disable tiling (see savage man page)?

Sorry about taking so long to get back to this... no, DRI is not enabled (it's
built, but I don't have enough VRAM to enable it at full resolution: it's an 8MB
card, but my laptop's LCD is 1400x1050). I tried disabling tiling, but that
didn't help. Switching to 24bpp depth, however, seems to fix the problem.

Created an attachment (id=5213)
screencapture of the corruption with tiling disabled

Here's a screen capture showing an example of the corruption pattern with
Option "DisableTiling" "TRUE" (and my X.0.log confirmed that tiling was
disabled).

capnemo (nicolas-dufour) wrote :

I have display several videos (mov and wmv) with totem on a savage xorg driver and saw lots of problem of display :
an example can be found here : http://www.flickr.com/photos/57244393@N00/134263889/

I have replay those video thru the vesa driver, and no problem appear.

Im on a Dapper and savage driver version is 2.0.2.3-0ubuntu1.

So right now, I fall back on vesa.

istoyanov (istoyanov) wrote :

Most probably Bug #63062 is a duplicate of this one.

ChristofferS (ubuntu-curo) wrote :

The newest xorg in Feisty has fixed this issue for me.

Sorry about the phenomenal bug spam, guys. Adding xorg-team@ to the QA contact so bugs don't get lost in future.

Michael Kanis (mkanis) wrote :

I'm using Edgy and tested this with the Feisty Herd 5 LiveCD. The bug exists in both versions.
The problem does not only appear with Totem but also with mplayer etc.
When the video is displayed at least as large as the video file's resolution, it is displayed correctly.

When you move the video window there appear also artifacts outside the window as described in #41148.

I have an IBM Thinkpad T23 with SuperSavage graphics and use the savage X11 driver.

ChristofferS (ubuntu-curo) wrote :

The bug has returned like Michael describes.

Timo Aaltonen (tjaalton) wrote :

Yep, tested it now.

Changed in xserver-xorg-video-savage:
assignee: nobody → tepsipakki
status: Unconfirmed → Confirmed
Michael Kanis (mkanis) wrote :

For me the behaviour described in Bug #63062 seems to be gone. However I do not know why. I thought it had to do with the "Option BCIforXv" as described in `man savage` but that is not the reason. I removed that option to test again today and there do not appear artifacts outside the video window. Because I had that option disabled for a while and did not often test it, I also do not know when the artifacts disappeared. Sorry about that...

The buggy video output, when resizing the window to a size smaller than the video's resolution still exists though. This is especially a problem on web sites with embedded videos (like on http://www.apple.com/trailers/ e.g.), because they are often displayed smaller than they really are.

Changed in xorg-server:
status: Unknown → Confirmed
Timo Aaltonen (tjaalton) on 2007-09-21
Changed in xserver-xorg-video-savage:
assignee: tepsipakki → nobody
Tormod Volden (tormodvolden) wrote :

Does the test package from https://wiki.ubuntu.com/XorgOnTheEdge help any? There were some recent fixes in this direction, although mostly for BCI.

Sławek Mikuła (zorba) wrote :

Nothing changed for me, i've installed on gutsy xserver-xorg-video-savage_2.1.3+git20080131.583051fc-0ubuntu0tormod~gutsy but these two main issues are still there.

Thinkpad T23, SuperSavage (01:00.0 VGA compatible controller: S3 Inc. SuperSavage IX/C SDR (rev 05))

Bryce Harrington (bryce) wrote :

[This is an automatic notification.]

Hi capnemo,

This bug was reported against an earlier version of Ubuntu, can you
test if it still occurs on Lucid?

Please note we also provide technical support for older versions of
Ubuntu, but not in the bug tracker. Instead, to raise the issue through
normal support channels, please see:

    http://www.ubuntu.com/support

If you are the original reporter and can still reproduce the issue on
Lucid, please run the following command to refresh the report:

  apport-collect 41148

If you are not the original reporter, please file a new bug report, so
we can work with you as the original reporter instead (you can reference
bug 41148 in your report if you think it may be related):

  ubuntu-bug xorg

If by chance you can no longer reproduce the issue on Lucid or if you
feel it is no longer relevant, please mark the bug report 'Fix Released'
or 'Invalid' as appropriate, at the following URL:

  https://bugs.launchpad.net/ubuntu/+bug/41148

Changed in xserver-xorg-video-savage (Ubuntu):
status: Confirmed → Incomplete
tags: added: needs-retested-on-lucid-by-june
Changed in xorg-server:
importance: Unknown → Medium

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in xserver-xorg-video-savage (Ubuntu):
status: Incomplete → Invalid

Thank you for taking the time to report this bug and helping to make Ubuntu better. My apologies as I should not have marked this Invalid. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Maverick Meerkat. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help.

Changed in xserver-xorg-video-savage (Ubuntu):
status: Invalid → Incomplete
Changed in xorg-server:
importance: Medium → Unknown
Changed in xorg-server:
importance: Unknown → Medium

Is this still an issue. The ubuntu bug was closed due to lack of response, so
I'm wondering if it has been fixed already.

I can't really say anything about this bug, as I no longer have the laptop with a Savage/IX chip.
Close WORKSFORME?

Mass closure: This bug has been untouched for more than six years, and is not
obviously still valid. Please reopen this bug or file a new report if you continue to experience issues with current releases.

Changed in xorg-server:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.