package samba4 4.0.0~alpha15~git20110124.dfsg1-2ubuntu1 failed to install/upgrade: ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 1

Bug #774012 reported by Martín Carioni
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
samba4 (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: samba4

Error in update ubuntu version

ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: samba4 4.0.0~alpha15~git20110124.dfsg1-2ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-28.49-generic 2.6.35.11
Uname: Linux 2.6.35-28-generic i686
NonfreeKernelModules: fglrx
Architecture: i386
Date: Sat Apr 30 02:04:26 2011
ErrorMessage: ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 1
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
SourcePackage: samba4
Title: package samba4 4.0.0~alpha15~git20110124.dfsg1-2ubuntu1 failed to install/upgrade: ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 1
UpgradeStatus: Upgraded to natty on 2011-04-29 (0 days ago)

Revision history for this message
Martín Carioni (martincarioni) wrote :
Revision history for this message
Marc Deslauriers (mdeslaur) wrote : Bug is not a security issue

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

security vulnerability: yes → no
visibility: private → public
Revision history for this message
Robert Roth (evfool) wrote :

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 #728840, 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. Feel free to continue to report any other bugs you may find.

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.