Après avoir réussi (douloureusement) à installer Skype sur mon Ubuntu 12.04 LTS, je suis confronté depuis des mois à un problème de paquets que je ne peux pas résoudre.
Jetez un coup d’œil à mon dernier message pour savoir la cause de ce problème: Installez Skype sur Ubuntu 12.04 LTS 64-bit
Si j'essaie d'installer les mises à jour du système, le gestionnaire de mise à jour se ferme de manière inattendue en indiquant que le système de package est en panne et renvoie l'erreur suivante:
The following packages have unmet dependencies:
grub-efi-AMD64: Depends: grub2-common (= 1.99-21ubuntu3.9) but 1.99-21ubuntu3.10 is installed
Depends: grub-efi-AMD64-bin (= 1.99-21ubuntu3.9) but 1.99-21ubuntu3.10 is installed
Si je lance Sudo apt-get -f install
afin de résoudre les problèmes de paquets potentiels, j'obtiens ce qui suit:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
linux-image-3.5.0-26-generic linux-headers-3.5.0-26
linux-headers-3.5.0-26-generic
Use 'apt-get autoremove' to remove them.
The following extra packages will be installed:
grub-efi-AMD64
The following packages will be upgraded:
grub-efi-AMD64
1 upgraded, 0 newly installed, 0 to remove and 28 not upgraded.
2 not fully installed or removed.
Need to get 39.5 kB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue [Y/n]? y
Get:1 http://archive.ubuntu.com/ubuntu/ precise-updates/main grub-efi-AMD64 AMD64 1.99-21ubuntu3.10 [39.5 kB]
Fetched 39.5 kB in 0s (154 kB/s)
dpkg: dependency problems prevent configuration of grub-efi-AMD64:
grub-efi-AMD64 depends on grub2-common (= 1.99-21ubuntu3.9); however:
Version of grub2-common on system is 1.99-21ubuntu3.10.
grub-efi-AMD64 depends on grub-efi-AMD64-bin (= 1.99-21ubuntu3.9); however:
Version of grub-efi-AMD64-bin on system is 1.99-21ubuntu3.10.
dpkg: error processing grub-efi-AMD64 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of grub-efi-AMD64-signed:
grub-efi-AMD64-signed depends on grub-efi-AMD64 (>= 1.99-21ubuntu3.5); however:
Package grub-efi-AMD64 is not configured yet.
dpkg: error processing grub-efi-AMD64-signed (--configure):
dependency problems - leaving unconfiguredNo apport report written because the error message indicates its a followup error from a previous failure.
No apport report written because the error message indicates its a followup error from a previous failure.
Errors were encountered while processing:
grub-efi-AMD64
grub-efi-AMD64-signed
E: Sub-process /usr/bin/dpkg returned an error code (1)
Si je lance Sudo dpkg --configure -a
je reçois:
dpkg: dependency problems prevent configuration of grub-efi-AMD64:
grub-efi-AMD64 depends on grub2-common (= 1.99-21ubuntu3.9); however:
Version of grub2-common on system is 1.99-21ubuntu3.10.
grub-efi-AMD64 depends on grub-efi-AMD64-bin (= 1.99-21ubuntu3.9); however:
Version of grub-efi-AMD64-bin on system is 1.99-21ubuntu3.10.
dpkg: error processing grub-efi-AMD64 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of grub-efi-AMD64-signed:
grub-efi-AMD64-signed depends on grub-efi-AMD64 (>= 1.99-21ubuntu3.5); however:
Package grub-efi-AMD64 is not configured yet.
dpkg: error processing grub-efi-AMD64-signed (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
grub-efi-AMD64
grub-efi-AMD64-signed
D'après ce que je comprends, la cause fondamentale est liée aux dépendances non satisfaites des paquets grub-efi-AMD64
et grub-efi-AMD64-signed
, et j'ai donc essayé ce qui est décrit ici Comment résoudre les dépendances non satisfaites après avoir ajouté un PPA? mais le problème persiste encore.
Je ne sais pas si la suppression des paquetages en conflit résoudrait le problème, mais je ne l'ai pas encore fait car je crains de ruiner mon système car il dispose du démarrage EFI et je le lance avec GRUB. Pour la même raison, je n'ai pas essayé d'exécuter Sudo apt-get -u dist-upgrade
, car les paquets en conflit pourraient peut-être être automatiquement supprimés.
J'aimerais savoir si d'autres personnes ont vécu une expérience similaire et ont proposé des solutions.
Juste comme information additionnelle ceci est la sortie de gedit /etc/apt/sources.list
:
# deb cdrom:[Ubuntu 12.04.2 LTS _Precise Pangolin_ - Release AMD64 (20130213)]/ dists/precise/main/binary-i386/
# deb cdrom:[Ubuntu 12.04.2 LTS _Precise Pangolin_ - Release AMD64 (20130213)]/ dists/precise/restricted/binary-i386/
# deb cdrom:[Ubuntu 12.04.2 LTS _Precise Pangolin_ - Release AMD64 (20130213)]/ precise main restricted
# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
# newer versions of the distribution.
deb http://archive.ubuntu.com/ubuntu precise main restricted
## Major bug fix updates produced after the final release of the
## distribution.
deb http://archive.ubuntu.com/ubuntu precise-updates main restricted
## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team. Also, please note that software in universe WILL NOT receive any
## review or updates from the Ubuntu security team.
deb http://archive.ubuntu.com/ubuntu precise universe
deb http://archive.ubuntu.com/ubuntu precise-updates universe
## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team, and may not be under a free licence. Please satisfy yourself as to
## your rights to use the software. Also, please note that software in
## multiverse WILL NOT receive any review or updates from the Ubuntu
## security team.
deb http://archive.ubuntu.com/ubuntu precise multiverse
deb http://archive.ubuntu.com/ubuntu precise-updates multiverse
## N.B. software from this repository may not have been tested as
## extensively as that contained in the main release, although it includes
## newer versions of some applications which may provide useful features.
## Also, please note that software in backports WILL NOT receive any review
## or updates from the Ubuntu security team.
deb http://archive.ubuntu.com/ubuntu precise-security main restricted
deb http://archive.ubuntu.com/ubuntu precise-security universe
deb http://archive.ubuntu.com/ubuntu precise-security multiverse
## Uncomment the following two lines to add software from Canonical's
## 'partner' repository.
## This software is not part of Ubuntu, but is offered by Canonical and the
## respective vendors as a service to Ubuntu users.
deb http://archive.canonical.com/ubuntu precise partner
deb-src http://archive.canonical.com/ubuntu precise partner
## This software is not part of Ubuntu, but is offered by third-party
## developers who want to ship their latest software.
# deb http://extras.ubuntu.com/ubuntu precise main
# deb-src http://extras.ubuntu.com/ubuntu precise main
deb http://archive.canonical.com/ precise partner
deb-src http://archive.canonical.com/ precise partner
Et gedit /etc/apt/sources.list.d/*
(fichiers différents):
deb-src http://ppa.launchpad.net/cassou/emacs/ubuntu precise main
### THIS FILE IS AUTOMATICALLY CONFIGURED ###
# You may comment out this entry, but any other modifications may be lost.
deb http://dl.google.com/linux/chrome/deb/ stable main
### THIS FILE IS AUTOMATICALLY CONFIGURED ###
# You may comment out this entry, but any other modifications may be lost.
deb http://dl.google.com/linux/chrome/deb/ stable main
deb http://ppa.launchpad.net/guilhem-fr/swftools/ubuntu precise main
deb-src http://ppa.launchpad.net/guilhem-fr/swftools/ubuntu precise main
deb-src http://ppa.launchpad.net/rabbitvcs/ppa/ubuntu precise main
deb http://ppa.launchpad.net/yannubuntu/boot-repair/ubuntu precise main
deb-src http://ppa.launchpad.net/yannubuntu/boot-repair/ubuntu precise main
deb http://ppa.launchpad.net/yannubuntu/boot-repair/ubuntu precise main
deb-src http://ppa.launchpad.net/yannubuntu/boot-repair/ubuntu precise main
J'ai finalement résolu mon problème en supprimant avec Synaptic les paquets problématiques grub-efi-AMD64 et grub-efi-AMD64.
Après cela, j'ai installé et appliqué toutes les mises à jour système en attente qui semblent avoir réinstallé les packages mentionnés.
Une fois que tout le processus de mise à jour est terminé, j'ai redémarré le système et tout va bien maintenant.
Installez simplement le gestionnaire de paquets synaptic et sous Statut (à gauche), cliquez sur les paquets cassés - sélectionnez-les et corrigez-les ou réinstallez-les.