Pop!OS update wonky?

ranking1960

Member
Joined
Apr 10, 2026
Messages
29
Reaction score
40
Credits
248
The latest update keeps telling me: I couldn't copy the error message so I put it in the below screenshot. Is something wrong with the files or do I have some sort of problem?
 

Attachments

  • Screenshot_error-msg.png
    Screenshot_error-msg.png
    325.9 KB · Views: 67


I am having similar issues with the updating. When I start the process it errors out and the Details drop-down gives the message that dpkg was interrupted and I need to run dpkg --configure -a. When I run this it again errors out and the Details drop-down states that the package Daemon disappeared. Further attempts swap back and forth between the two error messages. Running dpkg --audit results in a message that the update is hashed up and I need to run dpkg --force-remove-reinstreq to fix it. I couldn't find anything on the "reinstreq" part so I came here to ask if this is the right step forward?
 
@CRR^2 :-

PopOS! is developed by System76, and specifically built to work best with their own hardware setups. That said, they do also offer it for general public download.

IF it works okay for you, OOTB, that's great.....but if it doesn't, you can spend days, weeks, even months chasing your own tail, trying to fix 'issues' & getting absolutely nowhere. It really IS that 'fussy'.

Just my two-penn'orth, FWIW.


Mike. ;)
 
Last edited:
So is it time to switch OS? Or should I try the repair first to see if it fixes the issue, as much for information as anything, as I have already made a boo disk of Mint Xfce?
 
I tried the system recommended 'dpkg --force-remove-reinstreq' command and got an error message that it didn't recognize the command. I tried a number of variations on the format, but nothing worked. I switched to 'aptitude', read the manual and eventually was successful in updating the system. When I first opened 'aptitude' it recognized there was a problem with the status and said to run 'dpkg --configure -a', which I did. when I reopened 'aptitude' it opened without the error. After reading the manual I decided to run 'aptitude safe-upgrade' from the command line. This worked! It took a while to work its way through the packages that were not up to date (73) and held (34), but eventually it finished. The updater now says the system is "up to date". Hurrah.
 


Follow Linux.org

Members online


Top