Ubuntu
lirc package

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

Bug #769130 reported by lilifiz on 2011-04-22

This bug report is a duplicate of: Bug #621908: package lirc 0.8.6-0ubuntu4.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128. Edit Remove

This bug affects 1 person

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

Bug Description

Binary package hint: lirc

as kindda new to linux world, but as far as i know, compiz was crashed immediately after this bug, this is all i know so far about this bug

ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: lirc 0.8.7-0ubuntu4
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
Date: Fri Apr 22 13:11:46 2011
ErrorMessage: subprocess installed post-installation script returned error exit status 128
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110330)
SourcePackage: lirc
Title: package lirc 0.8.7-0ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
UpgradeStatus: Upgraded to natty on 2011-04-22 (0 days ago)

Tags:

Revision history for this message

lilifiz (lilifiz) wrote on 2011-04-22:

AptOrdering.txt Edit (171 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (1.1 KiB, text/plain; charset="utf-8")
Df.txt Edit (521 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (59.8 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (3.6 KiB, text/plain; charset="utf-8")

Revision history for this message

Robert Roth (evfool) wrote on 2011-05-19:

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 #621908, 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. Feel free to continue to report any other bugs you may find.