package imagemagick-common 8:6.7.7.10+dfsg-4ubuntu1 failed to install/upgrade: package imagemagick-common is already installed and configured

[Klaus Osswald]

Strange policy there: Why is it selectable in first place, if it complains that it is already installed
and configured?

Did install k3d, gimp and upgrades in Ubuntu 14.10 with Synaptic when this came up.

Maybe a bug in synaptic? Will those kinda problems be handled in 15.04 only

or can I have it all working and handled fine earlier in the promised ubuntu utopia ; ))

Would be so nice, thanks.

ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: imagemagick-common 8:6.7.7.10+dfsg-4ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
Uname: Linux 3.16.0-23-generic x86_64
ApportVersion: 2.14.7-0ubuntu8.1
AptdaemonVersion: 1.1.1+bzr980-0ubuntu1
Architecture: amd64
Date: Thu Jan 29 13:13:43 2015
DuplicateSignature: package:imagemagick-common:8:6.7.7.10+dfsg-4ubuntu1:package imagemagick-common is already installed and configured
ErrorMessage: package imagemagick-common is already installed and configured
InstallationDate: Installed on 2015-01-28 (0 days ago)
InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
PackageArchitecture: all
SourcePackage: dpkg
Title: package imagemagick-common 8:6.7.7.10+dfsg-4ubuntu1 failed to install/upgrade: package imagemagick-common is already installed and configured
UpgradeStatus: No upgrade log present (probably fresh install)

[Klaus Osswald (y-klaus)]

Additional remark: Of course seems like imagemagick wanted to have been installed as a dependency to
k3d and others. Seems that problem that has to be handled here is that of dependencies of different programs, such as k3d and gimp or others who both seem to need the imagemagick, but are not the same, So when competely different programs with a common dependency want to be installed at same time, then there is this cross-access to same dependencies and disturbing error
messages coming up. Could there be a precaution arranged to avoid such cross-accessing desasters?

[Marc Deslauriers (mdeslaur)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.