Upgrade to 22.04 fails (failed to downgrade packages) #320
Comments
dlschmidt
changed the title
|
Have the same issue +1 |
|
Same error here. Possibly related to mono / xamarin. I'm attaching the corresponding logs |
|
@mbaske Can I ask you how you retrieved those logs? I would then post my logs aswell. |
|
dlschmidt The logs are stored in /var/log/apt/history.log and /var/log/syslog |
|
This shows my /var/log/syslog |
|
I have exactly the same error log as @dlschmidt |
|
I had the same issue |
|
Also having this issue from the command line pop-upgrade 21.10 -> 22.04: |
|
If everyone could share their complete logs from |
|
Attaching output from "journalctl -u pop-upgrade" |
|
That one indicates an issue with trying to recover the system state after removing a mono PPA. |
|
That looks like a system that's already partially upgraded to 22.04, and it's failing to downgrade packages back to 21.10 versions. |
|
Going backwards will be more difficult than going forward. I'd perhaps recommend trying to upgrade manually. Switch all the apt sources in |
|
|
this my log , same erro |
I tried this approach - running the script threw a couple of errors, then shut down the system. After reboot, Pop_Shop! showed the new jammy sources (old impish being greyed out) and 60 pending updates, but trying to execute them failed with more errors. |
Thanks! Although the GUI-Updater failed after script execution and reboot, my system somehow updated to 22.04 after a few restarts without me doing anything. (Automatic Updates are disabled) |
|
PS: I think, there is still something wrong. And if I would run |
|
Like @dlschmidt I had the same experience with my system having updated by itself to 22.04 after a restart. But it still wasn't working properly; video card no longer was detected and I couldn't mount the SATA drive. So I did an OS refresh, and it is now stable and at 22.04. But this is equivalent to a new OS install from image. And I lost all previous system-wide installed binaries and libraries. Stuff in my home was still preserved of course. By no means a fix, but a desperate work-around just to get my system bumped up to 22.04. |
|
I have a similar issue: |
|
I have the same problem - any solutions to this yet? |
Could you give the command steps to switch all the apt sources in there? |
Unfortunately that didn't work |
sudo sed -i 's/impish/jammy/g' /etc/apt/sources.list.d/system.sources /etc/apt/sources.list.d/pop-os-release.sources /etc/apt/sources.list.d/pop-os-apps.sources |
It works on me Thanks ! sudo sed -i 's/impish/jammy/g' /etc/apt/sources.list.d/system.sources /etc/apt/sources.list.d/pop-os-release.sources /etc/apt/sources.list.d/pop-os-apps.sources
sudo apt update
sudo apt full-upgrade
pop-upgrade recovery upgrade from-release
pop-upgrade release upgrade |
|
Ekk, this process failed and now my machine can't start, it requested a reboot during the process, it can't load the gui but I still have access to terminal. Continuing the process still errors at pop-upgrade release upgrade with "release upgrade aborted: failed to downgrade packages" |
I attempted this process but it canceled due to having too many errors. |
|
|
|
I had the same problem and didn't manage to resolve it - so I created a new bootable USB of POP OS and refreshed teh installation - this created other issues though as my apps needed to be reinstalled (but managed to rescue my user account) |
|
I had a problem with rtl8821ce-dkms remaining in a broken install state (the installed version didn't support the running kernel). I removed it, did the upgrade, the re-installed it afterwards. Generally this sort of problems may occur with any dkms driver I suppose. |
|
@Ajilagi @arthurlch @wanjas Excuse me for mentioning you particularly, but I wanted to pose a quick question: While executing What did you guys choose? I assume, I should go with the default way. I want to be sure to follow the right steps, as my system is stuck somewhere in-between 21.10 and 22.04, as it seems. I have actually already updated to 22.04 through the GUI. The update seemed to be successful, but after rebooting, the system was still at 21.10 and it prompted me to update to 22.04. After some issues with unresolved package dependencies (related to I would be very grateful if someone could confirm my thoughts. Thank you very much already in advance! |
|
@dlschmidt Well, after the first step, nothing happened (meaning, there was no output in the console). The second step resulted in a few seemingly successful operations, but also a few 404 errors and errors which state that certain depots don't contain a release-file. Now I'm "stuck" at What did you choose when it prompted you to choose a given option in the described situation, in case you have encountered this? Or what would you choose? Would you confirm my assumption to select "N"? Thank you very much for your interest! |
|
I think we can help more if you can paste the exact URLs which could not be resolved / throwed the 404. |
|
@dlschmidt I will make sure to do so, in case the process doesn't resolve the issue, but I want to give it a try nonetheless. Such errors don't necessarily have to prevent further processes, as they may be unrelated. Which option did you choose when it prompted you to choose a given option in the described situation, in case you have encountered this? Or what would you choose? Would you support my assumption to select "N"? |
|
I can not remember that this prompt was shown back then. Therefore I can only give you the advice to fix the 404, because the system upgrade will definitely depend on the process of downloading the correct packages and package metadata. How shall your popOS do the full-upgrade when it is not possible to fetch all neccessary packages? |
|
@dlschmidt Alright, I will post the entire output that was written to the terminal as a result of |
|
Yes, German is my main language. |
I can't remember to have ever done that. Do you now suggest to edit it manually? The content of this file redirects me to another file: The "system.sources" file contains the following content: |
|
Maybe try this #320 |
|
Isn't this being done with |
|
clearly your system.sources contains "impish" so that command did not work in your case |
|
After running the command again (twice), it seems to have changed. I'm not entirely sure why I had to do it three times, but anyway... I will try it again. |
|
And |
|
@dlschmidt I have made some progress, but I fear I'm still not in the position to be able to update. I figured out, that I needed to run the suggested command from this comment (#320) twice as well, so that it has some effect. Now, I will try to reboot a couple of times. |
|
You dont have to reboot. You may have installed popOS without a recovery partition. |
|
Unfortunately, it was unsuccessful: |
|
If I try it again, I get another reason for the abortion of the upgrade. This is the output in this case: |
|
And now (after rebooting) there seem to be some package dependency issues with Output of Output of Output of |
|
@duck-dev I can't read German, but the problem is pretty simple at this point. You have some 21.10 packages installed and some 22.04 packages installed. The packages depend on each other (and the dependencies include the version numbers, so they have to match.) The steps to fix this are two-fold:
From your earlier The sources were misconfigured at that time-- the URL was set to old-releases, but Jammy is the new release, not an old release. The
To do this, for any package name that apt complains about, run If your sources are configured properly and you specify compatible version numbers, then apt should proceed with the operation. If you can't figure this out, please feel free to join the ~upgrade-help channel on the Pop!_OS Mattermost server, and someone can go back and forth with you to figure the specific command for your system out (this is easier to do via live chat than a GitHub issue, as it requires feedback between every step): https://chat.pop-os.org/pop-os/upgrade-help I also want to be clear that you are doing the upgrade manually at this point (as System76 customers can reach out to support for technical assistance. For non-System76 hardware, you can seek community support on Reddit or Mattermost. |
|
Hello @jacobgkau . First of all, thank you very much for your answer, it certainly proves helpful. I explained my whole situation from the beginning in the Pop!_OS Mattermost server, as you suggested. I tried to provide all the information I have and think is useful. Now, as I described there, after changing the URL for the After all that, there are no package updates anymore ( How should I proceed now? Am I allowed to continue with the update? Edit: I tried to continue with the update through the GUI and it just throws everything over again, as if nothing had changed. The It just doesn't work. |
|
@duck-dev Part of the issue is that Once you have all of your sources pointing to This will remove the directory that those files come from and then force them to be reinstalled. The reason apt doesn't do this automatically is because Once you do this, I replied to your thread on Mattermost with this information. |
|
Thank you very much for your answer. You were absolutely right, it seems to work properly now. It doesn't prompt me to update anymore, and the settings display 22.04 as the current version. |
|
We are working on preventing more upgrade issues from happening over in #319. |
and others
Distribution (run
cat /etc/os-release):NAME="Pop!_OS"
VERSION="21.10"
Issue/Bug Description:
After clicking the "Downloading Pop!_OS 22.04"-Button in OS Upgrade & Recovery, the following error is shown:
failed to upgrade OS: client error: failed to downgrade packagesBut when I follow all the suggested comments in order like "apt clean", "apt update -m" and so on, no error will be prompted.
Steps to reproduce (if you know):
I just used regularly "apt-get update" and "apt-get upgrade" and installed some must-have applications like VSCode via .deb packages.
The text was updated successfully, but these errors were encountered: