package whoopsie 0.1.32 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
whoopsie-daisy (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Configurando whoopsie (0.1.32) ...
useradd: no se puede bloquear /etc/passwd; inténtelo más tarde.
adduser: `/usr/sbin/useradd -d /nonexistent -g whoopsie -s /bin/false -u 130 whoopsie' devolvió el código de error 1. Saliendo.
dpkg: error al procesar whoopsie (--configure):
el subproceso instalado el script post-installation devolvió el código de salida de error 1
Configurando libphonon4 (4:4.7.
Configurando phonon-
Configurando phonon (4:4.7.
Configurando minitube (1.6-1) ...
Procesando disparadores para libc-bin ...
ldconfig deferred processing now taking place
Se encontraron errores al procesar:
whoopsie
E: Sub-process /usr/bin/dpkg returned an error code (1)
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: whoopsie 0.1.32
ProcVersionSign
Uname: Linux 3.2.0-24-generic i686
ApportVersion: 2.0.1-0ubuntu7
Architecture: i386
CrashReports:
600:0:
640:1000:
Date: Sun May 27 22:05:12 2012
ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 1
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
SourcePackage: whoopsie-daisy
Title: package whoopsie 0.1.32 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1
UpgradeStatus: Upgraded to precise on 2012-05-07 (20 days ago)
WhoopsieLog: Failed to find user: whoopsie
security vulnerability: | yes → no |
visibility: | private → public |
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 523896, 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. Please continue to report any other bugs you may find.