@vgaetera so I have tested chromium-freeworld (which installed when I attempted to install chromium-vaapi I’m assuming it is the same thing from rpmfusion). That version of chromium doesn’t find the chromecast device on the network either.
You seem to believe that this is not related to Chromium and what the Fedora team has removed from Chromium, but instead it has to do with mDNS. I’m a little unsure of what your sed command does to fix this issue, and I’m also wondering why this is needed for Chromium and not for Chrome, because I have confirmed that Chrome does work after installing and rebooting it will find a Chromecast. I would however appreciate your feedback.
I would like to update the Fedora Quick Doc for installing Chromium and Chrome, but I don’t feel that mucking around in the internals of Fedora’s mDNS system belongs in the “Quick Docs”. That seems to be taking the issue to a new level that is probably a bit beyond the average user that would be consulting the Quick Docs to simply figure out how to get Chromium or Chrome installed on their system. So what do you think we should do to proceed and help resolve this issue for Fedora users?
- I would like to rewrite the Quick Doc with a note that the Chromium builds available in the Fedora Repos and RPMFusion repos have broken features such as Chromecasting. If Chromecasting is a feature the is needed it is encouraged that the user installs Chrome from the Google provided RPM.
- Do you feel this is a good solutions for the Quick Docs so they are no longer giving misinformation?
- Would it be a good idea to add your thoughts about mDNS to the bug report that I opened, and request an infrastructure change to correct this problem or should to be done as a separate bug. I noticed that you CC: yourself to the bug that I opened, that is why I’m asking for your input on this.
Thank you for the part you played in researching mDNS, that is an area where I have no knowledge so I appreciate the work you have done there.