I don't have a reliable way to reproduce this. It has happened a few
times -- about half a dozen times -- with firefox 3.5b4 and never yet
with firefox-3.0.
MAIN yukyuk:~$ apt-cache policy firefox-3.5
firefox-3.5:
Installed: 3.5~b4~hg20090330r24021+nobinonly-0ubuntu1
Candidate: 3.5~b4~hg20090330r24021+nobinonly-0ubuntu1
Version table:
*** 3.5~b4~hg20090330r24021+nobinonly-0ubuntu1 0
500 http://us.archive.ubuntu.com jaunty/universe Packages
100 /var/lib/dpkg/status
MAIN yukyuk:~$ lsb_release -a
LSB Version:
core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch
Distributor ID: Ubuntu
Description: Ubuntu 9.04
Release: 9.04
Codename: jaunty
I will submit a bug report on the mozilla bugzilla when I get around to
it.
Thanks!
Oh, I think my diagnosis -- that firefox received a 200 success and a
Content-Length and then a short read followed by connection close --
might be wrong. I don't know that for sure. I would have to think
about it more.
--
short read from server results in cached page with the first few bytes
overwritten by the short read result
https://bugs.launchpad.net/bugs/382444
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
