package libatk1.0-0 2.3.91-0ubuntu2 failed to install/upgrade: libatk1.0-0:amd64 2.3.91-0ubuntu2 cannot be configured because libatk1.0-0

Bug #950601 reported by Nick Breen
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
atk1.0 (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

This started occurring after upgrading from oneiric to precise (amd64) and then trying to follow the instructions here https://help.ubuntu.com/community/CitrixICAClientHowTo#A64-bit

something went horribly wrong with the i386 dependancies.

apt-get install -f fails
aptitude tried to apply some fixes, and removed a pile of i386 packages

now just this error and a similar one for libqtcore4

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: libatk1.0-0 2.3.91-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.94.1-0ubuntu1
Architecture: amd64
Date: Thu Mar 8 11:50:16 2012
DuplicateSignature:
 Setting up libatk1.0-data (2.3.91-0ubuntu2) ...
 dpkg: error processing libatk1.0-0:i386 (--configure):
  libatk1.0-0:i386 2.3.91-0ubuntu1 cannot be configured because libatk1.0-0:amd64 is in a different version (2.3.91-0ubuntu2)
ErrorMessage: libatk1.0-0:amd64 2.3.91-0ubuntu2 cannot be configured because libatk1.0-0
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
SourcePackage: atk1.0
Title: package libatk1.0-0 2.3.91-0ubuntu2 failed to install/upgrade: libatk1.0-0:amd64 2.3.91-0ubuntu2 cannot be configured because libatk1.0-0
UpgradeStatus: Upgraded to precise on 2012-03-08 (1 days ago)

Revision history for this message
Nick Breen (nickbreen) wrote :
tags: removed: need-duplicate-check
tags: added: a11y
Revision history for this message
Elena (e-formoso) wrote :

I have the same problem after upgrading from oneiric to precise (amd64)

libatk1.0-0:i386 2.3.91-0ubuntu2 cannot be configured because libatk1.0-0:amd64 is in a different version (2.3.93-1)

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in atk1.0 (Ubuntu):
status: New → Confirmed
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.