Join the Mozilla’s Test Days event from Dec 2–8 to test the new Firefox address bar on Firefox Beta 134 and get a chance to win Mozilla swag vouchers! 🎁

Поиск в Поддержке

Избегайте мошенников, выдающих себя за службу поддержки. Мы никогда не попросим вас позвонить, отправить текстовое сообщение или поделиться личной информацией. Сообщайте о подозрительной активности, используя функцию «Пожаловаться».

Подробнее

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

  • 3 ответа
  • 8 имеют эту проблему
  • 13 просмотров
  • Последний ответ от 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.

Выбранное решение

Seems that a final update from Cisco solved the issue.

Прочитайте этот ответ в контексте 👍 0

Все ответы (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

Выбранное решение

Seems that a final update from Cisco solved the issue.