Description of problem: When I start a video call with Cisco Spark (https://teams.webex.com/) I get an error message: "Could not acquire local media. Please check you settings". The webcam is blocked after this. I can then either replug the device or stop Chromium. This does not happen with Google hangouts for example. Also I could use an online webcam test without having issues: https://www.onlinemictest.com/webcam-test/ Version-Release number of selected component (if applicable): chromium-69.0.3497.100-1.fc29.x86_64 How reproducible: Start a Cisco Spark call with Chromium browser. Steps to Reproduce: 1. 2. 3. Actual results: Phone call is initiated. Expected results: Webcam is hanging. Additional info: Fedora 29 Silverblue. The issue does not happen with Chrome browser. Also I could test Chromium with Windows and also there this issue does not appear.
Sorry, I mixed it up: Actual results: Webcam is hanging. Expected results: Phone call is initiated. Also one additional note: when I start the call I see the LED of my webcam turns on. But it is hanging. If I try to use "Cheese" after this it does not work because the webcam is blocked by Chromium.
Best guess? The video format that Chromium needs to use Cisco Spark is not enabled in the Fedora Chromium build (for legal reasons). rpmfusion has a "chromium-libs-media-freeworld" replacement package that you could try. If installing that resolves the issue, then, I would suggest that you either use that (or Google Chrome), but I cannot resolve it in the Fedora Chromium.
Meanwhile I was able to test this. Same error. I have removed Chromium from my system.
> If I try to use "Cheese" after this it does not work because the webcam is blocked by Chromium. Seems like a completely different issue to me. Do you face this issue in Google Chrome?
No, there are no such issues with Chrome. Disadvantage of Chrome is that you cannot install the rpm package the normal way because files are installed in /opt which is not allowed for rpm packages with Silverblue. So what I did is I wrote a script which did all the necessary installation steps (rpm2cpio then upnack the cpio and so on) to have a more or less automatic update procedure for Chrome. Chromium could be an alternative if everything would work - which is obviously not the case.
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. 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 EOL if it remains open with a Fedora 'version' of '29'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 29 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.