This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Hierdie gesprek is in die argief. Vra asseblief 'n nuwe vraag as jy hulp nodig het.

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

  • 3 antwoorde
  • 8 hierdie probleem
  • 13 views
  • Laaste antwoord deur 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.

Gekose oplossing

Seems that a final update from Cisco solved the issue.

Lees dié antwoord in konteks 👍 0

All Replies (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

Gekose oplossing

Seems that a final update from Cisco solved the issue.