Ubuntu
g15daemon package

package g15daemon 1.9.5.3-3 failed to install/upgrade: subprocess post-installation script returned error exit status 1

Bug #410462 reported by thomas4g63 on 2009-08-07

This bug report is a duplicate of: Bug #173675: g15daemon: Fail to install when required hardware is not present. Edit Remove

This bug affects 2 people

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

Bug Description

Binary package hint: g15daemon

its fucking my being able to play videos at a steady stream

ProblemType: Package
Architecture: i386
DistroRelease: Ubuntu 9.04
ErrorMessage: subprocess post-installation script returned error exit status 1
Package: g15daemon 1.9.5.3-3
SourcePackage: g15daemon
Title: package g15daemon 1.9.5.3-3 failed to install/upgrade: subprocess post-installation script returned error exit status 1
Uname: Linux 2.6.28-14-generic i686

Tags:

Revision history for this message

thomas4g63 (thomas4g63) wrote on 2009-08-07:

Dependencies.txt Edit (260 bytes, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (2.4 KiB, text/plain; charset="utf-8")

Revision history for this message

Marc Deslauriers (mdeslaur) wrote on 2009-08-10:

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

security vulnerability:	yes → no
visibility:	private → public

Revision history for this message

Jean-Baptiste Lallement (jibel) wrote on 2009-11-12:

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 173675, 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.