package samba-common 2:3.4.7~dfsg-1ubuntu3.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Bug #620102 reported by kelmark2180
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
samba (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Binary package hint: samba

Use samba to access ubuntu server on home network. After updates this laptop would not shutdown and I had to reload w/boot. When it tried to re-establish server access it said samba mod did not install.
This laptop is xbuntu10.04.1 LTS
Server = Ubuntu 9.10 (Kbuntu?)
I guess this may have been a permanent share thru smbfs

Don

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: samba-common 2:3.4.7~dfsg-1ubuntu3.1
ProcVersionSignature: Ubuntu 2.6.32-24.39-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic i686
Architecture: i386
Date: Wed Aug 18 14:49:43 2010
ErrorMessage: subprocess installed post-installation script returned error exit status 1
PackageArchitecture: all
SambaClientRegression: Yes
SourcePackage: samba
Title: package samba-common 2:3.4.7~dfsg-1ubuntu3.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Revision history for this message
kelmark2180 (dwbauer) wrote :
Revision history for this message
Scott Moser (smoser) wrote :

The terminal log shows :
Setting up samba-common (2:3.4.7~dfsg-1ubuntu3.1) ...

frontend: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

dpkg: error processing samba-common (--configure):

 subprocess installed post-installation script returned error exit status 1

I'm wondering if for some reason your X server was not available (maybe you had DISPLAY=:0.0 but no actual display available) or something other situation that caused debconf to attempt to use the X11 backend when that would fail.

I think if you try 'dpkg-reconfigure samba-common' you'll get through that issue.

Changed in samba (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
kelmark2180 (dwbauer) wrote : Re: [Bug 620102] Re: package samba-common 2:3.4.7~dfsg-1ubuntu3.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

  I'm just a follow the instructions, more technical, than most , allot
less than others guy. I ran the update and recovered through a terminal
session. I first tried the gui update manager and it was attempting to
recover/apply the Samba update and the update asked if was OK to
overwrite my smb.conf. That was a real pita to get out of since my
screen is only 800 X 600 and the window would not allow a re-size and I
could not see options nor complete a reply to the window since I had no
OK or anything to continue on. This was on an old 800 MHz laptop and I
don't have a screen stretcher.

Thanks for looking, I just did the auto whatever it required when the
interrupt occurred. I appreciate your efforts and thanks for a great OS
that has everything I could ever need!
Don

On 08/19/2010 12:19 PM, Scott Moser wrote:
> The terminal log shows :
> Setting up samba-common (2:3.4.7~dfsg-1ubuntu3.1) ...
>
> frontend: Fatal IO error 11 (Resource temporarily unavailable) on X
> server :0.0.
>
> dpkg: error processing samba-common (--configure):
>
> subprocess installed post-installation script returned error exit
> status 1
>
>
> I'm wondering if for some reason your X server was not available (maybe you had DISPLAY=:0.0 but no actual display available) or something other situation that caused debconf to attempt to use the X11 backend when that would fail.
>
> I think if you try 'dpkg-reconfigure samba-common' you'll get through
> that issue.
>
> ** Changed in: samba (Ubuntu)
> Importance: Undecided => Medium
>
> ** Changed in: samba (Ubuntu)
> Status: New => Incomplete
>

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.