libogg0:i386 conflicts with libogg0

Bug #977103 reported by xylo
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Trinity Desktop Environment

Bug Description

Ubuntu 12.04

Package libogg0:i386 conflicts with libogg0 which causes major problems when trying to install 32 bit applications such as acroread or other packages depending on ia32-libs and therefore on libogg0:i386.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: libogg0:1.2.2~dfsg-1ubuntu2
Uname: Linux d630 3.2.0-22-generic #35-Ubuntu SMP Tue Apr 3 18:33:15 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

Tags: i386 precise
xylo (stefan-endrullis)
affects: nvidia-drivers-ubuntu → libogg (Ubuntu)
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in libogg (Ubuntu):
status: New → Confirmed
Revision history for this message
Alex Stapleton (alexs-prol) wrote :

acroread depends on a large number of :i386 packages that are marked as conflicting with their 64-bit versions. I thought the whole point of multi-arch was that they didn't conflict anymore? :(

Revision history for this message
Alex Stapleton (alexs-prol) wrote :

Removing gstreamer0.10-fluendo-plugins-mp3-partner prior to doing the acroread install fixed this conflict for me. Side effect of one of the precise multiarch/aptitude bugs? e.g.

Revision history for this message
xylo (stefan-endrullis) wrote :

Thanks for you help, Alex. Unfortunately, your approach cannot be applied on my machine, since I do not have gstreamer0.10-fluendo-plugins-mp3-partner installed. Anyway, since libogg0:i386 and libogg0 conflict with each other I suppose the only solution would be to remove libogg0. I tried to do so but then I discovered that hundreds of packages (indirectly) depend on this package, so that aptitude would remove in total 673 packages in order to remove libogg0. Thus, this cannot be the solution.

The question is: Why does libogg0 conflict with libogg0:i386 at all?

Revision history for this message
xylo (stefan-endrullis) wrote :

Moreover, this bug does not seem to be related to the general multiarch bugs of aptitude. The libogg0:i386 package produces the same conflict in different Ubuntu package managers (tested with aptitude, apt-get, synaptic).

Revision history for this message
xylo (stefan-endrullis) wrote :

I cannot believe that only 2 persons are affected by this bug. How do all the others install 32 bit applications such as adobe reader or other applications that depend on the 32 bit versions of libsdl1.2 or the general ia32-libs? If there is anybody out there with a 64 bit installation without this problem please let me know! If there is any workaround please post it here. All my Ubuntu precise installations are affected by this stupid package conflict! :( Could I get rid of it by switching to Debian?

Revision history for this message
xylo (stefan-endrullis) wrote :

I discovered the source of the problem via "apt-cache policy libogg0". Actually the libogg0 package came from another repository (trinity desktop environment). After removing the repository from sources.list and downgrading to the Ubuntu version of package libogg0 I could finally install ia32-libs. :)

xylo (stefan-endrullis)
affects: libogg (Ubuntu) → trinity-desktop
Revision history for this message
Jeffry Johnston (ubuntu-kidsquid) wrote :

I have this problem also, since I upgraded to Ubuntu 12.04 (precise) from Ubuntu 11.10 (oneiric). I am also running a 64-bit system.

The "oneiric" versions of the libogg packages (from TDE) show as version 1.2.2~dfsg-1ubuntu2 (which are what I have installed), but the "precise" (from Ubuntu) packages are "older" and have version 1.2.2~dfsg-1ubuntu1. See attached output for details.

When I remove the TDE repositories, and do an apt-get update, the broken package problems magically go away. See attached output for details.

I'm wondering if a potential fix would be to change the TDE repository version of the libogg's back to 1.2.2~dfsg-1ubuntu1 so that the package is the same version as what is in Ubuntu Precise. Or would that break things in another distribution?

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.