Chromium/Chromecast: can't find device

moewb · 2016-12-19 22:36:43

Hi there!

It seems that Chromium decided to include a native feature for casting to a Chromecast in the version 52. There is a bug reported there where that native feature and the historical extension for that purpose are conflicting. Disabling the native feature apparently solved the problem for most of the impacted users, but it doesn't work for me
With the native feature on, neither the native feature nor the extension find any device. With the native feature disabled, the extension finds my device, but when I try to cast content, I get a message on the TV where my Chromecast is plugged in telling me that the connection with the casting machine has stopped

Does anyone has experienced a similar issue or/and have an idea where the problem could come from?

Last edited by moewb (2017-03-03 23:14:31)

woodape · 2016-12-20 06:28:25

I had a similar issue a little over a month ago, and just switched to google-chrome instead which worked fine. There is a bug report here relating to the issue. It has apparently been fixed upstream, but this may not have filtered down into the stable version yet. Have you tried the chromium-dev or snapshot version in the AUR? They're one major version ahead of the chromium in extra and might have the fix merged in.

Last edited by woodape (2016-12-20 06:28:51)

bulletmark · 2016-12-20 07:45:17

moewb wrote:

Does anyone has experienced a similar issue or/and have an idea where the problem could come from?

Yep, I suddenly started to see this same problem and like you I went looking some time ago and found the issue and supposed solution. However, also like you I found that disabling the media-router flag enabled me to see the device but it then always fails when I try to cast (from either my Arch PC or my laptop)

I've just been waiting for a fix to roll in to stock chromium but it has been a long time. It's really annoying to lose casting ability.

moewb · 2016-12-20 14:43:29

woodape, bulletmark, thanks for your answer!

Have you tried the chromium-dev or snapshot version in the AUR?

Nop, I haven't tried. I try to stick to stable versions as much as possible.
There are many issues being referenced in the link you pasted in your message woodape. I hope the issue I'm referring to is one of them. I guess we'll know with v56?

@bulletmark
Let's be patient until the next release

I'll keep an eye on it and update this thread when a new version gets released.

Version currently tested: 55.0.2883.87 (64 bits)

Last edited by moewb (2016-12-20 14:47:21)

bulletmark · 2017-02-02 04:34:49

@moweb, we've recently seen another major version update of chromium to 56 but this bug shows no signs of being fixed. I've reluctantly moved to google-chrome package where casting works fine.

moewb · 2017-02-02 14:40:00

@bulletmark

Thanks a lot for the heads-up. I just installed the update and same result for me: nothing has changed I wonder what's going on with Chromium... The other day, I tried to log in SoundCloud using my Google account, and that Google login thing never showed up whereas it does on Firefox or even Epiphany. I don't know what's going on... =/
I'll keep digging and report here if I ever find something.

moewb · 2017-02-09 02:24:02

The issue has also been reported in the Ubuntu community
https://bugs.launchpad.net/ubuntu/+sour … ug/1621753

moewb · 2017-02-09 02:27:57

On the Chromecast help forum too
https://productforums.google.com/forum/ … jIk-WweayY

moewb · 2017-02-09 02:37:45

There is an issue registered in the Chromium project bug tracker:
https://bugs.chromium.org/p/chromium/is … ?id=655838
I hope they'll fix it soon...

STiAT · 2017-02-25 16:35:42

Actually, Ubuntu somehow has a fix for this since two days ago..

They just didn't share what was the issue, I tried to look at patches submitted recently to chromium but didn't see anything there either. I asked if they're willing to share how it was fixed and what the issue was so other distros can fix it as well.
But Chris mentioned it was a code issue...

moewb · 2017-02-26 01:28:21

@STiAT

Oh, great news, thanks a lot for sharing that
The version of Chromium currently deployed in the Ubuntu repos is 37.0.2062.120. The one in Archlinux repos is still 56.0.2924.87-1, so I guess we just have to wait for a new version to be deployed...
Thanks for letting us know and sharing what you know!

irkdub · 2017-03-01 01:54:42

To resolve this issue you need to enable chrome://flags/#load-media-router-component-extension

Previously you needed to disable chrome://flags/#media-router but that is no longer the resolution to get chromecast functionality in the new build of chromium.

bulletmark · 2017-03-01 23:00:50

irkdub wrote:

To resolve this issue you need to enable chrome://flags/#load-media-router-component-extension

Thanks, I gave up when on chromium at v55 but this new option in v56 from last week seems to work.

moewb · 2017-03-02 00:28:27

irkdub wrote:

To resolve this issue you need to enable chrome://flags/#load-media-router-component-extension
Previously you needed to disable chrome://flags/#media-router but that is no longer the resolution to get chromecast functionality in the new build of chromium.

