Mythbuntu

package mythtv-common 2:0.24.1 fixes.20110624.572b95a-0ubuntu0mythbuntu1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1

Bug #801538 reported by Michael Syddall on 2011-06-24

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Mythbuntu	Won't Fix	Undecided	Unassigned

Bug Description

Connected external Windows Frontend which updated myth database, then when I reconnected to Mythbuntu frontend frontend crashes.

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: mythtv-common 2:0.24.1+fixes.20110624.572b95a-0ubuntu0mythbuntu1
ProcVersionSignature: Ubuntu 2.6.32-32.62-generic 2.6.32.38+drm33.16
Uname: Linux 2.6.32-32-generic x86_64
Architecture: amd64
CrashDB: mythbuntu
Date: Fri Jun 24 11:14:02 2011
ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationMedia: Mythbuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427.1)
Installed_mythtv_dbg: 0.0
SourcePackage: mythtv
Title: package mythtv-common 2:0.24.1+fixes.20110624.572b95a-0ubuntu0mythbuntu1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1

Tags:

Revision history for this message

Michael Syddall (michael-syddall) wrote on 2011-06-24:

.var.log.mythtv.mythbackend.log.txt Edit (2.4 MiB, text/plain; charset="utf-8")
.var.log.mythtv.mythfrontend.log.txt Edit (842.7 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (3.7 KiB, text/plain; charset="utf-8")
MythTVDirectoryPermissions.txt Edit (643 bytes, text/plain; charset="utf-8")
VarLogDistupgradeAptlog.gz Edit (271 bytes, application/x-gzip)
VarLogDistupgradeApttermlog.gz Edit (2.1 KiB, application/x-gzip)
VarLogDistupgradeHistorylog.gz Edit (648 bytes, application/x-gzip)

Revision history for this message

Thomas Mashos (tgm4883) wrote on 2015-01-10:

We really do appreciate you opening this ticket to help improve Mythbuntu, but it needs to be closed for a number of reasons. The biggest one is that upstream believes this to be fixed in the latest version. Could you please verify if this issue still exists in the latest version?

Please do not let the closing of this ticket dissuade you from opening a new ticket if this (or any other) problem occurs with the newer versions.