7

I am getting this error when I tried to update my system (Ubuntu 22.04) and getting this error message

The following packages have been kept back:
  gstreamer1.0-vaapi
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.

I have tried some solutions suggested on the internet like installing the package manually and i got this message: sudo apt-get install gstreamer1.0-vaapi

The following packages have unmet dependencies:
 gstreamer1.0-vaapi : Depends: libgstreamer-plugins-bad1.0-0 (>= 1.20.3) but 1.20.1-1ubuntu2 is to be installed
E: Unable to correct problems, you have held broken packages.

and "libgstreamer-plugins-bad1.0-0" also already installed. I have also tried commands like sudo apt-get dist-upgrade but I am getting the same error.

I'm on Ubuntu 22.04 with a Nvidia GPU.

[Edit]: Guys, this is not a duplicate of https://askubuntu.com/questions/223237/unable-to-correct-problems-you-have-held-broken-packages I have tried the suggestions from there but I am still having this issue. Thank You.

yaa__
  • 703
  • no, I have tried it too. the same error is shown even when i try these suggested commands. – yaa__ Jul 28 '22 at 10:17
  • You haven't provided any clear messages, which usually provide clues, ie. the package I'd expect to see is gstreamer1.0-vaapi | 1.20.1-1 | jammy/universe | amd64, arm64, armhf, ppc64el, riscv64, s390x which has a fix currently in -proposed but your messages don't include such detail, thus we're limited in how we can look up details for you. Your message does show libgstreamer-plugins-bad1.0-0 | 1.20.3-0ubuntu1 | jammy-proposed/universe | amd64, arm64, armhf, i386, ppc64el, riscv64, s390x where the satisfy requirement is in -proposed ... – guiverc Jul 28 '22 at 11:12
  • how do I provide that message to you? Is there a specific command you want me to run so that I can share the outcome here? – yaa__ Jul 28 '22 at 11:54
  • 1
    I have asked a new question here: https://askubuntu.com/questions/1420969/how-to-force-packages-have-been-kept-back-to-be-installed-automatic . My problem started exactly as yours, and now it has become something as explained in my question. Can you verify that in your system too? – FedKad Jul 29 '22 at 09:48
  • You can try to correct it with Synaptic... https://forum.ubuntu-nl.org/index.php?PHPSESSID=408mhn99rt9in1s74jt0ucv755&topic=110293.msg1068274#msg1068274 – Ron Jul 30 '22 at 07:34
  • @yaa__ Please look at this answer: https://askubuntu.com/a/1421041/855322 – FedKad Jul 30 '22 at 08:16
  • 1
    Yes, everyone please look at that answer! There are two variations of correct answer there. First is to disable phased updates, and second is to synchronize phased updates if you want all boxes phasing at the same time. – Utkonos Jul 30 '22 at 14:28
  • 2
    Does this answer your question? How to force "packages [that] have been kept back" to be installed [as] "automatic" – Utkonos Jul 30 '22 at 14:36

1 Answers1

4

I am getting the exact same error while running updates. Something, I believe, is currently broken in the current build chain. I would suggest waiting a little bit and seeing if a new update to the package fixes the issue:

$ sudo apt upgrade gstreamer1.0-vaapi/jammy-updates
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Selected version '1.20.1-1ubuntu1' (Ubuntu:22.04/jammy-updates [amd64]) for 'gstreamer1.0-vaapi'
Selected version '1.20.3-0ubuntu1' (Ubuntu:22.04/jammy-updates [amd64]) for 'libgstreamer-plugins-bad1.0-0' because of 'gstreamer1.0-vaapi'
Calculating upgrade... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 gstreamer1.0-plugins-bad : Depends: libgstreamer-plugins-bad1.0-0 (= 1.20.1-1ubuntu2) but 1.20.3-0ubuntu1 is to be installed
E: Broken packages
FedKad
  • 10,515
HCEarwicker
  • 41
  • Thanks for making my post readable FedKad :) -- I appreciate it. – HCEarwicker Jul 28 '22 at 16:47
  • Can you try the same command once more? It seems to have been fixed now! – FedKad Jul 28 '22 at 16:49
  • Same issue as before. Package being held back. – HCEarwicker Jul 28 '22 at 16:51
  • Thanks, I will wait and see if new update fixes this issue or not. – yaa__ Jul 28 '22 at 18:59
  • 1
    @HCEarwicker The problem has become worse. And I have asked a new question here: https://askubuntu.com/questions/1420969/how-to-force-packages-have-been-kept-back-to-be-installed-automatic . Can you verify that? – FedKad Jul 29 '22 at 09:49
  • 2
    Everyone go check out @FedKad question and the two answers there. Both answers are correct for different use cases. The problem is not actually a bug, this is all part of a design decision (feature) made in Ubuntu called Phased Updates. You can disable it so everything behaves as older versions of Ubuntu did, or you can set the phasing to be synchronized on all computers you're running. Or you can understand what this feature is, and just leave it as is. – Utkonos Jul 30 '22 at 14:29