644035 - Network connection does not start on Firefox 4.0 startup

Status: RESOLVED DUPLICATE of bug 652440

(Firefox :: General, defect)

Description

[calebtheheretic]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.2.15) Gecko/20110303 Firefox/3.6.15 (.NET CLR 3.5.30729)
Build Identifier: Firefox 4.0

Since i've used Firefox i was used to seeing a network connections screen/windows popping up on Firefox startup asking me wether i want to manually (I decide when and how to connect to the internet, not my programs themselves) connect to the internet via the standard connection (external USB-ADSL modem), but since i "upgraded" to 4.0 it DIDN'T do this any longer, but just did nothing on startup.

So i decided to downgrade to 3.6 until this critical bug is solved for the better.  

I'd be grateful if you'd work on this. 

Reproducible: Always

Steps to Reproduce:
1. Startup Firefox 4.0 
2. Network connection via USB-ADSL-modem does not appear as used to be the case while using 3.6.15 and earlier versions.
 
Actual Results:  
Firefox does nothing. I have to start the connection manually by doubleclicking on the connection icon itself. 

Expected Results:  
Open/popup the connection screen asking me whether i want to connect or not as it did under 3.6.15.

Comment 1

[Ed Morley [:emorley]]

Frank, might this is fallout from bug 620472?

Comment 2

[Frank Yan (:fryn)]

I'm not sure. Cc'ing roc as he may know.

Comment 3

[Robert O'Callahan (:roc) (email my personal email if necessary)]

I'm not sure either.

Comment 4

[Robert O'Callahan (:roc) (email my personal email if necessary)]

(but it probably is.)

Comment 5

[Tim (fmdeveloper)]

Reporter -> Are you still experiencing this issue with the latest version of Firefox 5? Does the issue occur with the latest nightly? http://nightly.mozilla.org/

Would you be willing to try and track down a regression window? http://quality.mozilla.org/docs/bugzilla/guide-to-triaging-bugs-for-firefox/finding-a-regression-window/

Comment 6

[Alice0775 White]

Is this similar to Bug 652440 ?