Your message dated Sun, 11 Sep 2016 17:46:36 -0400
with message-id
<CANTw=mnlqks9kwj_50r0su56md97mgbs0nfrtevcx08kflm...@mail.gmail.com>
and subject line re: chromium: Chromecast device not found after update to 52.
has caused the Debian Bug report #833477,
regarding chromium: Chromecast device not found after update to 52.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
833477: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833477
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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 libavformat57 7:3.1.1-3
ii libavutil55 7:3.1.1-3
ii libc6 2.23-4
ii libcairo2 1.14.6-1+b1
ii libcups2 2.1.4-4
ii libdbus-1-3 1.10.8-1
ii libexpat1 2.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-keyring0 3.12.0-1+b1
ii libgtk2.0-0 2.24.30-4
ii libharfbuzz0b 1.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 libpulse0 9.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-utils 7.7+3
ii xdg-utils 1.1.1-1
Versions of packages chromium recommends:
ii fonts-liberation 1.07.4-1
Versions of packages chromium suggests:
pn chromium-l10n <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
version: 53.0.2785.89-1
The upstream bug indicates that this is fixed in chromium 53. Please
reopen if not.
Best wishes,
Mike
--- End Message ---
