Chromium, in Linux, can't send to Chromecast?

[BloodyIron 24]

Hi Folks,

 

I'm on Ubuntu 16.10 using Chromium "Version 55.0.2883.87 Built on Ubuntu , running on Ubuntu 16.10 (64-bit" as my test here.

 

When I'm in my Emby ecosystem, I see the Chromecast icon in the various places one would expect (top left and such). However, when I click on it, the only option I see is to send to Chrome v55, but no Chromecast option.

 

Now the reason I know this is generally localised to Chromium is when I open up Chrome on the same computer "Version 55.0.2883.87 (64-bit)", and try to do the same thing, I get the option "Chromecast" in the list now, and can then proceed to selecting which Chromecast I want to send to.

 

Can anyone please advise what's going on? Is my Chromium missing something, or is this perhaps an issue with Emby?

 

Thanks!

[Luke 42077]

Possibly some good reading:

 

http://www.omgubuntu.co.uk/2016/09/google-axes-chromecast-support-in-chromium-controversy

[BloodyIron 24]

But, but, when I read the bug report it talks about ( https://bugs.chromium.org/p/chromium/issues/detail?id=634168 ), it seems my Chromium version is already higher than what should have the fix in it! I'm now rather confused D:

 

 

Possibly some good reading:

 

http://www.omgubuntu.co.uk/2016/09/google-axes-chromecast-support-in-chromium-controversy

[Luke 42077]

did you read every word?

[BloodyIron 24]

I tried to, and I re-read it as best I could, and I'm still unsure which version actually has the fix.

 

For example, comment 29 ( https://bugs.chromium.org/p/chromium/issues/detail?id=634168#c29 ) says : "I don't see this on 55.0.2868.3"

 

Which could mean:

 

1. I don't see the error any more.

2. I don't see the page they're referring to.

 

Either way that number is lower than my version.

 

I appreciate your expedient responses here, and I'm still confused

 

 

did you read every word?

[Luke 42077]

Well the last post about the security settings might be relevant.

[BloodyIron 24]

I am having a pain of a time finding how to modify the Content Security Policy (CSP). Am I to assume it's baked-in? (aka, compiled in?).

 

Honestly I glossed over that last comment because I thought the issue was resolved earlier in the bug tracking. I see now that the "chrome:" syntax isn't included in the CSP whitelist, but I can't for the life of me find how to modify that (I assume without recompiling Chromium).

Considering that last comment was Sept, I'm a bit in awe that the bug tracking hasn't been updated since (obviously not even close to your involvement, but just commenting here).

 

So, I sit on my hands till a Chromium build comes to me with the whitelisting fix for CSP, or?

 

 

Well the last post about the security settings might be relevant.

[Luke 42077]

Sorry, I mis-read that, or rather I failed to read the whole thing myself. Yes CSP is baked in. In the near future I will be trying to get chromecast to work with Emby Theater on Windows, which embeds chromium. So once I've looked at that we'll see where this stands after that.

[BloodyIron 24]

Cool beans! If there's any way I can help, please let me know

 

Sounds like I just need to sit on my hands for now. Thanks for this chat!

 

 

Sorry, I mis-read that, or rather I failed to read the whole thing myself. Yes CSP is baked in. In the near future I will be trying to get chromecast to work with Emby Theater on Windows, which embeds chromium. So once I've looked at that we'll see where this stands after that.