User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4 This problem usually occurs when I first start my computer, but it happens at other times as well. I double click firefox from my desktop, and no window opens at all. I must then end the process through the Windows Task Manager, and then execute it again, whereupon it works fine. It might be related to another problem where when I start my computer, I do not connect to my internet connection until I right click the network connection icon in the system tray and hit repair. Maybe firefox cannot connect to the internet so it fails to open? Reproducible: Didn't try Steps to Reproduce: 1. Double click firefox Actual Results: No window opened, but program did run in background Expected Results: Opened the browser window
Does it work if you start Firefox in the Firefox safemode instead of the normal mode ?
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050522 Firefox/1.0+ WFM. Reporter: How long are you waiting before you kill the process, it takes awhile to start up if you have a lot of extensions installed. Please try to reproduce this with a clean profile and then comment on the results of that here. Also, some free advice from me. If you have to repair your network connection everytime you restart your computer, you need to make a startup script that has the following in it (naming and figuring out how to set it to run at startup are your deal though): ::Repair my net connection on startup ipconfig /release [adapter] ipconfig /renew [adapter] :end
Summary: program doe snot appear when executed, must be killed by ending process → program does not appear when executed, must be killed by ending process
Version: unspecified → 1.0 Branch
This usaully happens to me when I close firefox then try to open it again.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.