Welcome, Guest. Please login or register.
Did you miss your activation email?

Author Topic:   relocation error: LIBAVCODEC 57 [solved]  (Read 2232 times)

Offline mash

  • User
  • Posts: 47
relocation error: LIBAVCODEC 57 [solved]
« on: 2018/01/07, 21:26:38 »
I am getting the following error on starting chromium and digikam:
Code: [Select]
relocation error: /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5: symbol avcodec_parameters_to_context, version LIBAVCODEC_57 not defined in file libavcodec.so.57 with link time reference
I am getting this error for chromium since October 2017 but switched to another browser.
Now I am getting it on digikam as well. I need digikam on a daily basis, so now I need to get rid of this error.
The application just wont start after emitting the error message.
Hint:
When I do a d-u I get
The following packages have been kept back:
  kaffeine
But I have not held back any broken packages
Any hints welcome
« Last Edit: 2018/01/09, 11:50:26 by mash »
when it was hard to write it should be hard to read

Offline melmarker

  • User
  • Posts: 2.799
    • g-com.eu
Re: relocation error: LIBAVCODEC 57
« Reply #1 on: 2018/01/07, 21:34:43 »
Was erwartet man auch sonst bei einer Transition oder neuen Version von av?
---
What else would one expect in an ongoing Transition of av?
Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. (Benjamin Franklin, November 11, 1755)
Never attribute to malice that which can be adequately explained by stupidity. (Hanlons razor)

Offline mash

  • User
  • Posts: 47
Re: relocation error: LIBAVCODEC 57
« Reply #2 on: 2018/01/07, 21:39:04 »
Danke fuer Eure Hilfe gestern im IRC. Leider war dann eine Neuinstallation von KDE erforderlich und bei den lahmen Leitungen hat das ein paar Stunden gedauert
« Last Edit: 2018/01/08, 09:42:04 by mash »
when it was hard to write it should be hard to read

Offline whistler_mb

  • User
  • Posts: 198
Re: relocation error: LIBAVCODEC 57
« Reply #3 on: 2018/01/08, 09:40:41 »
Wenn du Digikam ständig benötigst, könntest du es auch experimental testen. Sei dir aber bewusst, dass du keinen Support dafür erwarten kannst.

Code: [Select]
$ apt-cache policy digikam
digikam:
  Installiert:           4:5.7.0-2+b2
  Installationskandidat: 4:5.7.0-2+b2
  Versionstabelle:
 *** 4:5.7.0-2+b2 100
          1 http://ftp.de.debian.org/debian experimental/main amd64 Packages
        100 /var/lib/dpkg/status
     4:5.6.0-4+b2 500
        500 http://ftp.de.debian.org/debian unstable/main amd64 Packages

Es startet auch jeden Fall bei mir und es ist bedienbar. Ich benutze es aber ansonsten kaum, kann daher wenig zu tieferliegenden Funktionalitäten sagen.

Offline melmarker

  • User
  • Posts: 2.799
    • g-com.eu
Solved: relocation error: LIBAVCODEC 57
« Reply #4 on: 2018/01/08, 10:15:06 »
@whistler_mb - alles erledigt, das waren die segensreichen Auswirkungen von mm-dmo 8)

@mash: nu ja - Neuinstallation nicht, aber nach der Entfernung von mm-dmo fehlten Dir erst mal jede Menge Updates, die Aktion war ja notwendig, um überhaupt erst mal ein update-fähiges System zu erhalten. Leider warst Du verschwunden, bevor ich das erwähnen konnte (hatte es verdrängt) :)
« Last Edit: 2018/01/08, 19:54:38 by melmarker »
Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. (Benjamin Franklin, November 11, 1755)
Never attribute to malice that which can be adequately explained by stupidity. (Hanlons razor)

Offline mash

  • User
  • Posts: 47
Re: relocation error: LIBAVCODEC 57
« Reply #5 on: 2018/01/09, 02:15:45 »
Danke melmarker fuer die Hilfs-Aktion letzte Nacht.Und vor allem fuer die Erklaerung in Deineml Posting hier. Mir war tatsaechlich irgendwann nicht mehr klar warum ich diesen Fehler hatte aber eure hilfe war fuer mich eine ganz besondere Erfahrung.
when it was hard to write it should be hard to read

Offline piper

  • User
  • Posts: 1.785
  • we are the priests ... of the temples of syrinx
Re: relocation error: LIBAVCODEC 57
« Reply #6 on: 2018/01/09, 08:55:16 »
mm-dmo build here :P

Code: [Select]
System:    Host: x1 Kernel: 4.14.12-towo.2-siduction-amd64 x86_64 bits: 64 gcc: 7.2.0
           Desktop: KDE Plasma 5.10.5 (Qt 5.9.2) dm: sddm,sddm
           Distro: siduction 18.1.0 Patience - kde - (201801071438)

I'm not seeing any of these problems ;), but, I don't use chromium
digikam works fine, no problems on 3 boxes (one box died, power supply)


digikam (4:5.6.0-4+b2 Debian:unstable [amd64]

Back in the day to get rid of dmo, you used

Code: [Select]
aptitude search '?narrow(?version(CURRENT),?maintainer(Christian Marillat))' --disable-columns -F%p

dpkg --remove --force-depends $(aptitude search '?narrow(?version(CURRENT),?maintainer(Christian Marillat))' --disable-columns -F%p)

remove the multimedia repo in sources

apt -f install

This has not been tested in years ( I believe 5 years), I have never had to use it myself, but did test it at the time and it worked. (today could be different)

DMO is not recommended/supported and is frowned upon, but ...
Free speech isn't just fucking saying what you want to say, it's also hearing what you don't want to fucking hear

I either give too many fucks or no fucks at all, it's like I cannot find a middle ground for a moderate fuck distribution, it's like what the fuck