Open Bug 478793 Opened 17 years ago Updated 2 years ago

Resuming of downloads mostly fail if multiple network connections are used

Categories

(Toolkit :: Downloads API, defect, P3)

Product:
Toolkit
Component:
Downloads API
Type:
defect

Tracking

()

People

(Reporter: whimboo, Unassigned)

References

(
URL
)

Details

(Keywords: dataloss)

Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1b3pre) Gecko/20090215 Shiretoko/3.1b3pre Ubiquity/0.1.5 ID:20090215020429 This is a spun-off from bug 436382. This bug is about download failures when trying to resume a download while multiple network connections are in use. * Resuming a paused download will fail when having multiple network connecions activated. Enable your WIFI adapter and connect to a network while the network cable is connected too. When you start a download now and remove the cable we don't switch into the pause state and when plugging the cable in again, we fail. * Also failures happen when trying to resume a download when I remove the network cable for about a minute. The download is paused correctly, but when we want to resume I get the failure: C:\Dokumente und Einstellungen\henrik\Desktop\ubuntu-8.10-desktop-i386.iso could not be saved, because the source file could not be read. Try again later, or contact the server administrator. Having big downloads this causes a dataloss. You have to start from the beginning again.
Depends on: 436382
This really has more to do with necko than the download manager.
Component: Download Manager → Networking
Product: Toolkit → Core
QA Contact: download.manager → networking
Version: 1.9.1 Branch → Trunk
How is this a necko issue? DL manager should resume the download when it gets a network error.
Component: Networking → Download Manager
Product: Core → Toolkit
QA Contact: networking → download.manager

In the process of migrating remaining bugs to the new severity system, the severity for this bug cannot be automatically determined. Please retriage this bug using the new severity system.

Severity: major → --

The severity field is not set for this bug.
:mak, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(mak)

Would be nice to verify if this is still an issue nowadays.

Severity: -- → S3
Flags: needinfo?(mak)
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.