Closed
Bug 292532
Opened 20 years ago
Closed 20 years ago
wont startup. starts to run then closes. no errors displayed. nothing in logs.
Categories
(Toolkit :: Startup and Profile System, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: dan, Unassigned)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050414 Build Identifier: firefox wont start - directly downloaded from mozilla.org click firefox to startup. starts to run. then vanishes. no errors. no warnings. nothing in logs. just wont run. and cant figure out what is wrong with it. runing Suse Linux pro v9.3 and the version it came with started having this problem then I downloaded the latest 1.03 from mozilla.org to try and fix it, but it still has the problem. click on icon, shows it is starting up, but the indicator goes away and nothing happens. no errors in any logs. no messages. no warnings. just doesnt work any more. need help diagnosing the problem. Reproducible: Always Steps to Reproduce: 1. click icon. problem reproduces every time 2. 3. Actual Results: it starts to run. it goes away. doesnt run. Expected Results: i expected the firefox window to open. or at least an error or warning or log. but nothing firefox main i guess(?)
| Reporter | ||
Comment 1•20 years ago
|
||
finally got this - from running from command line: INTERNAL ERROR on Browser End: Expected a version > 5! Version = 4 System error?:: No such file or directory
Comment 2•20 years ago
|
||
You changed your UA and the Java plugin kills Firefox. Remove the useragentoverride pref in your prefs.js (profile) or create a new profile. -> invalid (support questions are invalid in bugzilla, pelase use the mozillazine.org Forums for help)
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
| Reporter | ||
Comment 3•20 years ago
|
||
i changed the UA because I was having problems with sites forcing me to use IE, and I really hate sites that do that. thanks that fixed it!
| Assignee | ||
Updated•16 years ago
|
Product: Firefox → Toolkit
You need to log in
before you can comment on or make changes to this bug.
Description
•