On 1 April 2010 12:13, David García Granda <dgranda@xxxxxxxxx> wrote: > Hi Don, > >> Yesterday I updated to kernel 2.6.32.9.70 fc12 and to firefox-3.5.9-1.fc12 and now firefox won't start. I get a notice in the bottom bar for a few seconds and then it goes blank. > > Strange, I have the same package versions and firefox runs fine... > >> I tried starting firefox in a terminal and it returned "can't load XPCOM" >> I tried 'locate XPCOM' and it returned some files in /usr/lib/VirtualBox and /usr/lib/xulrunner-1.9.1/modules/XPCOMUtils.jsm > > Uhmmm... I don't have virtualbox installed, so this can make the difference. > >> I have VirtualBox installed, but I am not trying to run firefox in virtualBox, but on the desktop. >> I just found that xulrunner-1.9.1.9-1.fc12 was installed at the same time as the new firefox so I suspect the problem is between firefox and xulrunner. > > I think the problem here is VirtualBox. > It is improper methodology to start blaming other "most unlikely" packages before going through the proper troubleshooting steps. I don't have VBox installed and that file is there in my system. xulrunner is what firefox uses for all of its UI and configuration. (at least that is what I know) $ yum deplist firefox | grep xul provider: xulrunner.x86_64 1.9.1-0.20.beta4.fc11 provider: xulrunner.x86_64 1.9.1.9-1.fc11 dependency: libxul.so()(64bit) provider: xulrunner.x86_64 1.9.1-0.20.beta4.fc11 provider: xulrunner.x86_64 1.9.1.9-1.fc11 dependency: xulrunner >= 1.9.1.9 provider: xulrunner.x86_64 1.9.1.9-1.fc11 provider: xulrunner.i586 1.9.1.9-1.fc11 provider: xulrunner.x86_64 1.9.1-0.20.beta4.fc11 provider: xulrunner.x86_64 1.9.1.9-1.fc11 dependency: libxul.so()(64bit) provider: xulrunner.x86_64 1.9.1-0.20.beta4.fc11 provider: xulrunner.x86_64 1.9.1.9-1.fc11 provider: xulrunner.x86_64 1.9.1-0.20.beta4.fc11 provider: xulrunner.i586 1.9.1-0.20.beta4.fc11 >> I don't know what to try next. I have been using fc12 for a long time successfully for quite a while Any help or advice would be appreciated. > > Is it possible for you to check if XPCOM files related from VirtualBox > conflict with Firefox/xulrunner ones?. Maybe something not compatible > from VirtualBox is loaded instead of the right one. > The OP should first try 1. starting firefox in safe mode `firefox -safe-mode' and see whether any of the add-ons are to blame. 2. If that doesn't work, try looking for unreleased lock files for firefox. $ cd ~/.mozilla $ find -type f -name '*lock' If any are found delete them and try again. 3. If none of the above works try creating a new user and start firefox there. And finally if none of the above work appeal to the collective knowledge of the list with the results from the above. > HTH, > > David -- Suvayu Open source is the future. It sets us free. -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
