Ubuntu
tzdata package

package tzdata 2012b-0ubuntu0.10.04 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 128

Bug #969876 reported by maxastro on 2012-03-31

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
	tzdata (Ubuntu)	New	Undecided	Unassigned

Bug Description

Ubuntu restricted extras couldn't finish setup operation without "apt-get install -f" command entered in terminal manually.

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: tzdata 2012b-0ubuntu0.10.04
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
Architecture: i386
Date: Sat Mar 31 16:41:35 2012
ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код ошибки 128
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
PackageArchitecture: all
SourcePackage: tzdata
Title: package tzdata 2012b-0ubuntu0.10.04 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 128

Tags:

Revision history for this message

maxastro (maxastro-yandex) wrote on 2012-03-31:

AptOrdering.txt Edit (2.1 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (489 bytes, text/plain; charset="utf-8")
Df.txt Edit (597 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (41.9 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (19.7 KiB, text/plain; charset="utf-8")

Revision history for this message

Brian Murray (brian-murray) wrote on 2012-03-31:

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.