package winbind 2:3.2.0-4ubuntu2 failed to install/upgrade: subprocess post-installation script returned error exit status 2

Bug #253910 reported by knarf
98
This bug affects 2 people
Affects Status Importance Assigned to Milestone
samba (Ubuntu)
Fix Released
High
Dustin Kirkland 
Intrepid
Fix Released
High
Dustin Kirkland 

Bug Description

Binary package hint: samba

Updating Intrepid today, got "package winbind 2:3.2.0-4ubuntu2 failed to install/upgrade: subprocess post-installation script returned error exit status 2" message.

Cause is a missing double semicolon in the init script.

Attached patch fixes bug.

apt-cache policy winbind
winbind:
  Installed: 2:3.2.0-4ubuntu2
  Candidate: 2:3.2.0-4ubuntu2
  Version table:
 *** 2:3.2.0-4ubuntu2 0
        400 http://archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status
     2:3.0.30-2ubuntu3 0
        400 http://se.archive.ubuntu.com intrepid/main Packages

ProblemType: Package
Architecture: i386
Date: Fri Aug 1 12:02:30 2008
DistroRelease: Ubuntu 8.10
ErrorMessage: subprocess post-installation script returned error exit status 2
NonfreeKernelModules: ath_hal
Package: winbind 2:3.2.0-4ubuntu2
PackageArchitecture: i386
SourcePackage: samba
Title: package winbind 2:3.2.0-4ubuntu2 failed to install/upgrade: subprocess post-installation script returned error exit status 2
Uname: Linux 2.6.26-t23-200807141556 i686

Related branches

Revision history for this message
knarf (launchpad-ubuntu-f) wrote :
Matt Zimmerman (mdz)
Changed in samba:
importance: Undecided → High
status: New → Triaged
assignee: nobody → kirkland
Revision history for this message
Marcin (marcinsud) wrote :

on amd64 this bug also occur

Revision history for this message
Niels Egberts (nielsegberts) wrote :

Confirm on amd64

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package samba - 2:3.2.0-4ubuntu3

---------------
samba (2:3.2.0-4ubuntu3) intrepid; urgency=low

  * debian/winbind.init: Fixed error in init script. (LP: #253910)

 -- Chuck Short <email address hidden> Fri, 01 Aug 2008 14:01:09 +0000

Changed in samba:
status: Triaged → Fix Released
Revision history for this message
Marcin (marcinsud) wrote :

on amd64 still this bug isn't fixed

Changed in samba:
status: Fix Released → New
status: New → Incomplete
Revision history for this message
Marcin (marcinsud) wrote :

on amd64 still don't work

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

The original bug is fixed. The problem now though, is when you upgrade, dpkg runs the old prerm script which tries to stop winbind. This procedure fails due to the syntax error in the old init script, which prevents the upgrade.

You can work around this by hand-editing /etc/init.d/winbind before you attempt the upgrade

Revision history for this message
Mathias Gug (mathiaz) wrote :

As mentioned above, this bug is fixed.

Changed in samba:
status: Incomplete → Fix Released
Revision history for this message
George Prowse (torqueing) wrote :

moving or deleting /etc/init.d/winbind allows apt to update it normally. As long as you install the package maintainers version then you are ok

Changed in samba:
status: Fix Released → Confirmed
Changed in samba:
status: Confirmed → Fix Released
Revision history for this message
Dustin Kirkland  (kirkland) wrote :

If you are still bitten by this problem, you can:
 # sudo rm -f /etc/init.d/winbind
 # sudo apt-get remove --purge winbind
 # sudo apt-get install winbind

:-Dustin

Revision history for this message
Marques Johansson (marques) wrote :

Ricktick,

Another option is to download the latest winbind . This should show you the url from your shell:
apt-get --print-uris -y --reinstall install winbind | grep "^'" | sed -e "s/^'//" -e "s/\.deb.*/\.deb/"

Then "sudo dpkg -x DEBFILE /"
replacing DEBFILE with the name/location of the package you just downloaded..

Then you should be able to "apt-get -f install" , or "dpkg --configure -a", or whatever else was breaking due to winbind.

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.