Description of problem: When attempting to Cast a Tab or when attempting to Cast to another screen a Google Slide Presentation, Chromium fails to find a chromecast device, even though other computers on the same network interface find the chromecast device successfully. (Lubuntu 19.04, Ubuntu-Mate 19.10, and Windows 10 are all able to see and find the chromecast device successfully) Version-Release number of selected component (if applicable): Chromium 78 (latest version in the F31 default repo) How reproducible: Happens every time when using Chromium, even after reboot. Steps to Reproduce: 1. Open Chromium (installed from default F31 repo with "sudo dnf install chromium") 2. Attempt to either "Cast..." from the menu or "Present on another screen" from the drop down selector next to the "Present" button in Google Slides application. 3. A pop up will appear claiming "No Device Available" even though the chromecast is not in use, and it can be seen by other OS's. Actual results: "No Device Available" Expected results: It should list the chromecast that is plugged into the TV, and allow me to cast the Google Slides to it or cast the tab to it. Additional info: Strangely, Google Chrome is able on the same install of F31 to find the chromecast device, and is able to cast a Google Slides presentation to the chromecast. However, if I close Chrome and open Chromium on the same computer, and attempt to cast from Chromium, I can't find the chromecast that Google Chrome was just casting too from the same laptop. Also after failing to cast with Chromium, if I open Chrome again and attempt to cast it is now broken in Google Chrome too, it now fails to see the chromecast. A reboot seems to fix this issue so that Google Chrome can see and cast to the chromecast. My current work around this bug was to remove Chromium from the laptop, and leave only Google Chrome installed, and attempt to cast only from Google Chrome on this F31 install.
Hmm. I wonder if chromecast depends on widevine. Short back story: We have to disable some functionality in chromium due to legal issues, which makes our chromium package notably different from Google Chrome (and from other Linux distros which do not care about being sued). We know that widevine doesn't work in our build (even if you copy the widevine files from Google Chrome into chromium's path). Unfortunately, because widevine is the DRM component, it's entirely proprietary, and figuring out exactly why it doesn't work is basically impossible. You might try uninstalling the Fedora chromium and installing "chromium-freeworld" from https://unitedrpms.github.io/ and seeing if it has the same failure.
I will do some further testing in a few days to see if the same behavior exists for chromium-freeworld and chromium-vaapi from rpm fusion. I guessing that both of those packages would have the widevine libraries. If they work and if widevine is the only difference between those packages and what is found in the default F31 repos we will know that widevine is a necessary dependency for casting to function properly. I can update the Fedora Quick Docs to reflect that as well. Hopefully, I will have an update early next week.
Well, technically, none of them have the widevine libraries, but I have heard that those builds work when you copy the widevine libraries from the corresponding Google Chrome build. If the chromecast works on chromium-freeworld without widevine added, then it is something about the way we build chromium in Fedora which is breaking things.
This package has changed maintainer in the Fedora. Reassigning to the new maintainer of this component.
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. 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 '31'. 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 31 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.
So although F31 is end of life, I experienced the same issue on F33 with chromium and found the solution. You must *only* enable the following flag: chrome://flags/#load-media-router-component-extension. Yes there are a few other casting related settings, but you don't need them. There may also be some firewall related settings, There's a post on the internet about it from a 'Linux Kamarada' if you're interested (it's talking about a different distro but the settings are the same)
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 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.