Closed Bug 554825 Opened 15 years ago Closed 14 years ago

Extra Timeout Popups

Categories

(MailNews Core :: Networking: NNTP, defect)

Product:
MailNews Core
Component:
Networking: NNTP
Platform:
x86
All
Type:
defect
Priority:
Not set
Severity:
minor

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: david, Unassigned)

Details

(Whiteboard: [closeme 2011-12-15])

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.8) Gecko/20100205 SeaMonkey/2.0.3 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3 If I attempt to open a newsgroup account when the news server is sluggish or not responding, I get a timeout popup. When I acknowledge the popup, I get a second timeout popup. One should be sufficient. Reproducible: Always
Component: General → Mail Window Front End
QA Contact: general → front-end
(In reply to comment #0) > I get a timeout popup. When I acknowledge the popup, I get a > second timeout popup. One should be sufficient. David, please post the exact wording of the error message. And, do you still see this in version 3.1 or trunk build?
OS: Windows XP → All
Whiteboard: [dupeme?]
The only way I can recreate this is with a dial-up connection (which I can do) and a very busy NNTP server (which I cannot contrive). Tomorrow afternoon, I will try using Thunderbird with a dial-up connection after not viewing newsgroups overnight and in the morning.
this needs more details/information before it should be considered "new"
Status: NEW → UNCONFIRMED
Component: Mail Window Front End → Networking: NNTP
Ever confirmed: false
Product: Thunderbird → MailNews Core
QA Contact: front-end → networking.nntp
Whiteboard: [dupeme?] → [closeme 2011-12-15]
Mozilla/5.0 (Windows NT 5.1; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 The way Thunderbird now notifies the user of a timeout, this no longer occurs.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.