Closed
Bug 878466
Opened 12 years ago
Closed 1 year ago
Firefox cannot connect after reverting to no proxy
Categories
(Core :: Networking: Proxy, defect, P3)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: coniliakis.cred, Unassigned)
Details
(Whiteboard: [dupme?][necko-backlog])
Attachments
(1 file)
|
3.62 KB,
text/plain
|
Details |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_5) AppleWebKit/536.29.13 (KHTML, like Gecko) Version/6.0.4 Safari/536.29.13
Steps to reproduce:
I used proxy to connect to university network. After reverted to no proxy use firefox cannot load any page.
Actual results:
Connecting message in statusbar. Message
6/1/13 5:59:07.256 PM [0x0-0x99099].org.mozilla.firefox: WARNING: QApplication was not created in the main() thread.
6/1/13 5:59:09.391 PM [0x0-0x99099].org.mozilla.firefox: QIODevice::seek: The device is not open
in console
Expected results:
Open sites
|
||
Updated•12 years ago
|
Component: Untriaged → Networking
Product: Firefox → Core
|
||
Comment 1•9 years ago
|
||
like bug 1121800?
Flags: needinfo?(coniliakis.cred)
Summary: Firefox cannot connect → Firefox cannot connect after reverting to no proxy
Whiteboard: [dupme?]
|
||
Updated•9 years ago
|
Whiteboard: [dupme?] → [dupme?][necko-backlog]
|
||
Comment 2•8 years ago
|
||
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: -- → P1
|
|
||
Comment 3•8 years ago
|
||
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: P1 → P3
|
||
Updated•3 years ago
|
Severity: normal → S3
|
|
||
Comment 4•1 year ago
|
||
Moving bug to Core/Networking: Proxy.
Component: Networking → Networking: Proxy
|
||
Comment 5•1 year ago
|
||
A needinfo is requested from the reporter, however, the reporter is inactive on Bugzilla. Given that the bug is still UNCONFIRMED, closing the bug as incomplete.
For more information, please visit BugBot documentation.
Status: UNCONFIRMED → RESOLVED
Closed: 1 year ago
Flags: needinfo?(coniliakis.cred)
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•