package whoopsie 0.1.32 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1

Bug #1021291 reported by lauren
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
whoopsie-daisy (Ubuntu)
New
Undecided
lauren

Bug Description

installArchives() failed: (Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 310820 files and directories currently installed.)
Removing mixxx ...
Removing libid3tag0 ...
Removing libportmidi0 ...
Removing mixxx-data ...
Processing triggers for man-db ...
Processing triggers for desktop-file-utils ...
Processing triggers for bamfdaemon ...
Rebuilding /usr/share/applications/bamf.index...
Processing triggers for gnome-menus ...
Processing triggers for libc-bin ...
ldconfig deferred processing now taking place
Processing triggers for doc-base ...
Processing 1 removed doc-base file...
Enregistrement des documents avec scrollkeeper...
Setting up whoopsie (0.1.32) ...
useradd: impossible de verrouiller /etc/passwd; veuillez ressayer plus tard.
adduser: /usr/sbin/useradd -d /nonexistent -g whoopsie -s /bin/false -u 177 whoopsie a retourn le code d'erreur 1. Abandon.
dpkg: error processing whoopsie (--configure):
 subprocess installed post-installation script returned error exit status 1
No apport report written because MaxReports is reached already
Errors were encountered while processing:
 whoopsie
Error in function:
Setting up whoopsie (0.1.32) ...
useradd: impossible de verrouiller /etc/passwd; veuillez ressayer plus tard.
adduser: /usr/sbin/useradd -d /nonexistent -g whoopsie -s /bin/false -u 177 whoopsie a retourn le code d'erreur 1. Abandon.
dpkg: error processing whoopsie (--configure):
 subprocess installed post-installation script returned error exit status 1

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: whoopsie 0.1.32
ProcVersionSignature: Ubuntu 3.2.0-26.41-generic-pae 3.2.19
Uname: Linux 3.2.0-26-generic-pae i686
ApportVersion: 2.0.1-0ubuntu8
AptOrdering:
 mixxx-data: Purge
 whoopsie: Configure
Architecture: i386
CrashReports:
 640:114:124:578098:2012-07-05 13:13:47.513813000 +0400:2012-07-05 13:13:48.513813000 +0400:/var/crash/_usr_lib_i386-linux-gnu_colord_colord.114.crash
 600:0:0:115921:2012-07-05 17:10:17.135073000 +0400:2012-07-05 17:18:40.323094491 +0400:/var/crash/whoopsie.0.crash
Date: Thu Jul 5 17:10:18 2012
ErrorMessage: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
SourcePackage: whoopsie-daisy
Title: package whoopsie 0.1.32 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
UpgradeStatus: Upgraded to precise on 2012-04-30 (65 days ago)
WhoopsieLog:
 Failed to find user: whoopsie
 Failed to find user: whoopsie

Revision history for this message
lauren (ptite-lolo974) wrote :
Changed in whoopsie-daisy (Ubuntu):
assignee: nobody → lauren (ptite-lolo974)
lauren (ptite-lolo974)
Changed in whoopsie-daisy (Ubuntu):
status: New → Incomplete
status: Incomplete → New
Revision history for this message
Brian Murray (brian-murray) 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 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.

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.