Chromium 50 dropped support for externally linking to strp, so this
probably works now, please test.
Be aware of #821154, all video is probably broken with the current upload.
Best wishes,
Mike
Package: chromium
Version: 45.0.2454.85-1
Followup-For: Bug #770659
For the record: bug still present in Chromium 45.
Paride
Package: chromium
Version: 44.0.2403.107-1
Followup-For: Bug #770659
Dear Maintainer,
given what has been said in the upstream bug discussion, especially
https://code.google.com/p/chromium/issues/detail?id=501318#c37
it seems the usage of use_system_libsrtp is heavily discouraged, the
option
control: forcemerge -1 791429
control: forwarded -1 http://crbug.com/501318
For anyone caring deeply about this bug, helping upstream figure out
the problem is the right way to go (see above). Using embedded srtp is
not an acceptable solution.
Good luck!
Best wishes,
Mike
--
To UNSUBSCRIBE,
I appreace the interested of Paride about this bug
We are talking about months...MONTHS...The WebRTC is a cornerstone of
modern browsers and is inconceivable ignore this)
This took me several weeks ago to back into mozilla (i'm sure many people
changed browser)
I wonder why the maintainers of
I agree: this is the Debian package of the browser that has by far the
highest usage share, see:
https://en.wikipedia.org/wiki/Usage_share_of_web_browsers#Summary_tables
it's not a niche project of some Free Software integralist (like me).
After years we have finally an open standard for real
Package: chromium
Version: 44.0.2403.89-1
Followup-For: Bug #770659
Bug still present in 44.0.2403.89-1:
[156:429:0723/111036:ERROR:webrtcsession.cc(1202)] ConnectDataChannel called
when data_channel_ is NULL.
[156:438:0723/111036:ERROR:process_thread_impl.cc(31)] TimeUntilNextProcess
returned
Package: chromium
Version: 43.0.2357.130-1
Followup-For: Bug #770659
Dear Maximilian,
First of all I confirm that the bug is still present in 43.0.2357.130-1.
I really hope that this can be fixed with chromium 44, as today the support
for WebRTC is far superior in chrome/chromium with respect to
If it may help to fix this bug: WebRTC from the Chromium package
available on Ubuntu 15.04 works fine. Maybe the solution can be borrowed
from there...
Paride
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
If it may help to fix this bug: WebRTC from the Chromium package
available on Ubuntu 15.04 works fine. Maybe the solution can be borrowed
from there...
Paride
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Debian Testing/Stretch
Chromium browser (43.0.2357.65)
This Bug is *STILL* present of chromium
Debian Jessie (chromium 42.0.2311.90-1) the bug is still here.
Package: chromium
Version: 39.0.2171.71-2
Followup-For: Bug #770659
I have Chromium 39 and am still getting the unhelpful Couldn't start
the video call because of an error message.
Strangely enough, if I right click and Reload the page, it works.
-- System Information:
Debian Release: 8.0
When I try to start a video call on google hangouts:
Version Chromium : 39.0.2171.71-2
Version of debian: 8.0 Debian Testing
The log report this error:
getrlimit(RLIMIT_NOFILE) failed
[23:23:1226/151659:ERROR:rtc_peer_connection_handler.cc(119)] Native
session description is null.
I can confirm this.
If I remember my tests correctly in all versions of chromium 37 that hit the
Debian archive webrtc was working and in all versions 38 it is broken.
Sadly I have no idea what might be the cause of this.
signature.asc
Description: This is a digitally signed message part.
Package: chromium
Version: 38.0.2125.101-3
Severity: normal
Starting with either chromium 37 or 38, WebRTC voice/video sharing sites
have stopped working, like Google Hangouts, talky.io, appear.in, etc.
The more open sites all say they can't get access to my camera and
microphone, and Hangouts
16 matches
Mail list logo
