package samba-common 2:4.3.11+dfsg-0ubuntu0.14.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

Bug #1636988 reported by Ajax4Hire
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
samba (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Failed during upgrade.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: samba-common 2:4.3.11+dfsg-0ubuntu0.14.04.1
ProcVersionSignature: Ubuntu 4.4.0-45.66~14.04.1-generic 4.4.21
Uname: Linux 4.4.0-45-generic i686
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: i386
Date: Wed Oct 26 15:43:51 2016
DuplicateSignature: package:samba-common:2:4.3.11+dfsg-0ubuntu0.14.04.1:subprocess installed post-installation script returned error exit status 128
ErrorMessage: subprocess installed post-installation script returned error exit status 128
InstallationDate: Installed on 2016-09-21 (35 days ago)
InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release i386 (20160803)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.7
 apt 1.0.1ubuntu2.15
SambaClientRegression: Yes
SourcePackage: samba
Title: package samba-common 2:4.3.11+dfsg-0ubuntu0.14.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.samba.gdbcommands: [deleted]

Revision history for this message
Ajax4Hire (ajax4hire) wrote :
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.

From the Log I found:
Use of uninitialized value $reply in scalar chomp at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 66, <GEN0> line 12.

But those should be unrelated. They are part of a very old issue that can't be 100% fixed in all cases but should not be fatal.

It might be useful if you can report the output of journalctl -xe after such a failed upgrade.
Maybe we can find some more what is going on in your case in there.

Since there isn't enough information in your report to differentiate between a local configuration problem and a bug in Ubuntu, I'm marking this bug as Incomplete.

If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community

Or if you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New.

Changed in samba (Ubuntu):
status: New → Incomplete
tags: removed: need-duplicate-check
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for samba (Ubuntu) because there has been no activity for 60 days.]

Changed in samba (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.