Red Hat Bugzilla – Bug 611955
starting ekiga result in other videodevice become unusable
Last modified: 2011-06-29 09:55:00 EDT
Description of problem:
When i start my fully configured and working ekiga, other videodevice become unusable util next reboot. e.g: me-tv
Version-Release number of selected component (if applicable):
I have no clue, what componets are involved,
so here is my wild guess:
Steps to Reproduce:
1. Start me-tv and watch television
2. Start ekiga with a connected uvcvideo usb cam
3. Videoplayback in me-tv will freeze ~20 sec., comes back for a few seconds and than freeze again forever.
In this state, restarting me-tv doesn't help, no video at all.
A full powercircle is required.
ekiga starts, video in me-tv stops playing, me-tv becomes unuseable.
ekiga starts, no video freeze in me-tv, me-tv stays useable.
running alone ekiga with usb-cam: works fine.
running alone me-tv with SAA Card: works fine.
both apps running together on differnt vieo devices don't work.
Some hardware info:
Bus 002 Device 004: ID 046d:0994 Logitech, Inc. QuickCam Orbit/Sphere AF
01:00.0 VGA compatible controller: nVidia Corporation G92 [GeForce 8800 GTS 512] (rev a2)
05:02.0 Multimedia controller: Philips Semiconductors SAA7131/SAA7133/SAA7135 Video Broadcast Decoder (rev d1)
Maybe some helpfull catch from my logfiles, wenn starting ekiga while me-tv is running:
==> messages <==
Jul 8 20:15:14 hurricane kernel: tda827xa_set_params: could not write to tuner at addr: 0xc2
==> /home/jensen/.xsession-errors <==
me-tv-player (xine): Setting deinterlacer state to trueme-tv-player (xine): Setting mute state to falseme-tv-player (xine): Xine engine terminating normally
==> messages <==
Jul 8 20:16:05 hurricane kernel: tda827xa_set_params: could not write to tuner at addr: 0xc2
Jul 8 20:16:06 hurricane kernel: tda827xa_set_params: could not write to tuner at addr: 0xc2
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '13'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 13's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 13 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.