package linux-libc-dev 2.6.31-12.41 failed to install/upgrade: error writing to '<standard output>': No such file or directory

[geoganoe]

This bug may be related to 445736, but it occurred in the next released version of the package. While the package appears to have been installed correctly, the message that was used to launch this bug still popped up as an icon in the notification area.

                George

ProblemType: Package
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: george 1562 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf7eb8000 irq 16'
   Mixer name : 'Realtek ALC269'
   Components : 'HDA:10ec0269,1043834a,00100004'
   Controls : 12
   Simple ctrls : 7
Date: Thu Oct 8 00:26:02 2009
Dependencies:

DistroRelease: Ubuntu 9.10
ErrorMessage: error writing to '<standard output>': No such file or directory
MachineType: ASUSTeK Computer INC. 1000
Package: linux-libc-dev 2.6.31-12.41
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-12-generic root=UUID=446dd80c-5cef-478b-8e4b-4e32abb8e347 ro quiet splash
ProcVersionSignature: Ubuntu 2.6.31-12.41-generic
RelatedPackageVersions: linux-firmware 1.21
SourcePackage: linux
Title: package linux-libc-dev 2.6.31-12.41 failed to install/upgrade: error writing to '<standard output>': No such file or directory
Uname: Linux 2.6.31-12-generic i686
dmi.bios.date: 07/14/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0702
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 1000
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTek Computer INC.
dmi.chassis.version: x.x
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0702:bd07/14/2008:svnASUSTeKComputerINC.:pn1000:pvrx.x:rvnASUSTeKComputerINC.:rn1000:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x:
dmi.product.name: 1000
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.

[geoganoe (geoganoe-yahoo)]

I forgot to mention that the bug icon appeared in the notification area after the following sequence of actions:

I attempted to run Update Manager, which failed and locked up the system (i.e. - no response to the mouse, keyboard, and even ctrl/alt/delete didn't work). I had to use the hold the power button down to get the machine to shut off.

When I tried to reboot, I received a transient message about an install problem that I didn't get to read all of before it disappeared, then after logging in, the only thing that came up was the default background image.

I rebooted again with the same result.

I rebooted into safe mode and used the "dpkg repair ??" option in the menu.

When dpkg finished and gave me a login prompt, I logged in then used "sudo reboot" to restart the system.

This time the system restarted normally, and after logging in, I saw the bug icon in the notification area.

                               George