Kubuntu 20.04 Focal Fossa - Purrs like a bear

Discussion in 'all things UNIX' started by Mrkvonic, May 1, 2020.

  1. Krusty

    Krusty Registered Member

    Joined:
    Feb 3, 2012
    Posts:
    10,371
    Location:
    Among the gum trees
    I've compiled a small list of commands for maintaining Kubuntu / Mint and would appreciate any feedback about any I could add and / or remove.
    Code:
    1.) sudo apt-get update < > Updates all the packages in the apt cache to the current version
    
    2.) sudo apt dist-upgrade
    
    3.) fwupdmgr refresh --force
    
    4.) sudo apt-get upgrade < > Actually installs newer versions of the packages you have. After updating the lists, the package manager knows about available updates for the software you have installed
    
    5.) sudo apt-get autoclean < > Cleans all packages that have been superseded by a newer version of the same package
    
    6.) sudo apt-get autoremove < > Cleans all packages that were once installed as dependencies for other packages but are no longer needed; i.e. the original package was uninstalled
    Any thoughts appreciated.
     
  2. Stupendous Man

    Stupendous Man Registered Member

    Joined:
    Aug 1, 2010
    Posts:
    3,017
    Location:
    the Netherlands
    I use sudo apt autoremove and sudo apt autoclean.
    I ran fwupdmgr --force refresh, once, as a test. It doesn't fix the "Failed to update metadata for lvfs: checksum failure: failed to verify data" error, it was back 24 hours later.
    I do not use sudo apt update, sudo apt upgrade, or sudo apt full-upgrade (which is the apt equivalent of apt-get dist-upgrade), I leave all that to Discover (or Muon Package Manager).
     
  3. Iangh

    Iangh Registered Member

    Joined:
    Jul 13, 2005
    Posts:
    857
    Location:
    Melbourne, Australia
    It seems to have worked for me. Not seen the error for 3 days.
     
  4. Krusty

    Krusty Registered Member

    Joined:
    Feb 3, 2012
    Posts:
    10,371
    Location:
    Among the gum trees
    It seems to have worked here too so far.
     
  5. Krusty

    Krusty Registered Member

    Joined:
    Feb 3, 2012
    Posts:
    10,371
    Location:
    Among the gum trees
    Well that didn't last long. The machine was on all night and when I opened Discover this morning I got the same "Failed to fetch..." error.
     
  6. Stupendous Man

    Stupendous Man Registered Member

    Joined:
    Aug 1, 2010
    Posts:
    3,017
    Location:
    the Netherlands
    I'm sorry, but that is what I guessed would happen.
    I don't know why Iangh's experience seems to be different.
    I don't know if there is one server for the LVFS (Linux Vendor Firmware Service), or different regional servers like for (*)Ubuntu. Or if it is not a server issue.

    Ah, I just noticed shmu26 opened an issue here: https://github.com/fwupd/fwupd/issues/3652. I hope they'll figure out what is wrong and how to fix it.
     
  7. Krusty

    Krusty Registered Member

    Joined:
    Feb 3, 2012
    Posts:
    10,371
    Location:
    Among the gum trees
    I was hopeful but no such luck. :(
    @Iangh appears to also be in Australia, but quite possibly a different part of the country as Australia is huge. I suspect we would be accessing the same server/s though.
    Oh, nice!

    Thanks and best of luck, @shmu26 . :thumb:
     
  8. Iangh

    Iangh Registered Member

    Joined:
    Jul 13, 2005
    Posts:
    857
    Location:
    Melbourne, Australia
    You've jinxed me. I'm now seeing on two out of 3 machines.:(
     
  9. Stupendous Man

    Stupendous Man Registered Member

    Joined:
    Aug 1, 2010
    Posts:
    3,017
    Location:
    the Netherlands
    Sorry to hear that.
    I hope that in shmu26's https://github.com/fwupd/fwupd/issues/3652 thread, hughsie (Richard Hughes) will see what is going on and how to fix it.
    In an earlier thread with a similar issue, https://github.com/fwupd/fwupd/issues/2089, hughsie diagnosed the issue to the fact that the server was 'OOMing', out of memory, a server reboot fixed that.
     
  10. wat0114

    wat0114 Registered Member

    Joined:
    Aug 5, 2012
    Posts:
    4,096
    Location:
    Canada
    I've used all except #3 successfully every time in Debian or Debian-based distros. I've never heard of #3 before.
     
  11. Iangh

    Iangh Registered Member

    Joined:
    Jul 13, 2005
    Posts:
    857
    Location:
    Melbourne, Australia
    Hope so, third PC has reverted to error message.:(
     
  12. Stupendous Man

    Stupendous Man Registered Member

    Joined:
    Aug 1, 2010
    Posts:
    3,017
    Location:
    the Netherlands
    I posted in shmu26's thread at GitHub, referring to the reports in this Wilders thread, in case that might be helpful to hughsie (Richard Hughes) to get a view of lvfs issue reports.
     
  13. Krusty

    Krusty Registered Member

    Joined:
    Feb 3, 2012
    Posts:
    10,371
    Location:
    Among the gum trees
    Not a lot of answers in that thread as yet.
     
  14. Stupendous Man

    Stupendous Man Registered Member

    Joined:
    Aug 1, 2010
    Posts:
    3,017
    Location:
    the Netherlands
    One by vlrmt and one by Mastercroft, later on, but that's it, no more replies by hughsie (Richard Hughes).
    I guess Richard Hughes is sure the issue is not caused by fwupd or LVFS.

    Edit:
    A lot more replies, by now.
     
    Last edited: Sep 3, 2021
  15. Iangh

    Iangh Registered Member

    Joined:
    Jul 13, 2005
    Posts:
    857
    Location:
    Melbourne, Australia
    So the advice for Kubuntu 20.04 users is to sit back and wait for a fix?

    Anything I should be doing in the meantime?
     
  16. Stupendous Man

    Stupendous Man Registered Member

    Joined:
    Aug 1, 2010
    Posts:
    3,017
    Location:
    the Netherlands
    Regarding the "Failed to update metadata for lvfs: checksum failure: failed to verify data" error, I am waiting for a fix. I hope the GitHub thread will lead to insight in the cause of the error, and consequently a fix. I don't think we need to do anything in the meantime. Unless one has something to add to the GitHub thread that could be helpful.
     
  17. Krusty

    Krusty Registered Member

    Joined:
    Feb 3, 2012
    Posts:
    10,371
    Location:
    Among the gum trees
    Annoying as the error message is, I don't believe it actually has any affect on downloading and / or installing updates. I could be wrong though.

    Strange it has been going on for so long without a fix.
     
  18. Krusty

    Krusty Registered Member

    Joined:
    Feb 3, 2012
    Posts:
    10,371
    Location:
    Among the gum trees
  19. Stupendous Man

    Stupendous Man Registered Member

    Joined:
    Aug 1, 2010
    Posts:
    3,017
    Location:
    the Netherlands
    Yes, I noticed, thanks, Krusty.
    I'm keeping an eye on both threads.
    Based on the GitHub thread, I was not sure where and what to report, exactly, otherwise I would've been willing to post that report. Let's hope the new bug report is what was needed to get the issue fixed.
     
  20. Krusty

    Krusty Registered Member

    Joined:
    Feb 3, 2012
    Posts:
    10,371
    Location:
    Among the gum trees
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.