Where did you install Firefox from? Help Mozilla uncover 3rd party websites that offer problematic Firefox installation by taking part in our campaign. There will be swag, and you'll be featured in our blog if you manage to report at least 10 valid reports!

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

Wannan tattunawa ta zama daɗaɗɗiya. Yi sabuwar tambaya idan ka na bukatar taimako.

Firefox 3.6.3 always exits immediately on CentOS after a normal quit.

  • 1 amsa
  • 2 sa na da wannan matsala
  • 14 views
  • Amsa ta ƙarshe daga AnonymousUser

more options

Our sysadmins upgraded firefox from 3.5.7 to 3.6.3 a little over a month ago. Since then, when I try to start firefox 3.6.3 after a normal quit from it it immediately exits with status code 1. I can still run firefox 3.5.7 which starts and runs ok. Furthermore, if I quit from 3.5.7, 3.6.3 will then start and run ok. This seems to be the only way to get 3.6.3 to run.

Crash ID(s)

bp-a32dec10-9e76-4953-af02-00b4e2100603 06/03/2010 11:03 AM bp-60e56aee-9193-4549-8c7a-eee482091229 12/29/2009 04:48 PM bp-a80e3e01-817d-49d9-ad4b-137da2091113 11/13/2009 06:12 PM

Our sysadmins upgraded firefox from 3.5.7 to 3.6.3 a little over a month ago. Since then, when I try to start firefox 3.6.3 after a normal quit from it it immediately exits with status code 1. I can still run firefox 3.5.7 which starts and runs ok. Furthermore, if I quit from 3.5.7, 3.6.3 will then start and run ok. This seems to be the only way to get 3.6.3 to run. == Crash ID(s) == bp-a32dec10-9e76-4953-af02-00b4e2100603 06/03/2010 11:03 AM bp-60e56aee-9193-4549-8c7a-eee482091229 12/29/2009 04:48 PM bp-a80e3e01-817d-49d9-ad4b-137da2091113 11/13/2009 06:12 PM

All Replies (1)

more options

I experienced about the same problem.

What I did was running firefox in "safe-mode" (firefox -safe-mode). I disabled all add-ons. After that I activated the add-ons one-by-one and found out that in my situation the VMWare-add-on was causing the problem.