Closed
Bug 606634
Opened 15 years ago
Closed 13 years ago
sessionstore.js reset following ethernet adapter change
Categories
(Firefox :: Session Restore, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: acmiddleton, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.8) Gecko/20100722 Firefox/3.6.8 ( .NET CLR 3.5.30729; .NET4.0E)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.8) Gecko/20100722 Firefox/3.6.8 ( .NET CLR 3.5.30729; .NET4.0E)
With firefox open, I disable wireless adapter, and plug in ethernet cable. For reason unknown, this wipes out internet connectivity, though I can still access my intranet which is all I care about and I believe irrelevant to this bug. Anyways, exiting firefox and restarting does not restore previous session/tabs. This is repeatable.
Reproducible: Always
Steps to Reproduce:
1. Disable wireless adapter
2. Connect wired ethernet connection
3. Restart Firefox
Actual Results:
Firefox starts up reporting error connecting to internet. Don't understand why connectivity problem, don't care at moment. Re-enabling wireless adapter restores internet connection.
Expected Results:
Restarting Firefox should restore session/multiple tabs. I just get one tab, loose all other tabs.
(HP CQ61 laptop, Windows 7, x64)
| Reporter | ||
Comment 1•15 years ago
|
||
Correction, this problem is not always repeatable. I have witnessed this twice, however, I just tried again and session resumed as expected.
Comment 2•15 years ago
|
||
If you can reproduce reliably let me know. Until then I highly doubt this is actually related to session restore. We don't care about your ethernet adapter change.
If you think you can reproduce reliably, try again in safe mode (disables extensions). This will make sure it's not actually an extension to blame.
Updated•14 years ago
|
Version: unspecified → 3.6 Branch
Comment 3•13 years ago
|
||
needs more info
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•