package update-manager 1:0.87.12 failed to install/upgrade: ErrorMessage: SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg returned an error code (1), E:Sub-process /usr/bin/dpkg returned an error code (1), E:Sub-process /usr/bin/dpkg returned an error code (1)

Bug #204757 reported by Erik
18
Affects Status Importance Assigned to Milestone
exim4 (Ubuntu)
Invalid
Undecided
Pascal De Vuyst

Bug Description

Binary package hint: update-manager

I was upgrading to 8.04

ProblemType: Package
Architecture: i386
Date: Fri Mar 21 19:12:10 2008
DistroRelease: Ubuntu 8.04
ErrorMessage: ErrorMessage: SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg returned an error code (1), E:Sub-process /usr/bin/dpkg returned an error code (1), E:Sub-process /usr/bin/dpkg returned an error code (1)

Package: update-manager 1:0.87.12
PackageArchitecture: all
SourcePackage: update-manager
Title: package update-manager 1:0.87.12 failed to install/upgrade: ErrorMessage: SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg returned an error code (1), E:Sub-process /usr/bin/dpkg returned an error code (1), E:Sub-process /usr/bin/dpkg returned an error code (1)
Uname: Linux 2.6.22-14-generic i686

Revision history for this message
Erik (erik-pope) wrote :
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. Could you please add all the files contained in /var/log/dist-upgrade/ to your bug report as separate attachments? Thanks in advance.

Changed in update-manager:
status: New → Incomplete
Revision history for this message
yamo (stephane-gregoire) wrote :

I've also have this bug when upgrading from gutsy to hardy beta

Revision history for this message
drewp (drewp) wrote :

Similar message, but the popup also mentioned "/usr/bin/cwm", which is a python program that I think I installed with normal 'python setup.py install' (or possibly easy_install).

Revision history for this message
Michael Vogt (mvo) wrote :

Thanks for your bugreport.

@drewp:
The cause of the error is a bug in virtualbox-ose (that is already reported):
2008-04-21 08:38:46,188 ERROR got an error from dpkg for pkg: '/var/cache/apt/archives/virtualbox-ose_1.5.6-dfsg-6ubuntu1_amd64.deb': 'subprocess pre-installation script returned error exit status 1

@yamo:
The problem you experienced is a bug in exim4-config:

2008-04-12 16:25:19,137 ERROR got an error from dpkg for pkg: 'exim4-config': 'le sous-processus post-installation script a retourné une erreur de sortie d'état 2
...
Paramétrage de example-content (31) ...
Paramétrage de exim4-config (4.69-2) ...
Installation de la nouvelle version du fichier de configuration /etc/exim4/conf.d/transport/30_exim4-config_remote_smtp_smarthost ...
Installation de la nouvelle version du fichier de configuration /etc/exim4/conf.d/transport/30_exim4-config_remote_smtp ...
Installation de la nouvelle version du fichier de configuration /etc/exim4/conf.d/main/02_exim4-config_options ...
Installation de la nouvelle version du fichier de configuration /etc/exim4/conf.d/main/03_exim4-config_tlsoptions ...
Installation de la nouvelle version du fichier de configuration /etc/exim4/conf.d/router/300_exim4-config_real_local ...
Installation de la nouvelle version du fichier de configuration /etc/exim4/conf.d/acl/40_exim4-config_check_data ...
Installation de la nouvelle version du fichier de configuration /etc/exim4/conf.d/acl/30_exim4-config_check_rcpt ...
Installation de la nouvelle version du fichier de configuration /etc/exim4/exim4.conf.template ...
/usr/sbin/dpkg-statoverride: groupe Debian-exim non existant
Syntaxe : dpkg-statoverride [<option> ...] <commande>
Commandes :
  --add <propriétaire> <groupe> <mode> <fichier>
                           ajouter une nouvelle entrée dans la base de données.
  --remove <fichier supprimer le fichier de la base de données.
  --list [<motif>] liste les forçages actuels dans la base de données.
Options :
  --admindir <répertoire> positionne le répertoire avec le fichier des permissions (statoverride).
  --update mettre à jour le fichier des permissions immédiatement.
  --force forcer une action si un contrôle de cohérence échoue.
  --quiet opération discrète, affichage minimal.
  --help afficher ce message d'aide.
  --version afficher la version.
dpkg : erreur de traitement de exim4-base (--configure) :
 problèmes de dépendances - laissé non configuré
...

I reassign and

Revision history for this message
Michael Vogt (mvo) wrote :

@yamo:
Does your /etc/group file contain a Debian-exim group? I was not able to reproduce this failure in a chroot upgrade test from dapper to hardy.

Changed in exim4:
status: Incomplete → Confirmed
Revision history for this message
yamo (stephane-gregoire) wrote :

I'll try to reproduce this bug, but since the bug report, I've removed exim4* and mailx...

I had this on gutsy and the bug appeared after the upgrade to hardy beta.

I think it's only a bug caused by the order of installation :

I've tried to only install exim4-config :

  sudo apt-get install exim4-config
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances
Lecture des informations d'état... Fait
Les NOUVEAUX paquets suivants seront installés :
  exim4-config
0 mis à jour, 1 nouvellement installés, 0 à enlever et 0 non mis à jour.
Il est nécessaire de prendre 310ko dans les archives.
Après cette opération, 1053ko d'espace disque supplémentaires seront utilisés.
Réception de : 1 http://archive.ubuntu.com hardy/main exim4-config 4.69-2 [310kB]
310ko réceptionnés en 8s (37,7ko/s)
Préconfiguration des paquets...
Sélection du paquet exim4-config précédemment désélectionné.
(Lecture de la base de données... 114341 fichiers et répertoires déjà installés.)
Dépaquetage de exim4-config (à partir de .../exim4-config_4.69-2_all.deb) ...
Paramétrage de exim4-config (4.69-2) ...
Adding system-user for exim (v4)

As you see I've succeded!

Revision history for this message
Pascal De Vuyst (pascal-devuyst) wrote :

Erik,
We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

yamo,
This bug has also been reported as bug #240703.

Changed in exim4:
assignee: nobody → pascal-devuyst
status: Confirmed → Invalid
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.