package libpostproc52 6:0.8.10-0ubuntu0.13.10.1 failed to install/upgrade: libpostproc52:amd64 6:0.git20120821-4 (Multi-Arch: no) is not co-installable with libpostproc52 which has multiple installed instances

Bug #1286836 reported by sunsik on 2014-03-02
422
This bug affects 97 people
Affects Status Importance Assigned to Milestone
libav (Ubuntu)
High
Unassigned
libpostproc (Ubuntu)
High
Unassigned

Bug Description

 -

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libpostproc52 6:0.8.10-0ubuntu0.13.10.1
ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5
Uname: Linux 3.13.0-14-generic x86_64
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
Date: Mon Mar 3 00:57:47 2014
Dependencies:
 gcc-4.9-base 4.9-20140222-0ubuntu1
 libavutil51 6:0.8.10-0ubuntu0.13.10.1 [origin: unknown]
 libc6 2.19-0ubuntu2
 libgcc1 1:4.9-20140222-0ubuntu1
 multiarch-support 2.19-0ubuntu2
ErrorMessage: libpostproc52:amd64 6:0.git20120821-4 (Multi-Arch: no) is not co-installable with libpostproc52 which has multiple installed instances
InstallationDate: Installed on 2013-12-12 (79 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
SourcePackage: libav
Title: package libpostproc52 6:0.8.10-0ubuntu0.13.10.1 failed to install/upgrade: libpostproc52:amd64 6:0.git20120821-4 (Multi-Arch: no) is not co-installable with libpostproc52 which has multiple installed instances
UpgradeStatus: Upgraded to trusty on 2014-03-02 (0 days ago)

sunsik (sunsik) wrote :

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.

information type: Private Security → Public
Launchpad Janitor (janitor) wrote :

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

Changed in libav (Ubuntu):
status: New → Confirmed
Changed in libav (Ubuntu):
importance: Undecided → High
Julien Aubin (gojulgarbmail) wrote :

Same there

Reinhard Tartler (siretart) wrote :

I believe this is effectively a duplicate of #1277552

Launchpad Janitor (janitor) wrote :

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

Changed in libpostproc (Ubuntu):
status: New → Confirmed
Changed in libpostproc (Ubuntu):
importance: Undecided → High
Julien Aubin (gojulgarbmail) wrote :

Workaround :
sudo dpkg --purge libpostproc52:i386

Then reinstall libpostproc52.

Rgds,

Claudiney (yet-estelar) wrote :

This is showing spam with this upgrade order System update: "FFmpeg library derived prostprocessing 31kb"
But when I authorize this upgrade, installation error appears, as I solve this? For the problem is related in this package.

"
Workaround :
sudo dpkg --purge libpostproc52:i386

Then reinstall libpostproc52.
"
or in other words
sudo apt-get purge libpostproc52:i386
sudo apt-get install libpostproc52

worked for me too

Charles Witt
210-787-2734
http://www.linkedin.com/pub/charles-witt/19/817/484/<http://www.linkedin.com/profile/view?id=64729828&trk=tab_pro>

On Fri, May 2, 2014 at 4:49 AM, Claudiney <email address hidden> wrote:

> This is showing spam with this upgrade order System update: "FFmpeg
> library derived prostprocessing 31kb"
> But when I authorize this upgrade, installation error appears, as I solve
> this? For the problem is related in this package.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1286836
>
> Title:
> package libpostproc52 6:0.8.10-0ubuntu0.13.10.1 failed to
> install/upgrade: libpostproc52:amd64 6:0.git20120821-4 (Multi-Arch:
> no) is not co-installable with libpostproc52 which has multiple
> installed instances
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1286836/+subscriptions
>

Anders Hall (a.hall) wrote :

"or in other words
sudo apt-get purge libpostproc52:i386
sudo apt-get install libpostproc52"

worked for me too

Claudiney (yet-estelar) wrote :

I used the tip from (cwwitt) to solve my problem and it worked.

" Workaround :
sudo dpkg --purge libpostproc52:i386

Then reinstall libpostproc52.
"
or in other words
sudo apt-get purge libpostproc52:i386
sudo apt-get install libpostproc52

worked for me too "

As if by magic, my problem is over, thanks for the hint and all the best to you!

Forest (foresto) wrote :

Here's a cleaner variation of the workaround:

sudo dpkg --purge --force-depends libpostproc52
sudo apt-get install libpostproc52
sudo apt-mark auto libpostproc52

The first line purges the package without removing any of the packages that depend on it. (This is fine, since we're going to reinstall the dependency immediately.)

The second line reinstalls the package.

The third line marks the package as automatically-installed (as it is in a stock ubuntu system), so the system knows to treat it as a dependency rather than something the user manually installed.

Attila Szász (tilusnet) wrote :

Thank you Julien at #7, you saved my day!

Forest (foresto) wrote :

For the record:

This happened to me during a distribution upgrade from 13.10 (saucy) to 14.04 (trusty). When it happened, the release upgrade tool interrupted itself with a dialog box containing this alarming and not very helpful message:
Could not install the upgrades
The upgrade has aborted. Your system could be in an unusable state. A recovery will run now (dpkg --configure -a).

This dialog box was modal, preventing me from scrolling or copying the text in the Terminal widget to see what really happened. The text visible in the Terminal widget did not show up in any of the /var/log/dist-upgrade/* logs, but it was clearly a python exception and stack trace.

Upon closing the dialog box, the upgrade continued, contrary to what the alarming message stated. (I guess the message was referring to one particular package, not the overall release upgrade, but most end users wouldn't know that, and even if they did the message didn't state which package.)

As the upgrade continued, I was unable to copy & paste the stack trace before it was pushed out of the Terminal widget's rather short scroll buffer.

Changed in libpostproc (Ubuntu):
status: Confirmed → Triaged
Changed in libav (Ubuntu):
status: Confirmed → Triaged
nicom87 (nico-musella87) wrote :

I followed the instructions of Foresto at #12 and it works perfectly!

Thank you very much!

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers