Steps to reproduce:
1) set the chrome and firefox to use different proxy setting
due to 7168102, proxy setting in /root/.mozilla may be need to set to be different from chrome's. (chrome's proxy is through system's setting)
2) launch any applet in chrome with java console enabled, if it says plugin uses proxy setting for firefox rather for chrome, bug is reproduced.
1) set the chrome and firefox to use different proxy setting
due to 7168102, proxy setting in /root/.mozilla may be need to set to be different from chrome's. (chrome's proxy is through system's setting)
2) launch any applet in chrome with java console enabled, if it says plugin uses proxy setting for firefox rather for chrome, bug is reproduced.