apt package management conflict crash

[stevec]

This is not a serious issue but more of an instance of a crash that should be handled gracefully.

I was logged into 10.04 via SSH via one user account. I was installing packages via aptitude over the command line.

At the same time I switched over to the terminal local to the machine and went into the System->Administration->Software Sources menu and made some adjustments via another user account.

The adjustments seem to have taken, but when I clicked "close" (when it normally updates the apt-cache) it crashed and gave me the apport dialogue.

Again, this is a pretty non-serious issue as most people probably aren't ever even in a position to do this and it was more me abusing the system than a problem with the system--I just figured I'd report it in case there was an easy way to make it catch the error more gracefully (for instance with the dialogue one usually gets if trying to open Software Sources while Update Manager is running).

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-26-generic (not installed)
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: I82801BAICH2 [Intel 82801BA-ICH2], device 0: Intel ICH [Intel 82801BA-ICH2]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: scorenfl 13136 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'I82801BAICH2'/'Intel 82801BA-ICH2 with AD1885 at irq 17'
   Mixer name : 'Analog Devices AD1885'
   Components : 'AC97a:41445360'
   Controls : 38
   Simple ctrls : 27
Date: Fri Dec 3 16:47:10 2010
ErrorMessage: corrupted filesystem tarfile - corrupted package archive
HibernationDevice: RESUME=UUID=255a184e-79a5-4bf2-a724-404e1c119670
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
Lsusb:
 Bus 002 Device 004: ID 413c:2002 Dell Computer Corp. SK-8125 Keyboard
 Bus 002 Device 003: ID 413c:1002 Dell Computer Corp. Keyboard Hub
 Bus 002 Device 002: ID 046d:c00c Logitech, Inc. Optical Wheel Mouse
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Dell Computer Corporation OptiPlex GX240
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=UUID=fa991b67-9b47-4102-988a-c540a77881f9 ro quiet splash
RelatedPackageVersions: linux-firmware 1.34
RfKill:

SourcePackage: linux
Title: package linux-image-2.6.32-26-generic (not installed) failed to install/upgrade: corrupted filesystem tarfile - corrupted package archive
dmi.bios.date: 07/19/2002
dmi.bios.vendor: Dell Computer Corporation
dmi.bios.version: A05
dmi.board.name: OptiPlex GX240
dmi.board.vendor: Dell Computer Corporation
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Computer Corporation
dmi.modalias: dmi:bvnDellComputerCorporation:bvrA05:bd07/19/2002:svnDellComputerCorporation:pnOptiPlexGX240:pvr:rvnDellComputerCorporation:rnOptiPlexGX240:rvr:cvnDellComputerCorporation:ct6:cvr:
dmi.product.name: OptiPlex GX240
dmi.sys.vendor: Dell Computer Corporation

[Victor Vargas (kamus)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

Now open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.