| Summary: | Cannot enter JITSI room with Chrome/ium - blue button dead | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Riccardo Poleggi <poleggi.riccardo> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | 8 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | https://community.jitsi.org/t/cannot-enter-jitsi-room-in-chrome-and-mageia-8-fresh-installation/111880 | ||
| Whiteboard: | |||
| Source RPM: | chromium-browser-stable-97.0.4692.99-1.mga8.src.rpm | CVE: | |
| Status comment: | |||
|
Description
Riccardo Poleggi
2022-03-05 10:48:16 CET
Not able to reproduce this error. kernel-desktop-5.16.10-2.mga8 (backports) chromium-browser-97.0.4692.99-1.mga8 -> meet.jit.si works kernel-desktop-5.15.23-1.mga8 chromium-browser-97.0.4692.99-1.mga8 -> meet.jit.si works kernel-desktop-5.16.10-2.mga8 (backports) Google Chrome 99.0.4844.51 -> meet.jit.si works kernel-desktop-5.15.23-1.mga8 Google Chrome 99.0.4844.51 -> meet.jit.si works What happens when you install jitsi-2.10.5550-10.mga8? Are you able to join any room? And here is the link to the discussion at jitsi community: https://community.jitsi.org/t/cannot-enter-jitsi-room-in-chrome-and-mageia-8-fresh-installation/111880 URL:
(none) =>
https://community.jitsi.org/t/cannot-enter-jitsi-room-in-chrome-and-mageia-8-fresh-installation/111880 And if it don't even work with an upstream Google Chrome (not shipped with Mageia) and an upstream Chromium, i strongly believe that this is no Mageia problem. First of all, thank you for your time! > Not able to reproduce this error. > > What happens when you install jitsi-2.10.5550-10.mga8? Are you able to join > any room? That puzzles me... I don't have a JITSI-Chrome/ium combination working in any new installation of Mageia8... Still I have all my old PCs working just fine with different hardware (i5 and i7) I installed jitsi-2.10.5550-10.mga8 (VOIP client) and checked again: nothing happened. If I launch Chromium from Konsole, though, I get A LOT of these errors: libpng warning: iCCP: CRC error [14005:14014:0305/170834.301125:ERROR:ssl_client_socket_impl.cc(996)] handshake failed; returned -1, SSL error code 1, net_error -107 I don't know if they are related. JITSI installation had these dependencies: jitsi 2.10.5550 10.mga8 x86_64 x11-font-type1 1.0.0 16.mga8 noarch x11-font-xfree86-type1 1.0.4 9.mga8 noarch java-1.8.0-openjdk 1.8.0.312.b> 2.1.mga8 x86_64 java-1.8.0-openjdk-headless 1.8.0.312.b> 2.1.mga8 x86_64 but none of them did the trick. (In reply to sturmvogel from comment #2) > And here is the link to the discussion at jitsi community: > https://community.jitsi.org/t/cannot-enter-jitsi-room-in-chrome-and-mageia-8- > fresh-installation/111880 Yes, I know: I opened it... (In reply to sturmvogel from comment #3) > And if it don't even work with an upstream Google Chrome (not shipped with > Mageia) and an upstream Chromium, i strongly believe that this is no Mageia > problem. And that will leave me just stuck....;-( Could you give more informations please. I tried several installation combinations in a VB and was still not able to reproduce this behaviour. - which desktop environment do you use? - did you chose special packages whilst installation (i did several minimal installations. Nothing more than Plasma was ticked)? - do you use any chrome/chromium extensions/addons? - do you use a proxy/VPN/special DNS settings? - fresh /home partition (i assume so if you did a VB installation)? - ... (In reply to sturmvogel from comment #7) > Could you give more informations please. I tried several installation > combinations in a VB and was still not able to reproduce this behaviour. > > > - which desktop environment do you use? Plasma 5.20.4 > - did you chose special packages whilst installation (i did several minimal > installations. Nothing more than Plasma was ticked)? In the last VB installation only plasma ticked > - do you use any chrome/chromium extensions/addons? Nope I just installed chromium-browser-stable from repositories I didn't install any extensions/addons > - do you use a proxy/VPN/special DNS settings? I do have a proxy: 192.168.1.254:8080 (Mageia8 with squid/e2guardian) The older working PC has it too. > - fresh /home partition (i assume so if you did a VB installation)? Yep > - ... PS: my IP is in the e2guardian exceptioniplist... (In reply to Riccardo Poleggi from comment #4) > If I launch Chromium from Konsole, though, I get A LOT of these errors: > [14005:14014:0305/170834.301125:ERROR:ssl_client_socket_impl.cc(996)] > handshake failed; returned -1, SSL error code 1, net_error -107 (In reply to Riccardo Poleggi from comment #8) > > - do you use a proxy/VPN/special DNS settings? > I do have a proxy: 192.168.1.254:8080 (Mageia8 with squid/e2guardian) > The older working PC has it too. I'm not sure if there is a relation between this two points above. Could you test a setup without this proxy and web filtering stuff? When i read the description of e2guardian i want to start crying. This "security solutions" with such "features" are most likely to create such problems as you have. That did the trick! Without the proxy (I connected through a WIFI to bypass it) Chrome and Chromium worked as expected and I could connect to a JITSI room. It doesn't explain, though, why the old PC is working like a charm through the same e2guardian/squid configuration, nor why Windows/Chrome on the same PC and proxy config has no problems. However, I now have a workaround and can start digging on the e2guardian/squid configuration. Thank you so much! If you have any hints about it, please don't restrain yourself! ;-) Otherwise, we can consider this "bug" "SOLVED"... Thank you again! Closing then. Sidenote: At my former job many commissioning engineers and software developers where constantly cursing because of such "security solutions". We had to spent more time on bypassing this company security crap to get our normal job done: connecting to measuring devices and other electronics. Forgot to close :) Status:
NEW =>
RESOLVED THKS! |