We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

ActiveTouch General Plugin Container crashes, there is any solution for this?

  • 3 Antworten
  • 8 haben dieses Problem
  • 1 Aufruf
  • Letzte Antwort von mariusft

more options

I'm trying to access a WbEx session which uses this plugin "ActiveTouch General Plugin Container" version 105 Tried with two versions 28.12.2013.820 & 29.1.2014.722

With latest version of Firefox: ESR 31.3.0 & 34.0.5

In both cases the plugin freezes, and I'm prompted to wait or to close the plugin, main problem is that during the freeze all tabs are blocked as well so I can't perform any action.

I'm trying to access a WbEx session which uses this plugin "ActiveTouch General Plugin Container" version 105 Tried with two versions 28.12.2013.820 & 29.1.2014.722 With latest version of Firefox: ESR 31.3.0 & 34.0.5 In both cases the plugin freezes, and I'm prompted to wait or to close the plugin, main problem is that during the freeze all tabs are blocked as well so I can't perform any action.

Ausgewählte Lösung

Seems that a final update from Cisco solved the issue.

Diese Antwort im Kontext lesen 👍 0

Alle Antworten (3)

more options

Just to mention, I've tried restarting the browser, uninstalling the plugin and re-installing, cleaning up the java cache of application same result, even from different workstation.

Chrome browser has no issue on connecting to WebEx

more options

I've been able to discover why it didn't work. I'm behind corporate proxy and with recent update of Firefox something happened when some variables are sent to the application. Same firewall rules works OK with Chrome, but not with Firefox.

more options

Ausgewählte Lösung

Seems that a final update from Cisco solved the issue.