Ubuntu
oss4 package

package oss4-dkms 4.2-build2002-2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10

Bug #675443 reported by Cédric Jeanneret deactivated on 2010-11-15

This bug report is a duplicate of: Bug #601342: kernel update breaks oss4. Edit Remove

This bug affects 1 person

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

Bug Description

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 10.04.1 LTS
Release: 10.04
Codename: lucid

iF oss4-dkms 4.2-build2002-2 Open Sound System - DKMS module sources

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: oss4-dkms 4.2-build2002-2
ProcVersionSignature: Ubuntu 2.6.32-25.45-generic-pae 2.6.32.21+drm33.7
Uname: Linux 2.6.32-25-generic-pae i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Mon Nov 15 10:14:39 2010
ErrorMessage: subprocess installed post-installation script returned error exit status 10
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
PackageArchitecture: all
SourcePackage: oss4
Title: package oss4-dkms 4.2-build2002-2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10

Tags:

Revision history for this message

Cédric Jeanneret deactivated (cjeanneret-c2c-deactivated) wrote on 2010-11-15:

AptOrdering.txt Edit (161 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (867 bytes, text/plain; charset="utf-8")
Df.txt Edit (512 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (45.8 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (7.5 KiB, text/plain; charset="utf-8")

Revision history for this message

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

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 #633445, 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.