Comment 70 for bug 767498
Revision history for this message
| Anthony Harrington (linuxchemist) wrote | #70 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
As comment 67 said:
Folks, the ubuntu5 update will work even without the workaround, and if apport gives you a report about ubuntu5 failing to upgrade that's a wrongly titled bug for the ubuntu3 or ubuntu4 failures. You can ignore those by now.
So, this specific bug was fixed in 1.20.1-0ubuntu5.
Since your bug isn't related to 1.20.1-ubuntu4 or 1.20.1-ubuntu3 (like the title of this report), you could file a new one. Although i'd seriously urge you to read the above comments for solutions. Back when i had this issue, completely removing apport packages and then reinstalling them fixed the issue. Good luck!