User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b5) Gecko/2008043010 Fedora/3.0-0.60.beta5.fc9 Firefox/3.0b5 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b5) Gecko/2008043010 Fedora/3.0-0.60.beta5.fc9 Firefox/3.0b5 I have fresh install of FC 9 that comes preloaded with firefox3.0.beta5. I had a machine crash due to shutdown of the NIS server with firefox opened. On restarting firefox it gave the usual message "Another firefox is running". I cleared up the profile files and started my FF. It starts up but with the entire upper region with the exception of home button is inactive. The address bar and google bar does not respond anymore while all other icons are greyed out. I tried reinstalling FF but the same error recurs. This does happens when I work as the root user. I have no clue on why this happens. Reproducible: Didn't try Steps to Reproduce: 1.It happened due to a hard boot of the machine with firefox opened. Actual Results: 1.address bar has become inactive 2.google bar is inactive 3.All buttons in the toolbar with exception of home and tab have greyed out. As a root user i do not have the above said problems. It works normally. I feel there is some configuration file located outside .mozilla that brings about this problem. I tried moving all user config files and restarting FF but the same problem repeated.
Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe mode or a fresh profile? If not, please close. These links can help you in your testing. http://support.mozilla.com/kb/Safe+Mode http://support.mozilla.com/kb/Managing+profiles
Whiteboard: [notacrash] → [CLOSEME 2011-2-25]
This bug has had the CLOSEME tag for several weeks and the date in the tag is far gone. If the reporter can still see this issue, Please retest with Firefox 3.6.x or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). Then please remove the closeme tag in the whiteboard, mark the bug against the proper version and comment on the bug.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.