package metacity 1:2.28.0-0ubuntu2 failed to install/upgrade: il sottoprocesso vecchio script di post-installation ha restituito lo stato di errore 2

[TaRkuS]

Binary package hint: metacity

Configurazione di metacity (1:2.28.0-0ubuntu2)...
update-alternatives: error: il collegamento alternativo /usr/bin/x-window-manager è già gestito da x-window-manager.before_restore_2009-11-30_18.54.45.427990.
dpkg: errore nell'elaborare metacity (--configure):
 il sottoprocesso vecchio script di post-installation ha restituito lo stato di errore 2
Si sono verificati degli errori nell'elaborazione:
 metacity
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
AptOrdering:
 xserver-common: Install
 xserver-xorg-core: Install
 metacity: Configure
 xserver-common: Configure
 xserver-xorg-core: Configure
Architecture: amd64
Date: Sat Mar 27 00:10:24 2010
DistroRelease: Ubuntu 9.10
ErrorMessage: il sottoprocesso vecchio script di post-installation ha restituito lo stato di errore 2
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
Package: metacity 1:2.28.0-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.31-20.58-generic
SourcePackage: metacity
Title: package metacity 1:2.28.0-0ubuntu2 failed to install/upgrade: il sottoprocesso vecchio script di post-installation ha restituito lo stato di errore 2
Uname: Linux 2.6.31-20-generic x86_64

[Pedro Villavicencio (pedro)]

Thanks for the report, it has been some time without any response or feedback in this bug report and we are wondering if this is still an issue for you with the latest release of Ubuntu the Natty Narwhal, May you please test with that version and comment back if you're still having or not the issue? Please have a look at http://www.ubuntu.com/download to know how to install that version.Thanks in advance.

[Pedro Villavicencio (pedro)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.