Comment 3 for bug 63850
Revision history for this message
| Thomas Folz-Donahue (eigenlambda) wrote | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
I'm posting this here because the solution to this bug is not actually the same as the solution to the one it's flagged as a dupe of, and you asked here.
What happens now is
Reading package lists... Error!
E: Encountered a section with no Package: header
E: Problem with MergeList /var/lib/
E: The package lists or status file could not be parsed or opened.
I didn't delete those files, though, I just shoved them to my home directory in the hopes of examining them or the conditions of the bus error more thoroughly in the future. Why do you say that it would be hard to print a real error message instead of crashing? It seems to me that catching SIGSEGV or SIGBUS and printing something wouldn't be too hard.
...So I just moved them back, expecting another bus error, and I still got a decent error message... and didn't get any error on my next apt-get update. That's actually kind of frustrating. Problems shouldn't just go away like that.