Corrupted /var/lib/dpkg/status during update to 6.10

Bug #69215 reported by Alex Mayorga
4
Affects Status Importance Assigned to Milestone
dpkg (Ubuntu)
Invalid
Undecided
Unassigned
update-manager (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: update-manager

My update crashed and I was instructed by the error to report it.
So I'm doing it.

I was updating from 6.06 to 6.10

Tags: edgy-upgrade
Revision history for this message
Alex Mayorga (alex-mayorga) wrote :
Revision history for this message
Alex Mayorga (alex-mayorga) wrote :
Revision history for this message
Alex Mayorga (alex-mayorga) wrote :
Changed in update-manager:
status: Unconfirmed → Confirmed
description: updated
Revision history for this message
Michael Vogt (mvo) wrote :

This is what caused the error:

dpkg: parse error, in file `/var/lib/dpkg/status' near line 17602 package `firefox-gnome-support':
 `Depends' field, invalid package name `l)bfontconfig1': character `)' not allowed - only letters, digits and -+._ allowed
Traceback (most recent call last):
  File "/usr/lib/python2.4/logging/__init__.py", line 740, in emit
2.0-0ubuntu1_i386.deb) ...
    self.flush()
  File "/usr/lib/python2.4/logging/__init__.py", line 718, in flush
    self.stream.flush()
IOError: [Errno 9] Bad fi

So it looks like the /var/lib/dpkg/status file gots corrupted during the upgrade. This might be a bug in dpkg, but it is more likely that there is some sort of hardware problem/filesystem corruption here. Does a memtest runs ok? Does checking the filesystem tells anything about problems there?

Thanks,
 Michael

Changed in update-manager:
status: Confirmed → Unconfirmed
Ian Jackson (ijackson)
Changed in dpkg:
status: Unconfirmed → Needs Info
Revision history for this message
Alex Mayorga (alex-mayorga) wrote :

Running the meemtest right now.
Please let me know the commands to check the filesystem.

Thanks,
Alex

Revision history for this message
Alex Mayorga (alex-mayorga) wrote :

Michael,

memtest found some bits of bad memory on this laptop. After many tries of dist-upgrade I'm back on a functional system. So let me know if there's anything I can upload to confirm/close this one.

Also I wonder if theres a bug dealing with BadRAM in Ubuntu.

Thanks,
Alex

Revision history for this message
Ian Jackson (ijackson) wrote :

Thanks for that information. Bad memory might well cause these symptoms so I think there probably isn't a bug in the software here.

Changed in update-manager:
status: Unconfirmed → Rejected
Revision history for this message
Ian Jackson (ijackson) wrote :

Thanks for that information. Bad memory might well cause these symptoms so I think there probably isn't a bug in the software here.

Changed in dpkg:
status: Needs Info → Rejected
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.