Ubuntu
samba package

package samba-common 2:3.3.2-1ubuntu3.2 failed to install/upgrade: subprocess post-installation script returned error exit status 3

Bug #440725 reported by mback
80
This bug affects 17 people
Affects Status Importance Assigned to Milestone
samba (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Binary package hint: samba

Tried upgrading today from what was most recent to today's version of SAMBA. Expected the updater to either merge the conf file or use prev, and it crashed instead.

Tried a 3-way merge on the conf file... unsuccessful. Upgrade Manager came back & asked again & I said said use existing conf file... then ... crash

$ lsb_release -rd
Description: Ubuntu 9.04
Release: 9.04
$ apt-cache policy samba
samba:
  Installed: 2:3.3.2-1ubuntu3.2
  Candidate: 2:3.3.2-1ubuntu3.2
  Version table:
 *** 2:3.3.2-1ubuntu3.2 0
        500 http://us.archive.ubuntu.com jaunty-updates/main Packages
        500 http://us.archive.ubuntu.com jaunty-security/main Packages
        100 /var/lib/dpkg/status
     2:3.3.2-1ubuntu3 0
        500 http://us.archive.ubuntu.com jaunty/main Packages

ProblemType: Package
Architecture: amd64
DistroRelease: Ubuntu 9.04
ErrorMessage: subprocess post-installation script returned error exit status 3
NonfreeKernelModules: fglrx
Package: samba-common 2:3.3.2-1ubuntu3.2
SourcePackage: samba
Title: package samba-common 2:3.3.2-1ubuntu3.2 failed to install/upgrade: subprocess post-installation script returned error exit status 3
Uname: Linux 2.6.28-15-generic x86_64

Revision history for this message
mback (mback) wrote :
Revision history for this message
Chuck Short (zulcss) wrote :

Relevant error:

Setting up samba-common (2:3.3.2-1ubuntu3.2) ...

Merging changes into the new version

 Conflicts found! Please edit `/etc/samba/smb.conf' and sort them out manually.

 The file `/etc/samba/smb.conf.ucf-new' has a record of the failed merge of the configuration file.

if you fix up those errors and dpkg --configure samba-common then you should be fine.

Regards
chuck

Changed in samba (Ubuntu):
status: New → Won't Fix
Revision history for this message
Jesse Glick (jesse-glick) wrote :

I would expect Update Manager to just tell me politely that there were merge conflicts, and maybe open my $EDITOR on whatever file I am supposed to edit - smb.conf seemed fine the way it was, and it was not clear whether I was supposed to rename smb.conf.ucf-new to smb.conf after removing conflict markers or simply save it. In any event I would not expect the UI to report a "crash" and offer to file a bug report.

Revision history for this message
Huygens (huygens-25) wrote :

I agree with Jesse.
I tweaked the smb.conf to fit our particular network environment (so I integrated the existing infrastructure).

I would expect that if an update requires a merge of the smb.conf it should propose to manually merge the file. During Ubuntu OS upgrade (from 8.10 to 9.04 for example), such feature is available.

In addition, as this is just a bug/security fix version, I would not even expect to have to merge my smb.conf. I would only expect it during major updates.

Revision history for this message
Buzzsaw (rhbusby) wrote :

I agree with Jesse and Huygens. I tried to view the smb conf files side by side but the system crashed. I had samba working well before teh security/ fix attmepted installatin, but now I have to ago back ad figure it out again. It is unclear wht I am supposed to do to get back to operatinal status. I am not very experienced and I had some difficulty in getting Samba workng in the first place.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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