[FEISTY] Launching several instances of Codeine causes problems

Bug #83965 reported by Christophe Dumez
6
Affects Status Importance Assigned to Milestone
codeine (Ubuntu)
Invalid
Undecided
Ralph Janke

Bug Description

Binary package hint: codeine

If I have two instances of codeine running, then the second one won't display the video correctly : the colors in the video will be altered a lot. This happens even if the video in the first codeine instance is paused.

I have to close the first instance of codeine to get the second one to work correctly.

Revision history for this message
Christophe Dumez (hydr0g3n) wrote :

Looks like the problem comes from this (from console output) :

First instance:
video_out_xv: using Xv port 73 from adaptor ATI Radeon Video Overlay for hardware colorspace conversion and scaling.

Second instance:
video_out_xv: Xv extension is present but I couldn't find a usable yuv12 port.
              Looks like your graphics hardware driver doesn't support Xv?!

Here is my devide section in xorg.conf:
Section "Device"
        Identifier "ATI Technologies, Inc. Radeon X600 (RV380)"
        Driver "ati"
        BusID "PCI:3:0:0"
        Option "DRI" "true"
        Option "ColorTiling" "on"
        Option "EnablePageFlip" "true"
        Option "AccelMethod" "EXA"
        Option "XAANoOffscreenPixmaps"
        Option "RenderAccel" "true"
        Option "AGPFastWrite" "on"
EndSection

Revision history for this message
Ralph Janke (txwikinger) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the development release - Hardy Heron. 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 codeine:
assignee: nobody → txwikinger
status: New → Incomplete
Revision history for this message
Ralph Janke (txwikinger) wrote :

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 codeine:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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