Ubuntu
lirc package

package lirc 0.8.6-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

Bug #575417 reported by Slacker Belmont on 2010-05-04

This bug report is a duplicate of: Bug #442941: debconf failed to upgrade from 1.5.27ubuntu1 to 1.5.27ubuntu2: exit status 128 - Use of uninitialized value $reply in scalar chomp at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 66. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	lirc (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

Binary package hint: lirc

Ubuntu Karmic,
GNOME 2.28.1
Amd Athlon X4 630
2GB Memory

ProblemType: Package
Architecture: i386
Date: Mon May 3 21:09:55 2010
DistroRelease: Ubuntu 9.10
ErrorMessage: subprocess installed post-installation script returned error exit status 128
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
NonfreeKernelModules: fglrx
Package: lirc 0.8.6-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.31-21.59-generic
SourcePackage: lirc
Title: package lirc 0.8.6-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
Uname: Linux 2.6.31-21-generic i686

Tags:

Revision history for this message

Slacker Belmont (xxslackerxx) wrote on 2010-05-04:

AptOrdering.txt Edit (465 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (1.0 KiB, text/plain; charset="utf-8")
Dmesg.txt Edit (45.3 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (9.4 KiB, text/plain; charset="utf-8")
XsessionErrors.txt Edit (1.5 KiB, text/plain; charset="utf-8")

Revision history for this message

Jean-Baptiste Lallement (jibel) wrote on 2010-06-09:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 442941, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.