It works for me too! Thanks a lot for the fix, I can finally use my Chromecast again with Chromium

moewb · 2017-03-03 14:17:05

Hmmm, so it solved the problem but it may also crash Chromium here. I can't be 100% sure about it being related to this but if I enable that flag, Chromium crashes after a few minutes. And when I try to launch it again, the UI shows up, freezes right away for a few second and crashes. I had to delete the ~/.config/chromium folder in order to be able to launch Chromium again without it crashing.
Has anyone encounter this issue as well?

bulletmark · 2017-03-03 21:27:46

@moewb, yep, after posting the above I started to get constant crashes of chromium. Would start and only run for a couple of secs before crashing again. Cleared chromium from ~/.cache and ~/.config but still crashed. Disable all my extensions but no difference. Searched everywhere around the web and forums but found nobody else reporting the issue. Then moved back to google-chrome.

Last edited by bulletmark (2017-03-03 21:29:48)

moewb · 2017-03-03 23:17:49

@bulletmark
Oh? Wow, that sounds like a serious issue... The only thing I can unfortunately tell you is what I did, which is simply removing the whole ~/.config/chromium folder, relaunching Chromium and not setting that flag anymore... =/

I removed the "[Resolved]" part in the title of this thread.

Scimmia · 2017-03-05 15:04:51

https://bbs.archlinux.org/viewtopic.php?id=222506
https://bugs.archlinux.org/task/51832

moewb · 2017-03-13 13:43:08

I just updated to Chromium 57.0.2987.98 and it still doesn't work

sshow · 2017-04-02 21:21:42

You can reset the flag by setting the load-media-router-component-extension flag to 0 again in ~/.config/chromium/Local\ State

$ sed -i -e 's/load-media-router-component-extension@1/load-media-router-component-extension@0/' ~/.config/chromium/Local\ State

Last edited by sshow (2017-04-02 21:22:06)

skein · 2017-09-22 16:45:07

This issue is resolved, as mentioned above. The cast plugin is simply disabled by default. Find this setting by pasting chrome://flags/#load-media-router-component-extension into your address bar.

Scimmia · 2017-09-22 16:46:31

Until it puts your browser into a crash loop

skein · 2017-09-22 16:56:52

I spoke too soon! Yep, my Chromium was totally hosed by enabling cast. I see why developers have disabled it. What's the latest workaround on this? Do we need to compile chromium from source?

gregfrankenstein · 2017-10-02 05:13:20

Is this whole crash loop thing only a risk if you have your startup page set to "continue where you left off"? Or would it still crash upon opening somehow if that wasn't set?

I mean I'd gladly leave it enabled if the worst that could happen is a one-time crash.

Arch Linux

#1 2016-12-19 22:36:43

Chromium/Chromecast: can't find device

#2 2016-12-20 06:28:25

Re: Chromium/Chromecast: can't find device

#3 2016-12-20 07:45:17

Re: Chromium/Chromecast: can't find device

#4 2016-12-20 14:43:29

Re: Chromium/Chromecast: can't find device

#5 2017-02-02 04:34:49

Re: Chromium/Chromecast: can't find device

#6 2017-02-02 14:40:00

Re: Chromium/Chromecast: can't find device

#7 2017-02-09 02:24:02

Re: Chromium/Chromecast: can't find device

#8 2017-02-09 02:27:57

Re: Chromium/Chromecast: can't find device

#9 2017-02-09 02:37:45

Re: Chromium/Chromecast: can't find device

#10 2017-02-25 16:35:42

Re: Chromium/Chromecast: can't find device

#11 2017-02-26 01:28:21

Re: Chromium/Chromecast: can't find device

#12 2017-03-01 01:54:42

Re: Chromium/Chromecast: can't find device

#13 2017-03-01 23:00:50

Re: Chromium/Chromecast: can't find device

#14 2017-03-02 00:28:27

Re: Chromium/Chromecast: can't find device

#15 2017-03-03 14:17:05

Re: Chromium/Chromecast: can't find device

#16 2017-03-03 21:27:46

Re: Chromium/Chromecast: can't find device

#17 2017-03-03 23:17:49

Re: Chromium/Chromecast: can't find device

#18 2017-03-05 15:04:51

Re: Chromium/Chromecast: can't find device

#19 2017-03-13 13:43:08

Re: Chromium/Chromecast: can't find device

#20 2017-04-02 21:21:42

Re: Chromium/Chromecast: can't find device

#21 2017-09-22 16:45:07

Re: Chromium/Chromecast: can't find device

#22 2017-09-22 16:46:31

Re: Chromium/Chromecast: can't find device

#23 2017-09-22 16:56:52

Re: Chromium/Chromecast: can't find device

#24 2017-10-02 05:13:20

Re: Chromium/Chromecast: can't find device

Board footer