Bug#833477: chromium: Chromecast device not found after update to 52.

2016-09-26 Thread Jamin
Unless the built-in media router not working is genuinely a bug, can we
consider disabling it by default?


diff -ur a/debian/chromium/etc/chromium.d/default-flags
b/debian/chromium/etc/chromium.d/default-flags
--- a/debian/chromium/etc/chromium.d/default-flags  2016-09-26
20:37:32.036974879 -0700
+++ b/debian/chromium/etc/chromium.d/default-flags  2016-09-26
20:38:13.044976103 -0700
@@ -8,3 +8,6 @@

 # Disable background networking
 export CHROMIUM_FLAGS="$CHROMIUM_FLAGS --disable-background-networking"
+
+# Disable media router (bug #833477)
+export CHROMIUM_FLAGS="$CHROMIUM_FLAGS --media-router=0"


Bug#833477: chromium: Chromecast device not found after update to 52.

2016-09-20 Thread Anthony Callegaro
On Tue, 13 Sep 2016 22:24:31 + Bob Smith  wrote:
> Fix:
> 1. chrome://flags/
> 2. Default -> Disabled
> Media Router Mac, Windows, Linux, Chrome OS
> Enables Chrome to access external presentation-type displays and use
them for presenting web content. #media-router
> 3. Casting will now work so long as you have the official extension
installed
>
> The built-in casting seems to block google's extension. Only solution
so far is to disable the new built-in casting. As far as I know, the
built-in streaming will never work with Chromium. Linux users are now
forced to Chrome or Chromium+disabled built-in casting+extension.
 
Thanks for the workaround it does work this way. Shame we can't use the
builtin one.

Thanks a lot for your help
LeTic



Bug#833477: chromium: Chromecast device not found after update to 52.

2016-09-13 Thread Bob Smith

On Mon, 12 Sep 2016 12:27:27 +0200 Anthony Callegaro  wrote:
> Hey Michael,
> 
> I just tested with the latest Chromium 53.0.2785.92-3 in unstable and
> the result is the same.
> 
> Downgrading back to 51.0.2704.79-1 I can see our offices Nexus Player again.
> 
> Let me know what options I should enable to help troubleshooting this.
> 
> Cheers
> LeTic

Fix:
1. chrome://flags/
2. Default -> Disabled
Media Router Mac, Windows, Linux, Chrome OS
Enables Chrome to access external presentation-type displays and use them for 
presenting web content. #media-router
3. Casting will now work so long as you have the official extension installed

The built-in casting seems to block google's extension.  Only solution so far 
is to disable the new built-in casting.  As far as I know, the built-in 
streaming will never work with Chromium.  Linux users are now forced to Chrome 
or Chromium+disabled built-in casting+extension.


Bug#833477: chromium: Chromecast device not found after update to 52.

2016-09-12 Thread Anthony Callegaro
Hey Michael,

I just tested with the latest Chromium 53.0.2785.92-3 in unstable and
the result is the same.

Downgrading back to 51.0.2704.79-1 I can see our offices Nexus Player again.

Let me know what options I should enable to help troubleshooting this.

Cheers
LeTic



Bug#833477: chromium: Chromecast device not found after update to 52.

2016-08-22 Thread Anthony Callegaro
Dear maintainer,

We are also affected by this internally. We have nexus players in all
our meeting rooms and now all developers using debian testing are
affected and cannot cast anymore (same for all OS X users).

Did you get any update yourself as I see no update on crbugs.com
tracker? Is there an upstream channel (IRC or others) where we could
escalate this bug ?

Thanks in advance
Cheers !

LeTic



Bug#833477: chromium: Chromecast device not found after update to 52.

2016-08-04 Thread Joel Brunetti
Package: chromium
Version: 52.0.2743.82-2
Severity: normal

Dear Maintainer,

After the recent update of chromium from 51 to 52 the browser is no longer able
to find the chromecast device present on the network.

The system that can no longer detect the chromecast was able to prior to the
update.

A second system that has yet to fully receive the update can still detect and
cast to the chromecast device as can a ChromeOS system with Chrome 52.

I have been unable to find good resources on how to debug this problem so my
troubleshooting has been little more than resetting the chromecast and
rebooting the effected system. This did not yield any positive results.

I understand that there have been recent changes that integrated cast support
into Chrome starting at 51 and that those changes appear to have made it into
Chromium 52.

Thanks,
Joel

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages chromium depends on:
ii  libasound2   1.1.1-2
ii  libatk1.0-0  2.20.0-1
ii  libavcodec57 7:3.1.1-3
ii  libavformat577:3.1.1-3
ii  libavutil55  7:3.1.1-3
ii  libc62.23-4
ii  libcairo21.14.6-1+b1
ii  libcups2 2.1.4-4
ii  libdbus-1-3  1.10.8-1
ii  libexpat12.2.0-1
ii  libfontconfig1   2.11.0-6.4
ii  libfreetype6 2.6.3-3+b1
ii  libgcc1  1:6.1.1-10
ii  libgdk-pixbuf2.0-0   2.34.0-1
ii  libglib2.0-0 2.48.1-2
ii  libgnome-keyring03.12.0-1+b1
ii  libgtk2.0-0  2.24.30-4
ii  libharfbuzz0b1.2.7-1
ii  libjpeg62-turbo  1:1.5.0-1
ii  libnettle6   3.2-1
ii  libnspr4 2:4.12-2
ii  libnss3  2:3.23-2
ii  libpango-1.0-0   1.40.1-1
ii  libpangocairo-1.0-0  1.40.1-1
ii  libpci3  1:3.3.1-1.1
ii  libpulse09.0-1.1
ii  libspeechd2  0.8.4-2
ii  libstdc++6   6.1.1-10
ii  libx11-6 2:1.6.3-1
ii  libxcomposite1   1:0.4.4-1
ii  libxcursor1  1:1.1.14-1+b1
ii  libxdamage1  1:1.1.4-2+b1
ii  libxext6 2:1.3.3-1
ii  libxfixes3   1:5.0.2-1
ii  libxi6   2:1.7.6-1
ii  libxml2  2.9.4+dfsg1-1
ii  libxrandr2   2:1.5.0-1
ii  libxrender1  1:0.9.9-2
ii  libxslt1.1   1.1.28-4
ii  libxss1  1:1.2.2-1
ii  libxtst6 2:1.2.2-1+b1
ii  x11-utils7.7+3
ii  xdg-utils1.1.1-1

Versions of packages chromium recommends:
ii  fonts-liberation  1.07.4-1

Versions of packages chromium suggests:
pn  chromium-l10n  

-- no debconf information