Bugzilla – Bug 383702
eclipse/xulrunner: security component waring
Last modified: 2008-09-16 09:24:02 UTC
When I run eclipse on Beta1+ I get a dialog with the following text on my screen: "Could not initialise the application's security component. The most probable cause is problems with files in your browser's profile directory. Please check that this directory has no read/write restrictions and your hard drive is not full or close to full. It is recommended that you exit the browser and fix the problem. If you continue to use this browser session, you might see incorrect browser behaviour when accessing security features." I don't know what component this dialog belongs to... sounds like xulrunner, which is used as the internal browser of eclipse???
This seems to be indeed a xulrunner issue. If I uninstall xulrunner via YaST2 and restart eclipse, the warning dialog does not appear.
I have no idea how eclipse embeds xulrunner components but probably they are doing something wrong. So for example can anyone enlighten me how Eclipse finds the mozilla components?
is eclipse 32bit or 64bit? if its 32bit, you perhaps need the -32bit packages.
I have the 64bit eclipse-archdep packages installed and the 64bit firefox+xulrunner packages too.
https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/188380 suggests that Eclipse is broken. https://bugs.eclipse.org/bugs/show_bug.cgi?id=206432 says it's fixed with Eclipse 3.4 Someone listening on bnc-team-java?
*** Bug 398531 has been marked as a duplicate of this bug. ***
As this bug is not fixed by now and probably won't until the final release, I plead tho mark this bug as one of the most annoying bugs for the 11.0 release. Currently the user has to decide if he/she want's to install (and use) firefox OR eclipse.
to me this issue is severe: I use eclipse as IDE and firefox as my browser - I suppose a lot of people use this combination. If I can't use these to applcations this is a killer! on comment#7: No chance to have this fixed for 11.0 (or at least with an early package upgrade)?
Has this been silently fixed by now? I don't experience this issue any longer.
There will be Eclipse 3.4 in openSUSE 11.1 which was already fixed by upstream. For older openSUSE releases please use workaround described in https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/188380