Closed
Bug 561750
Opened 14 years ago
Closed 11 years ago
Firefox starts only if previously run in safe-mode if some extensions are enabled
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: lukost, Unassigned)
References
Details
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.3) Gecko/20100423 Gentoo Firefox/3.6.3 Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.3) Gecko/20100423 Gentoo Firefox/3.6.3 Firefox exits with -1 exit status just after running it with no error message (before any window shows up) . If you run Firefox in safe-mode (clicking 'Quit' button on safe-mode menu suffices), Firefox would load normally for 1 time. After closing FF you have to pass through safe-mode to run it again. The problem is connected with extensions, as if none are enabled it does not occure at all. Specifically this extensions (if enabled) will cause Firefox not to start at all if not run after safe-mode: ReadItLater, CookieSafe, DownThemAll, WiredMarker (all current versions). Any other extension other than dictionaries would cause it to happen from time to time (I have checked TabMixPlus, Zotero, FireBug, DictionaryTooltip, AdblockPlus, each installed separetly on clean profile). All the extensions work fine, if Firefox starts - i.e. once after each safe-mode. Reproducible: Always Steps to Reproduce: 1. Run: firefox 2. Close all windows 3. Run: firefox Actual Results: Application exits with exit status -1 and no error message Expected Results: Open FF window Running firefox -safe-mode and clicking the 'quit' button allows to run firefox 1 time.
I have checked it more properly - if you delete or change compatibility.ini, so that FF checks for compatibility, it starts normally and all the plugins are working. There is no need of entering safe-mode, you only have to force compatibility check.
Comment 3•13 years ago
|
||
Can you still reproduce this bug in Firefox 6? Please update to Firefox 6 or later, update your plugins, and retest in a new profile. If you still see the issue with the updated version of Firefox, please post here. Otherwise, please close as RESOLVED > WORKSFORME.
Comment 4•11 years ago
|
||
Marking as incomplete since nobody answered comment 3. Please reopen the bug if you can still reproduce it on a current Firefox version (23, 24, 25) and give the necessary details.
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•