Darnit, now my brand new Ubuntu 9.04 installation is having the same
problem! Does a proxy have something to do with this?
** Summary changed:
- 'Bad header line' error trying to update breezy/dapper
+ 'Bad header line' error when trying to use apt
--
'Bad header line' error when trying to use
I am also getting 'bad header line' and 'got a single header line over
360 chars' in both my ubuntu 8.10 and my linux mint 7.0 while using
apt/synaptic. It usually only appears while downloading anything related
to KDE(though there are some exceptions)...
** Changed in: apt (Ubuntu)
I also get this on Dapper.
When I use telnet, it is easy to see that the header it is complaining about is
generated by Apache.
In my case, the first three characters of the Content-Encoding: header are
garbage.
This may be an apache bug.
--
'Bad header line' error trying to update
I can't reproduce this any more... something in the archive changed over
the last week, and it now works. For the record, up until then it was
100% reproducible for the linux-image-686 package as described above.
...
--
'Bad header line' error trying to update breezy/dapper
Standard error debug related to the previous comment above.
** Attachment added: apt-get stderr output
http://librarian.launchpad.net/4555335/apt-fetch-stderr.log
--
'Bad header line' error trying to update breezy/dapper
https://launchpad.net/bugs/26083
--
ubuntu-bugs mailing list
I get this running dapper with apt 0.6.43.3ubuntu when running apt-get
on the package linux-image-686.
As requested by Michael, I have attached the stdout and stderr for the
apt-get debug.
If you would like me to test anything else, please let me know.
It does not happen on every package, just
The bug has struck me on dapper 6.06(.1) with nginx as web server on frontend
and newer nginx on backand.
It don't appear then connecting directrly to a newer one on localhost.
--
'Bad header line' error trying to update breezy/dapper
https://launchpad.net/bugs/26083
--
ubuntu-bugs mailing
